On Mon, Mar 23, 2020 at 10:34:45AM +0000, Kevin Chadwick wrote: > On 2020-03-23 10:12, Stefan Sperling wrote: > > You should see "!wpakey" in 'ifconfig iwn0' if you keep trying to > > connect with a bad key. > > > > And message 2/4 failing almost always implies a wrong key. > > Ok, perhaps I missed it. > > I do seem to still have an issue connecting to the OpenBSD athn0 access point. > I do have stayauth and nobridge enabled, though I have tried without them > (weeks ago). > My phone takes a while to connect to it and play store seems to stall on this > OpenBSD access point only on my particular phone, so I might try swapping the > athn > modem out and will open another bug, if it continues. I assume it is a > completely > different issue with 'device timeout' as shown below. I have triple checked > the key.
I cannot really work with the information you've posted in this thread. Please avoid spreading information across several quick messages, assuming others will piece it all back together. And please avoid mixing up several problems in one discussion thread. It's all quite confusing and takes a lot of effort to follow. It's an OpenBSD AP which offers extensive logging in debug mode and has tcpdump installed, yet you are showing us no information from this AP, only a log from one of the clients? The bugs@ list is intended for in-depth bug reports with a clear problem description and as much hard data as possible to support the problem hypothesis. Not random snippets of info with many open questions.
