Re: Wi-Fi: netif restart wlan0: name resolution: dhclient

Just FYI, if that is related:

when wlan0 was used to connect to the internet (in the absence of a
physical cable) and wlan1 was used as an AP, then these DHCP problems
were regular, especially when resuming after suspend or when due to
marginal wifi signal wlan0 lost connection.

service netif restart wlan0  then regularly failed due dhclient problems.
Retrying after a sufficient delay (e.g. next day) often "did the
trick", dhclient worked.

HTH

On 9/12/22, Graham Perrin <grahamperrin@freebsd.org> wrote:
> On 12/09/2022 11:35, David Wolfskill wrote:
>>
>>> ... The name resolution problem was with DHCP.
>> Right -- re-connecting (e.g., via "service netif restart wlan0") should
>> be starting "dhclient wlan0". ...
>
> I'm as certain as I can be that dhclient does run.
>
> (I would have noticed the absence of an IP address in output from
> ifconfig wlan0.)
>
> So, if /etc/resolv.conf (a) lacked what was required following those
> things, then (b) was OK following a reboot of the OS: what might be the
> explanation for (a)?
>
> Privately, I received hints such as this:
>
>> You can run:
>> tcpdump -i wlan0 -s 0 -vvv port 67 or 68
>> to watch the DHCP dialog and see what your server is sending.
> -- useful for the future, but I'm now faraway from the home router where
> FreeBSD behaved strangely.
>
>
>