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
unabl
>Date: Wed, 24 Sep 2003 00:58:12 -0500
>From: "Conrad J. Sabatier" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: dhclient/ipfw conflict on boot
>I just ran into this today after upgrading. It seems that dhclient is
>unable to initialize prope
On Wed, Sep 24, 2003 at 05:51:56AM -0700, David Wolfskill wrote:
> >From: "Conrad J. Sabatier" <[EMAIL PROTECTED]>
> >Subject: dhclient/ipfw conflict on boot
>
> >I just ran into this today after upgrading. It seems that dhclient is
> >unable to i