A FreeBSD User <[email protected]> writes:
> Dag-Erling Smørgrav <[email protected]> writes:
> > As a workaround, add this to /boot/loader.conf:
> > 
> >     net.inet.ip.fw.default_to_accept="1"
> the above "trick" doesn't help.

This is concerning.

The fact that `dhclient em0` works after the firewall is up proves that
the firewall rules themselves are not the issue.  I therefore assumed
that the problem was that dhclient was trying to acquire a lease before
the firewall was configured.  Switching default_to_accept on should have
made that possible.  The fact that it doesn't means the firewall isn't
to blame at all.  Something else is causing dhclient not to run at boot.

Could you please provide the output from the following command:

    grep -r '^[^#]' /etc/rc.conf*

Could you please also provide a log of the boot messages, if possible?

DES
-- 
Dag-Erling Smørgrav - [email protected]

Reply via email to