In case it is of any help to anyone. I tried 11n on a ar9271 a few weeks ago and also an ar2133. Both would give athn0: device timeouts but the usb ar9271 needed a ifconfig down up to recover whereas the card recovered by itself. Using 11g made them far less likely and whilst I have hardly used the 11b ssid, I haven't had any with 11b on the 9271 so far.
Also after using 11n and getting multiple resets I had to plug the card into another laptop to get the firmware to load again without saying could not read ROM, even after reboots. So maybe some state is kept on OpenBSD or more likely perhaps it was unplugged for long enough to clear the cards memory or something. Thanks for working on the WIFI stack, BTW. I'm sure it is appreciated by many. If you want me to test any snapshots, let me know. On 20 Mar 2017 12:36, "Stefan Sperling" <s...@stsp.name> wrote: > On Sun, Mar 19, 2017 at 03:14:05PM +0000, Tom Murphy wrote: > > Hi, > > > > I'm running my athn(4) device in hostap mode. I noticed, when it's set > to > > 802.11n, I get higher latency (pinging the OpenBSD AP) and disconnections > > every few minutes. The Wifi clients are Linux-based (Android and Debian). > > > > When I set it back to 802.11g (mode 11g) it's fine again. > > > > I have athn0 using powersave on too, and when the client has powersave > mode > > on, the latency goes up and network performance also drops. As soon as I > turn > > powersave mode off on the client, it goes from being anywhere between > > 600-1000 ms per ping, to 1-2ms per ping. > > > > Is there some issue with 802.11n clients when OpenBSD is in hostap 11n > mode? > > Also is powersave mode a problem. Has anyone tested these and come up > with > > a good solution? I've tried different channels (can't try 5 GHz because > none > > of my devices support it except the hostap device) > > Thank you for documenting this. I have not tested power-save mode yet. > The OpenBSD clients I use do not support it. > > It sounds like this is something that needs more work. > > > Is there anything I can try to get 802.11n stable? > > Unless you wish to debug and fix the code yourself, it sounds like the > best you can do for now is to disable power saving.
