Re: How is testing going?

From: Ben Hutton <ben_at_benhutton.com.au>
Date: Sun, 29 Mar 2026 23:46:09 UTC
Hi Bjoern,

The previous version I tested was from 
commit 74aec9f02d9d8fbde250da1ecc881729c8baf489. It was around 7th March.

I had to revert because the connection kept dropping out due to errors 
and would eventually crash the system. I sent through logs of it at the 
time. I can dig out the email if that helps.

Currently the main issue I'm having is connecting to access points at 
11ac when they are using channels above 100. Currently I have two access 
points. One is using channels 52,56,60,64 and the other 149,153,157,161. 
Currently my FreeBSD based laptop will only connect to the one with 
149-161 with 11ng, the other connects fine at 11ac.

I suspect this issue is due to missing entries in regdomain.xml so I'm 
currently experimenting with adding the following (generated by Claude 
Haiku 4.5) and adding it to the end of the 11ac in the APAC2 section:

  <band>
<freqband ref="AC2_5480_5700_20"/>
<maxpower>30</maxpower>
<flags>IEEE80211_CHAN_HT20</flags>
<flags>IEEE80211_CHAN_VHT20</flags>
<flags>IEEE80211_CHAN_DFS</flags>
    </band>


I haven't gotten as far as looking up the documentation around the 
frequency regulations in Australia yet but planning on.

I'm still currently testing it, however tests so far have the current 
driver hitting the same speeds as my M1 MacBook Pro. Also it has been a 
big step up in stability. So far over the last day I've had no dropouts 
once connected.

Will let you know if I have any further issues. Any advise on the 
channels issue above regarding testing, also any advise on where to get 
the information regarding the channels/frequency ranges?

Kind regards
Ben

On 3/29/26 23:56, Bjoern A. Zeeb wrote:
> On Sun, 29 Mar 2026, Ben Hutton wrote:
>
> Hi Ben,
>
>> Working allot better for me than the last update.
>
> Thanks for the feedback.  Can you elaborate a bit more?
>
> From which to which version did you go?
> What's currently troubling?
>
> Sorry for asking but I need the details in order to try to make it 
> even better ;-)
>
> /bz
>