wireguard-openbsd/sys/net80211/ieee80211_node.c, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/net80211/ieee80211_node.c?h=jd%2Fqueueboosts2020-05-31T09:08:33ZRemove a dead assignment to ni_rsn_state in ieee80211_node_leave_rsn().2020-05-31T09:08:33Zstspstsp@openbsd.org2020-05-31T09:08:33Zurn:sha1:657bc46d951277cea3a1b922a2a7a9547526bbfd
Patch by Mikolaj Kucharski
Purge the ic_bss->ni_savedq mbuf queue when a wireless interface goes down.2020-05-05T18:14:42Zstspstsp@openbsd.org2020-05-05T18:14:42Zurn:sha1:539559bc1fbfd683fee58d889b480de7b7d5c9b4
Purging this queue prevents a panic which occurs when a WPA2-enabled athn(4)
hostap interface is reconfigured while this queue contains frames.
In hostap mode, this queue contains group-addressed (broadcast) frames
which are buffered for clients sleeping in powersave state. Frames on
this queue are transmitted when it is time to send another beacon, at
which point in time sleeping clients wake up to receive such frames.
The panic message is "key unset for sw crypto", which can be explained as
follows: Group keys are cleared when the interface goes down. The beacon Tx
interrupt handler gets triggered by hardware when the interface comes back
up. This handler attempts to encrypt the queued frames for transmission,
resulting in the above panic since the group key has been zeroed out.
This panic has been observed with athn(4) by Jan Stary and Ted Patterson,
and Ted has confirmed that this patch fixes the problem.
ok kettenis@ (with the caveat that it's been a long time since he put our
AP-side powersave support into a working state)
Fix ifconfig "media:" line for 11n wifi interfaces during and after bgscan.2020-04-08T09:34:29Zstspstsp@openbsd.org2020-04-08T09:34:29Zurn:sha1:c72ef0165c2337cba4a37a3208799b6f4fa5bf18
Media was displayed as e.g. "autoselect (OFDM6)" even though 11n was active
because the current media mode is changed to AUTO for background scanning
and was never switched back to 11N.
ok mpi@ pirofti@
If join is connected to an AP, remove the node from the cache so we properly2020-01-15T09:34:27Zphesslerphessler@openbsd.org2020-01-15T09:34:27Zurn:sha1:26bb14d9c773eb86f0cada3cb60d0328095d751a
reconnect to the AP
OK stsp@
If the new candidate AP found after a background scan has an RSSI level2019-12-29T14:00:36Zstspstsp@openbsd.org2019-12-29T14:00:36Zurn:sha1:05e5c69149cd9b1ca6422ddf55a7e2d8ef13bdf2
that will also trigger background scans, remain with the current AP.
Avoids ping-pong in environments where APs are tuned for low transmit
range, such as 36c3.
ok phessler benno
Stop connecting to available open wifi networks when the interface is put up.2019-11-10T09:09:02Zstspstsp@openbsd.org2019-11-10T09:09:02Zurn:sha1:dc90783b903847c6770f44144ca24f6efe4fd536
From now on, this behaviour must be explicitly enabled with ifconfig join "".
ok sthen jcs deraadt
Give access points which fail to AUTH or ASSOC less priority during2019-11-09T13:21:04Zstspstsp@openbsd.org2019-11-09T13:21:04Zurn:sha1:6b9ba65ed87f3976b0f260f5a480959a6bfd9ec0
the next selection of networks from the join list. Prevents endless
attempts to connect to an AP which is out of reach but still somehow
manages to get a beacon or two across to us during scan.
Tested with wifi networks at the University of Bucharest.
Makes switching wifi networks possible after walking to a different
room without having to down/up the interface or suspend/resume.
ok phessler@
Clear the unref callback function pointer when cleaning up an ieee80211_node.2019-11-09T09:03:24Zstspstsp@openbsd.org2019-11-09T09:03:24Zurn:sha1:83f8f70dcaaa5a75e02c1d9d9217d7aa922304d0
ok mpi@
Make background scans less frequent if we keep choosing the same AP.2019-10-31T11:03:43Zstspstsp@openbsd.org2019-10-31T11:03:43Zurn:sha1:0140f0f140fb476fcd62892bff1f6957bc05c775
This helps a bit in situations where a single AP is used and background scans
are causing packet loss, as seen with Jesper Wellin's Broadcom-based AP and my
Android phone in hotspot mode. This is not a proper fix but our background scan
frequency against a single AP was much higher than needed anyway.
Tested by jan, job, benno, Tracey Emery, Jesper Wallin
Make net80211 expose reasons for association failures to userland and have2019-09-02T12:54:21Zstspstsp@openbsd.org2019-09-02T12:54:21Zurn:sha1:799b58a52e554bb085a530cf8292c3c1c2519cc3
ifconfig display them in 'scan' output and on the ieee80211 status line if
the failure is applicable to an already selected AP (e.g. wrong WPA key).
This will hopefully reduce the amount of help requests for what often
turn out to be trivial misconfiguration issues that were previously
hard to diagnose without debug mode.
ifconfig must be recompiled with the new ieee80211_ioctl.h to stay in
sync with the kernel. A full 'make build' will do the right thing!
Very helpful input by mpi@ and deraadt@