Well, FreeBSD did do it after all. I only had 1 instance of
Wifi connectivity issue so far but zero wifi disconnects, like
I constantly had on OpenBSD. Shady.
On Thu, Apr 4, 2024 at 10:50 PM Peter N. M. Hansteen wrote:
>
> On Thu, Apr 04, 2024 at 07:22:01PM +0500, ofthecentury wrote:
> > Okkk,
On Thu, Apr 04, 2024 at 07:22:01PM +0500, ofthecentury wrote:
> Okkk, device hangups still occur. But there's some
> statistics at least in FreeBSD, by running
> `sysctl dev.ath`...anything like that in OpenBSD?
netstat -I $devicename with your choice of options will reveal at least some
Okkk, device hangups still occur. But there's some
statistics at least in FreeBSD, by running
`sysctl dev.ath`...anything like that in OpenBSD?
On Thu, Apr 4, 2024 at 6:54 PM ofthecentury wrote:
>
> Here's the solution to the athn0 driver constant cop outs.
> I installed FreeBSD and running a
Here's the solution to the athn0 driver constant cop outs.
I installed FreeBSD and running a wifi AP there seems smooth.
It might still start being wonky and might not last, but for now
there's been an immediate relief in symptoms, it seems.
Aside being on a different implementation of the
Frolicking through the net80211 jungle of the code, it looks like
the authenticated wifi client info is stored by the kernel and not exposed
to the userspace. But I'm still not 100% sure which source file does
it and what variable holds that. I see net80211 code that deals with
the association
On Tue, Apr 02, 2024 at 11:20:52PM +0500, ofthecentury wrote:
> I'll take a look at those locations, thanks. It might just be arp
> that's the authenticated client data store from the point of view of
> the wireless interface.
If you really want to debug what's going on I suggest you put another
I'll take a look at those locations, thanks. It might just be arp
that's the authenticated client data store from the point of view of
the wireless interface.
I do know German, I'll see if I can get the book, or if I even need it
after I poke around.
My OpenWrt router got fried by a remote
On Tue, Apr 02, 2024 at 10:31:59PM +0500, ofthecentury wrote:
> Where does OpenBSD keep a list of all wireless clients that have
> been authenticated? Not the dhcpd leases list. Actual wireless stations
> that have authenticated to an interface running in hostap mode. Not arp
> cache, is it?
>
>
Where does OpenBSD keep a list of all wireless clients that have
been authenticated? Not the dhcpd leases list. Actual wireless stations
that have authenticated to an interface running in hostap mode. Not arp
cache, is it?
This way I can cycle the wireless interface in hostap mode, which
resolves
On Sat, Mar 30, 2024 at 08:59:49PM +0500, ofthecentury wrote:
> And now something else happened, which seems like a big
> bug.
> athn0 sent a reason 6 deauthentication to my wifi client
> after I cycled the athn0 wifi interface!
> Reason 6 death is class 2 frame received from a nonauthenticated
>
And now something else happened, which seems like a big
bug.
athn0 sent a reason 6 deauthentication to my wifi client
after I cycled the athn0 wifi interface!
Reason 6 death is class 2 frame received from a nonauthenticated
station. Correct me if I'm wrong, but this sounds like a major
bug in the
Ok, I also just got reason 16 deauth happen. It says it was
sending msg 1/2 of the group key handshake to my wifi client,
it repeated it twice, and then the reason 16 deauth happened.
Then it says deauth to the wifi client and then wifi client was
purged from node cache. And now, the network SSID
Ok, I'm honing in on the details. There were different
things going on that were making it confusing. It still
might be different things going on, but there's a little
more info.
For now, it seems that I get the "athn0: device timeout"
that the man page for athn0 mentions. That resets athn0,
it
On Sat, Mar 30, 2024 at 05:44:32PM +0500, ofthecentury wrote:
> On Sat, Mar 30, 2024 at 5:29 PM Peter N. M. Hansteen wrote:
> >
> > why?
>
> I got "disassoc"s events in the log.
disassociations can happen for a number of different reasons. The event
should log a reason code, which you can look
On Sat, Mar 30, 2024 at 5:29 PM Peter N. M. Hansteen wrote:
>
> why?
I got "disassoc"s events in the log.
> The option to make the driver output more information is
>
> debug
I did this. "ifconfig athn0 debug." That's how I saw "disassoc"
events.
Anyone can send disassociation events to the
On Sat, Mar 30, 2024 at 04:19:31PM +0500, ofthecentury wrote:
> I have an athn0 wifi hotspot going.
> I think I get wifi dissassoc attacks.
why?
> I actually don't understand why cycling
> the interface gets my wifi device back
> online. Maybe it's actually a problem with
> the athn0? The logs
I have an athn0 wifi hotspot going.
I think I get wifi dissassoc attacks.
I know I'm just mitigating for now, but
I cycle the wifi interface periodically,
and that gets my client device back online.
I actually don't understand why cycling
the interface gets my wifi device back
online. Maybe it's
17 matches
Mail list logo
