> 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)
