dhclient/ipfw conflict on boot
Conrad J. Sabatier
conrads at cox.net
Tue Sep 23 22:58:20 PDT 2003
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 <conrads at cox.net> - "In Unix veritas"
More information about the freebsd-current
mailing list