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 <[email protected]> wrote: > > 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 wireless network > stack and the athn0 driver, what's different is that I use wpa3 > and hostapd on the FreeBSD install as well as no graphical > drivers at all unlike in OpenBSD (the default in FreeBSD install). > Hopefully, this might help someone to troubleshoot this. > > On Wed, Apr 3, 2024 at 10:32 AM ofthecentury <[email protected]> wrote: > > > > 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 frames. Is that where an authenticated user would be > > saved? Or is there something above net80211 that will handle that? > > > > On Wed, Apr 3, 2024 at 12:22 AM Peter J. Philipp <[email protected]> > > wrote: > > > > > > 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 > > > machine like a laptop into monitor mode and use the -Y flag with tcpdump > > > to capture what's going on at a frequency. Beware of beacons, they > > > clutter > > > up the frequencies. > > > > > > > I do know German, I'll see if I can get the book, or if I even need it > > > > after I poke around. > > > > > > Here is the ISBN along with all my techie books that I was going to donate > > > away. Thankfully noone wanted them because I was going to go to college > > > but didn't have the highschool marks to get accepted at the course I > > > wanted > > > to take. http://mainrechner.de/Buecher2024/ > > > > > > > My OpenWrt router got fried by a remote electric directional beam of a > > > > digital weapon from an apartment across the wall a few years ago. Even > > > > a simple digital thermometer near the router was getting broken and > > > > showing weird stuff on display. How can this be legal? We must mandate > > > > RF detectors in all homes for everyone's electronic device safety and > > > > personal safety. > > > > > > Yes radio can get really nasty especially when it's directed with a > > > parabolic > > > dish or phased array antenna. I have images in my head, that the military > > > has on trucks with huge parabolic dishes. Those were intended to "zap" > > > civil > > > unresters and make them disperse. Whether they are torture or not is not > > > in my scope, but I understand that when a human can get zapped at 60 feet > > > that > > > a electronic device can get zapped as well. > > > > > > I don't know what your laws are where you live, but I tend to agree with > > > that > > > statement. Eventually there may be sensors on your cellphone/smartphone, > > > is > > > what I suspect because I've seen google talks about measuring > > > radioactivity > > > with geiger counters built into android phones, so it definitely is going > > > around the heads of implementors. > > > > > > > I'm 100% cabled at home for a while now too, but trying to see if I > > > > can make this hostap work in OpenBSD, since it's the golden standard > > > > for security? > > > > > > > > Thanks again for your help. > > > > > > No problem, and my pleasure. I once had this idea to make 3 types of > > > accesses > > > in my home once. One would be an open access point (like freifunk maybe), > > > 2nd would be password protected with a QR code displaying the password > > > inside > > > the apartment on a digital photo picture frame, changing the password > > > daily or > > > semi-daily. And finally one for private communications. They could > > > potentially all be on the same hardware but vlan'ed and firewalled to > > > sh*ts, > > > including IPSEC. Strangers at the door can use the open access point, > > > friends > > > inside the apartment can use the encrypted 2nd access point and close > > > friends > > > such as spouse or girlfriend would be allowed on the highest layer of > > > private > > > Wifi. The only problem is getting friends these days is hard for loners > > > like > > > myself, so there is really no point for me. But if I had frequent guests > > > and > > > such I'd want such a system. > > > > > > I remember years ago OpenBSD devs were suggesting to "just buy a consumer > > > AP". > > > But times can change. Maybe in the future some time :P, it's still > > > unwritten. > > > Since I had wifi gear there was a guy named Bergamini who was very > > > skilled in > > > writing drivers. He left though, and since then the wifi stack afaik has > > > been > > > nurtured mostly by Stefan Sperling and anyone else who has the skill to > > > help > > > him. I'm obviously missing some names but these are the people who > > > impressed > > > me. Since last week I've been wanting to port OpenBSD to Pine64 Ox64. > > > > > > The idea is that we'd let the SoC run two OS's in parallel asynchronously > > > since I think the 64-bit C906 core doesn't have access to the Wifi. Some > > > people are lightly helping and I asked them to get familiar with Apache > > > NuttX > > > which could run on the 32-bit cores and we'd communicate somehow between > > > the OS's (perhaps a mailbox driver or shared memory). Anyhow I was sorta > > > side-tracked by easter weekend, and hope to pick up where I left off by > > > friday. > > > > > > Anyhow long typing, I'm gonna call it a day and go to sleep. Later! > > > > > > -pjp
