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"Received on Tue Sep 23 2003 - 20:58:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:23 UTC