On 2020/03/23 12:00, Kevin Chadwick wrote:
> On 2020-03-23 11:09, Stefan Sperling wrote:
> > 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
On 2020-03-23 11:09, Stefan Sperling wrote:
> 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.
>> "almost always implies a wrong key."
On Mon, Mar 23, 2020 at 10:34:45AM +, 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
On 2020-03-23 10:34, Kevin Chadwick wrote:
> Ok, perhaps I missed it.
BTW the key issue only affected the join, the key when testing connecting
otherwise was correct and is now working when it didn't before.
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
On Mon, Mar 23, 2020 at 10:04:13AM +, Kevin Chadwick wrote:
> On 2020-03-21 13:07, Kevin Chadwick wrote:
> > iwn seems to connect first time now with the last ? number of snapshots :)
> >
> > However, I have to run ifconfig iwn0 -joinlist first.
>
> You can close this bug now. It seems vi
On 2020-03-21 13:07, Kevin Chadwick wrote:
> iwn seems to connect first time now with the last ? number of snapshots :)
>
> However, I have to run ifconfig iwn0 -joinlist first.
You can close this bug now. It seems vi might have uppercased a letter in the
wpakey in hostname.iwn0 resulting in a
iwn seems to connect first time now with the last ? number of snapshots :)
However, I have to run ifconfig iwn0 -joinlist first.
On snapshots from atleast the last two weeks iwn seems to work reliably with the
same access point that it was failing with almost every time before. I still
have to run ifconfig -joinlist for it to work though.
On 2019-12-31 17:37, Kevin Chadwick wrote:
> After using 5G I tried 2.4 again and it worked first time (after a few scans
> where Ryo did not appear and the first still showed channel 44 whilst AP was
> switched).
>
> Clearly Ryo is dropping out of sight for some reason. Perhaps I will dwell on
On 2019-12-31 15:00, Stefan Sperling wrote:
> iwn(4) taking several scan attempts to find 5GHz APs is a known issue.
> The driver relies on the firmware for this. I have already tried to fix
> this problem but never got anywhere. If you want to give it another
> attempt then try playing with the
On Mon, Dec 30, 2019 at 12:19:13PM +, Kevin Chadwick wrote:
> >Synopsis: >joinlist enabled association repeatedly fails rather than once>
> >Category:
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6-current (GENERIC.MP) #517: Tue Dec 10
> 18:41:55
>Synopsis: joinlist enabled association repeatedly fails rather than once>
>Category:
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6-current (GENERIC.MP) #517: Tue Dec 10
18:41:55 MST 2019
13 matches
Mail list logo
