Date: Wed, 23 Sep 2020 10:33:02 +0400 From: Gleb Popov <arrowd@freebsd.org> To: Eugene Grosbein <eugen@grosbein.net> Cc: freebsd-net@freebsd.org Subject: Re: ifconfig_*="DHCP" in absence of server Message-ID: <CALH631ngcZ7eNP9JmVV7hiwmzBG4MGqR%2Bm8niO5ApX%2Bi7te-LA@mail.gmail.com> In-Reply-To: <93df435f-3544-5725-f0d6-3b85707870bf@grosbein.net> References: <CALH631mMj%2BObDEWnQtm7BVU1d9AfvAtngiPD1-ZPawmGUXOGEw@mail.gmail.com> <3ef4aa1b-d8fa-e201-6db8-e4c1d1dac63e@grosbein.net> <CALH631kPh96ucaqVnFtq6s7OcoW8t-cKNNZAmsLQ21T5Xjp35w@mail.gmail.com> <93df435f-3544-5725-f0d6-3b85707870bf@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 18, 2020 at 9:05 PM Eugene Grosbein <eugen@grosbein.net> wrote:
> 18.09.2020 20:05, Gleb Popov wrote:
>
> >> Look for "background_dhclient" in the rc.conf manual page, it merely
> adds
> >> "-b"
> >> to dhclient flags.
> >>
> >>
> > Thanks, this indeed improved things for the "netif" part of the problem.
> > But it still waited 30s for "default route interface". I found the
> > ${defaultroute_delay} variable in /etc/rc.d/defaultroute, which isn't
> > documented, and set it to "1s" in /etc/rc.conf. This finally did the
> trick.
> >
> > However, the networking on FreeBSD machines started to come up even
> longer.
> > I suspect this is because dhclient gradually increases the interval
> between
> > DHCP requests if it doesn't get an answer. I haven't found a way to
> > circumvent this. Any suggestions are welcome.
>
> Read dhclient.conf(5) manual page :-)
>
>
Right, I forgot that dhclient has a config file too. Thanks for all tips,
everything worked out like a charm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631ngcZ7eNP9JmVV7hiwmzBG4MGqR%2Bm8niO5ApX%2Bi7te-LA>