On Sat, Jan 14, 2017 at 12:42:09PM +0000, Peter Kay wrote: > On 14 January 2017 at 12:02, Stefan Sperling <s...@stsp.name> wrote: > > On Sat, Jan 14, 2017 at 11:31:00AM +0000, Peter Kay wrote: > >> On 14 January 2017 at 11:23, Stefan Sperling <s...@stsp.name> wrote: > > > If one of your clients says it cannot authenticate, then this client may be > > trying to use TKIP/WPA1. You can enable wpa1 explicitly for such clients: > > ifconfig athn0 wpaprotos wpa1,wpa2 > > But understand that you'll be running broken WEP-grade crypto if you do > > this. > I'll upgrade to the latest snapshot. It's not a TKIP/WPA1 issue as a > reboot fixes it.
A reboot is very drastic and won't help with narrowing down the cause of your issue. Can you find a better way to unwedge the AP when it runs into problems? Does 'ifconfig iwn0 scan' on the client help? Does 'ifconfig athn0 down up' on the AP help?
