Date: Mon, 12 Sep 2022 19:48:48 +0100 From: Graham Perrin <grahamperrin@freebsd.org> To: FreeBSD wireless <freebsd-wireless@freebsd.org> Subject: Wi-Fi: netif restart wlan0: name resolution: dhclient Message-ID: <d6cfe45f-d8cd-b90b-a7c2-242aff5f3881@freebsd.org> In-Reply-To: <Yx8LdFAEsGmCuzrm@albert.catwhisker.org> References: <7f07811f-503b-23ec-09a1-e563a4d39f32@freebsd.org> <0dd6932e-2222-8dc0-45be-7c22cd362524@freebsd.org> <Yx8LdFAEsGmCuzrm@albert.catwhisker.org>
index | next in thread | previous in thread | raw e-mail
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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d6cfe45f-d8cd-b90b-a7c2-242aff5f3881>