DHCP with ipfw
Suporte Matik
asstec at matik.com.br
Wed Apr 6 03:34:20 PDT 2005
On Tuesday 05 April 2005 23:12, Sergei Gnezdov wrote:
> In gmane.os.freebsd.devel.ipfw, you wrote:
> > On Monday 04 April 2005 05:06, Martin wrote:
> >> If the DHCP server is slow and did not reply back before the
> >> dhclient did continue the boot process, you maybe you do have
> >> to reload the FW rules once your DHCP connection is established.
> >
> > your dhcpd should not be sooo slow and ignore several retries
>
> I don't think dhcp speed matters. I can say for sure that I see
> ipfw rules initialization happends before (!) dhcp is initialized.
> I can't prove it with dmesg, because it does not capture absolutely
> everything, but I can see on the console ipfw rules show up first
> and then a dhcp startup message.
after boot mounts your partitions the network should be initialized
and if you have ifconfig_nic="DHCP" in your rc.conf dhclient should
look for a dhcp server first and probably gets an answer. If you
didn't daemonized the dhclient process it should stay until timeout
or getting the IP address and then run the rest of network setup.
So almost for sure dhcp goes first but is not getting an answer within
time and you do not noticed it.
May be your timeout in dhclient.conf is too low if your network
performance is poor. Or you may try increasing your retry value
may be you have an intrface problem and the -w option could be useful
for you or you consider configuring interface NIC { } in your
dhclient.conf
BTW what fbsd version are you referring to?
> I think startup order is simply incorrect.
does not make so much sense starting ipfw before the initial network
setup what invokes certainly dhclient first if set ...
Hans
--
Infomatik
http://info.matik.com.br
More information about the freebsd-ipfw
mailing list