Date: Mon, 12 Sep 2022 03:35:32 -0700 From: David Wolfskill <david@catwhisker.org> To: Graham Perrin <grahamperrin@freebsd.org> Cc: FreeBSD wireless <freebsd-wireless@freebsd.org> Subject: Re: Wi-Fi: netif restart wlan0: name resolution: resolvconf.conf(5) Message-ID: <Yx8LdFAEsGmCuzrm@albert.catwhisker.org> In-Reply-To: <0dd6932e-2222-8dc0-45be-7c22cd362524@freebsd.org> References: <7f07811f-503b-23ec-09a1-e563a4d39f32@freebsd.org> <0dd6932e-2222-8dc0-45be-7c22cd362524@freebsd.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, Sep 11, 2022 at 07:22:48PM +0100, Graham Perrin wrote: > On 11/09/2022 13:36, Graham Perrin wrote: > > % grep -v \#/etc/resolvconf.conf > > % > > To clarify: the file exists, it comprises lines that are commented out > (mostly, lines that are used only in static environments). > > The name resolution problem was with DHCP. Right -- re-connecting (e.g., via "service netif restart wlan0") should be starting "dhclient wlan0". Because I (also) needed to re-populate my ipfw rules when I get a new DHCP lease, I cobbled up a /etc/dhclient-exit-hooks script; while I was there anyway, I put in some code at that point to make /etc/resolv.conf "sane" (by whatever passes for my standards). Peace, david -- David H. Wolfskill david@catwhisker.org "In my administration, I'm going to enforce all laws concerning the protection of classified information. No one will be above the law." -- D. Trump, August, 2016 See https://www.catwhisker.org/~david/publickey.gpg for my public key. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQSr0Kzv+UJRY3wfOii0+6PfV4Ix1AUCYx8Lc18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0QUJE MEFDRUZGOTQyNTE2MzdDMUYzQTI4QjRGQkEzREY1NzgyMzFENAAKCRC0+6PfV4Ix 1OkpAP976GEF+YbfcM/rAmTzT36lgrcGoo4PTRF3kTMKm+4D9AD+I5D1vrFI4j89 lzsPxn/ZituSIHTYIw25T0m6x9MufgA= =D45z -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Yx8LdFAEsGmCuzrm>