From owner-freebsd-current@FreeBSD.ORG Tue Sep 23 22:58:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7000B16A4B3 for ; Tue, 23 Sep 2003 22:58:20 -0700 (PDT) Received: from lakemtao03.cox.net (lakemtao03.cox.net [68.1.17.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2869643FE1 for ; Tue, 23 Sep 2003 22:58:19 -0700 (PDT) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: from ip68-14-60-78.no.no.cox.net ([68.14.60.78]) by lakemtao03.cox.netESMTP <20030924055818.MFYP14673.lakemtao03.cox.net@ip68-14-60-78.no.no.cox.net> for ; Wed, 24 Sep 2003 01:58:18 -0400 Received: from ip68-14-60-78.no.no.cox.net (localhost [127.0.0.1]) h8O5wHWm001978 for ; Wed, 24 Sep 2003 00:58:17 -0500 (CDT) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: (from conrads@localhost)h8O5wCd5001977 for freebsd-current@freebsd.org; Wed, 24 Sep 2003 00:58:12 -0500 (CDT) (envelope-from conrads) Date: Wed, 24 Sep 2003 00:58:12 -0500 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20030924055812.GA1702@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: dhclient/ipfw conflict on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 05:58:20 -0000 I just ran into this today after upgrading. It seems that dhclient is unable to initialize properly at boot time, due to the prior initialization of ipfw2 (default to deny policy). As all traffic is denied until my firewall ruleset gets loaded (not until just after dhclient fails), it's unable to communicate with my ISP's DHCP server. This should be a quick and easy fix, right? :-) -- Conrad Sabatier - "In Unix veritas"