06.03.2023 14:13, Jonathan Gray пишет: > Parts of bwfm already mention wep. Is it just a matter of needing to > set IEEE80211_C_WEP or is more needed?
stsp quote from the initial 'Re: ifconfig: return non-zero on failed "nwkey"' https://marc.info/?l=openbsd-tech&m=163587479013162&w=2 : > But regardless, this error should never happen. > It looks like bwfm(4) does support WEP but the C_WEP capability is missing > from ic_caps so net80211 believes WEP was not supported by this driver. > > I don't think we have any supported wifi device that does not support WEP. > Even an(4) supports WEP! Noone ever stood up and gave WEP on bwfm a try. Until someone fixes it or rips out WEP completely, we should remove the false claim from the manual. I've intentionally left the recommendation against WEP and WPA1 untouched to it informative and the diff simple. OK? Index: bwfm.4 =================================================================== RCS file: /cvs/src/share/man/man4/bwfm.4,v retrieving revision 1.18 diff -u -p -r1.18 bwfm.4 --- bwfm.4 23 Apr 2022 18:41:13 -0000 1.18 +++ bwfm.4 8 Mar 2023 12:17:21 -0000 @@ -78,7 +78,6 @@ for other cards. The .Nm driver can be configured to use -Wired Equivalent Privacy (WEP) or Wi-Fi Protected Access (WPA1 and WPA2). WPA2 is the current encryption standard for wireless networks. It is strongly recommended that neither WEP nor WPA1
