Re: faq/faq6.html#Wireless : nwid vs join
> Not every detail gets into the FAQ. The difference between > 'join' and 'nwid' is described in the ifconfig(8) man page. Thank you for the helpful response Ken. If anyone is inclined, a quick patch to include what I thought could also be helpful to others without going on too long. Hopefully it's formatted correctly. diff --git faq6.html faq6.html index 08343df0c..52770af6e 100644 --- faq6.html +++ faq6.html @@ -398,7 +398,8 @@ inet autoconf Note that inet autoconf should be after the other configuration lines, as the network adapter will not be able to send a DHCP request until -it is configured. +it is configured. The choice between nwid and join +is explained further in https://man.openbsd.org/ifconfig;>ifconfig(8) Trunking a Wireless Adapter
Re: faq/faq6.html#Wireless : nwid vs join
On Mon, Oct 17, 2022 at 5:37 AM tux2bsd wrote: > > nwid puffyuberalles wpakey passwordhere > > inet autoconf > > > > Or, for multiple access points: > > > > join home-net wpakey passwordhere > > join work-net wpakey passwordhere > > join cafe-wifi > > inet autoconf > > It isn't clear why one uses 'nwid' and the other uses 'join', > I think it would be better to be consistent for either use case - > all 'nwid' or all 'join' (I prefer 'join'). > Not every detail gets into the FAQ. The difference between 'join' and 'nwid' is described in the ifconfig(8) man page. 'join' is used to add a network to the 'join list' which is a list of networks the system will try to connect to, when not already connected to another network. 'nwid' is used when you want to immediately connect to an access point without disturbing the join list. For example, you might use 'nwid' to connect to a public network such as one provided by a hotel or a cafe, without modifying your 'join' list which might normally have only your private home and office networks. -ken
faq/faq6.html#Wireless : nwid vs join
> nwid puffyuberalles wpakey passwordhere > inet autoconf > > Or, for multiple access points: > > join home-net wpakey passwordhere > join work-net wpakey passwordhere > join cafe-wifi > inet autoconf It isn't clear why one uses 'nwid' and the other uses 'join', I think it would be better to be consistent for either use case - all 'nwid' or all 'join' (I prefer 'join'). https://www.openbsd.org/faq/faq6.html#Wireless section: "Configuring a Wireless Adapter" tux2bsd p.s. Below has no real point other than to share the tale. It's how I ended up noticing the nwid/join difference above (while troubleshooting the following). 001_wifi bit me hard (OpenBSD 7.1, WIFI status: no network). Scenario: - Old laptop (eeepc 1005HA), had OpenBSD 7.0 already installed - Turned it on for the first time in months - ran 'sysupgrade', rebooted, was fine - went far away, suspend kicked in - wifi would not work after resume, distracted by this I tried to no avail to remedy my network settings - reboot wifi worked, sleep, wifi failed again (more useless remedy attempts) - reboot wifi worked, ifconfig athn0 down then up; wifi failed again (ruled out suspend but more useless remedy attempts) - being so fixated on the wifi not working I'd forgotten all about 'syspatch' until an epiphany I rebooted to try it. - ran syspatch, 001_wifi installed & rebooted, wifi down/up and it worked - fantastic - syspatch again for the rest and fw_update for good measure Sent with Proton Mail secure email. (tux2bsd note: apologies if Proton Mail busts formatting, this has been piped through fmt -sw72)
