Re: iwlwifi/AX210: country AU maps to ROW and omits common Australian 5 GHz channels 36-48

I decided to reapply the patch, this time using the regdomain.xml file 
from the source tree (currently on 1600018).

While I got it connect to Channel 100 it is not connecting at 11ac.


wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=0
ether xx:xx:xx:xx:xx:xx
groups: wlan
ssid xx channel 100 (5500 MHz 11a) bssid xx:xx:xx:xx:xx:xx
regdomain APAC2 country AU authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit AES-CCM ucast:128-bit txpower 26
bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 wme roaming MANUAL
parent interface: iwlwifi0
media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a
status: associated
nd6 options=829<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL,STABLEADDR>


On 6/17/26 10:34, Tamás Nagy wrote:
> Hi Ben,
>
> I tested this with my setup. It works in my setup (patch applied). AP
> Xiaomi Mi Router AX3000T (OpenWrt U-Boot layout) Xiaomi Mi Router
> AX3000T (OpenWrt U-Boot layout) Channel setup is what you suggested
>
>
> wlan0: flags=1028943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,PPROMISC,LOWER_UP>
> metric 0 mtu 1500
> options=100000<NETMAP>
> ether xx:xx:xx:xx:xx:x
> groups: wlan
> ssid Kicsikucko channel 100 (5500 MHz 11a vht/80+) bssid xx:xx:xx:xx:xx:xx
> regdomain APAC2 country AU authmode WPA2/802.11i privacy ON
> deftxkey UNDEF AES-CCM 2:128-bit AES-CCM ucast:128-bit txpower 26
> bmiss 10 mcastrate 6 mgmtrate 6 scanvalid 60 bgscan bgscanintvl 300
> bgscanidle 250 roam:rssi 7 roam:rate MCS 1 ampdulimit 64k
> ampdudensity 2 -amsdutx amsdurx shortgi -stbc -ldpc -uapsd vht vht40
> vht80 -vht160 -vht80p80 wme roaming MANUAL
> parent interface: iwx0
> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ac
> status: associated
> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>
>
> On Wed, 17 Jun 2026 at 12:14, Adrian Chadd<adrian@freebsd.org> wrote:
>> When you say "won't connect" what do you mean?
>>
>> does it see the DFS channels in the list there but it ignores them?
>>
>> Or it sees them, tries to associate but it can't associate?
>>
>>
>>
>> -adrian
>>
>> On Tue, 16 Jun 2026 at 17:21, Ben Hutton<ben@benhutton.com.au> wrote:
>>> Hi Bjoern,
>>>
>>> It just won't connect on the DFS channels. When I check the channels I get the following:
>>>
>>> ifconfig wlan0 list txpower
>>> Channel   1 : 2412 MHz 30.0 reg 30  Channel  68 : 5340 MHz 23.0 reg 23
>>> Channel   2 : 2417 MHz 30.0 reg 30  Channel  96 : 5480 MHz 26.0 reg 26
>>> Channel   3 : 2422 MHz 30.0 reg 30  Channel 100 : 5500 MHz 30.0 reg 30
>>> Channel   4 : 2427 MHz 30.0 reg 30  Channel 104 : 5520 MHz 30.0 reg 30
>>> Channel   5 : 2432 MHz 30.0 reg 30  Channel 108 : 5540 MHz 30.0 reg 30
>>> Channel   6 : 2437 MHz 30.0 reg 30  Channel 112 : 5560 MHz 30.0 reg 30
>>> Channel   7 : 2442 MHz 30.0 reg 30  Channel 116 : 5580 MHz 26.0 reg 26
>>> Channel   8 : 2447 MHz 30.0 reg 30  Channel 132 : 5660 MHz 30.0 reg 30
>>> Channel   9 : 2452 MHz 30.0 reg 30  Channel 136 : 5680 MHz 30.0 reg 30
>>> Channel  10 : 2457 MHz 30.0 reg 30  Channel 140 : 5700 MHz 30.0 reg 30
>>> Channel  11 : 2462 MHz 30.0 reg 30  Channel 144 : 5720 MHz 30.0 reg 30
>>> Channel  36 : 5180 MHz 23.0 reg 23  Channel 149 : 5745 MHz 36.0 reg 36
>>> Channel  40 : 5200 MHz 23.0 reg 23  Channel 153 : 5765 MHz 36.0 reg 36
>>> Channel  44 : 5220 MHz 23.0 reg 23  Channel 157 : 5785 MHz 36.0 reg 36
>>> Channel  48 : 5240 MHz 23.0 reg 23  Channel 161 : 5805 MHz 36.0 reg 36
>>> Channel  52 : 5260 MHz 23.0 reg 23  Channel 165 : 5825 MHz 36.0 reg 36
>>> Channel  56 : 5280 MHz 23.0 reg 23  Channel 169 : 5845 MHz 36.0 reg 36
>>> Channel  60 : 5300 MHz 23.0 reg 23  Channel 173 : 5865 MHz 36.0 reg 36
>>> Channel  64 : 5320 MHz 23.0 reg 23
>>>
>>>
>>> The access point is configured for Channels 100 - 112 with a 80MHz channel width.
>>>
>>> The regdomain has the following entry that I've been playing with that provides the 100 - 112 range.
>>>
>>>      <band>
>>>        <freqband ref="AC2_5500_5580_80"/>
>>>        <maxpower>30</maxpower>
>>>        <flags>IEEE80211_CHAN_PASSIVE</flags>
>>>        <flags>IEEE80211_CHAN_DFS</flags>
>>>      </band>
>>>
>>> ....
>>>
>>> <freqband id="AC2_5500_5580_80">
>>>      <freqstart>5500</freqstart> <freqend>5580</freqend>
>>>      <chanwidth>80</chanwidth> <chansep>20</chansep>
>>>      <flags>IEEE80211_CHAN_A</flags>
>>>      <flags>IEEE80211_CHAN_HT40</flags>
>>>      <flags>IEEE80211_CHAN_VHT80</flags>
>>> </freqband>
>>>
>>>
>>> I have drafted this together with the following resources:
>>>
>>> https://wisp.net.au/info/5ghz-channel-spectral-width-in-australia-6.html
>>> https://en.wikipedia.org/wiki/List_of_WLAN_channels#cite_note-N5001000-67
>>>
>>> I'm not sure about the maxpower level. I'm basing this on the following from Claude. I haven't had a chance to verify this yet (Sometimes it's helpful...):
>>>
>>> Australian DFS Power Limits
>>>
>>> According to ACMA regulations and AS/NZS 4268, Australian 5 GHz bands have these requirements:
>>>
>>> 5150–5250 MHz: 200 mW EIRP (~23 dBm)
>>> 5250–5350 MHz: DFS required, 200 mW (~23 dBm)
>>> 5470–5725 MHz: DFS required, 1000 mW (~30 dBm)
>>>
>>>
>>>
>>> Note: I'm currently trying to understand how this works so if you have any recommendations of what to read, or can point me in the direction of where in the codebase to look where I can further understand how this all works. Happy to help where I can.
>>>
>>> Kind regards
>>> Ben
>>>
>>> On 6/15/26 17:53, Bjoern A. Zeeb wrote:
>>>
>>> On Mon, 15 Jun 2026, Ben Hutton wrote:
>>>
>>> The updated patch that Bjoern supplied works for non DFS channels. I've been experimenting with getting the DFS channels working.
>>>
>>>
>>> Hmm interesting.  In what way are they not working?
>>>
>>> The one thing I can think of which can be a problem is if your AP is set to
>>> automatically select a channel and switches due to detection while you are
>>> associated as LinuxkPI is not handling CSA currently.  I got one report of
>>> that from someone in Germany a while ago.
>>>
>>> Let me know if I can help.
>>>
>>> /bz
>>>