Date: Tue, 19 Aug 2025 17:17:20 -0700 From: Adrian Chadd <adrian@freebsd.org> To: "Bjoern A. Zeeb" <bz@freebsd.org> Cc: Andriy Gapon <avg@freebsd.org>, FreeBSD wireless mailing list <wireless@freebsd.org> Subject: Re: rtwn/rtl8821au: strange issue with 5GHz channels Message-ID: <CAJ-VmokG4sds%2Bc%2B2XQLQ%2BfKQRrhHN6VzSy9KmFBmdskoDBVnug@mail.gmail.com> In-Reply-To: <p84s6005-no21-r42o-3n09-qr49s0n746s9@SerrOFQ.bet> References: <4cb1c608-d534-4bfb-8cc9-92251000e0fd@FreeBSD.org> <CAJ-VmonQ7x%2BX=g5Gd4ZsJ1Ku3uTNKBEH34D=n8Xnw1nkAKudrw@mail.gmail.com> <9243aad2-20d1-4c17-8f9a-f5b682eb1f85@freebsd.org> <b7453c2b-13dc-4864-a899-2cfaf36bc5b1@FreeBSD.org> <p84s6005-no21-r42o-3n09-qr49s0n746s9@SerrOFQ.bet>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, 19 Aug 2025 at 16:39, Bjoern A. Zeeb <bz@freebsd.org> wrote: > On Tue, 19 Aug 2025, Andriy Gapon wrote: > > > On 19/08/2025 18:33, Andriy Gapon wrote: > >> Weird thing... I set the AP to 20MHz: > >> # iw dev phy1-ap1 info > >> Interface phy1-ap1 > >> ifindex 28 > >> wdev 0x10000000b > >> addr 7a:d2:94:80:1f:ec > >> ssid HolyLan > >> type AP > >> wiphy 1 > >> channel 149 (5745 MHz), width: 20 MHz, center1: 5745 MHz > >> txpower 20.00 dBm > >> multicast TXQ: > >> qsz-byt qsz-pkt flows drops marks overlmt > hashcol > >> tx- bytes tx-packets > >> 0 0 67 0 0 0 > 0 > >> 20434 67 > >> > >> Then I reset the client and tried again and it still wants to use > channel > >> 153: > >> > >> wpa_supplicant[16180]: wlan0: Trying to associate with > 7a:d2:94:80:1f:ec > >> (SSID='HolyLan' freq=5765 MHz) > >> wpa_supplicant[16180]: wlan0: Authentication with 7a:d2:94:80:1f:ec > timed > >> out. > >> wpa_supplicant[16180]: wlan0: Added BSSID 7a:d2:94:80:1f:ec into ignore > >> list, ignoring for 10 seconds > >> wpa_supplicant[16180]: wlan0: CTRL-EVENT-DISCONNECTED > >> bssid=7a:d2:94:80:1f:ec reason=3 locally_generated= > > > > After a couple of dozens of retries the correct channel / frequency was > > finally selected and connection was successfully established. > > That's something for Adrian having worked on that driver. > Yeah, that's hella odd and i don't like it. I'll go try to reproduce it here. This just also really keeps reminding me/us that we sorely need a channel config and regulatory support uplift during -16 development. -adrian > > > But it looks like the connection is 'a', not 'ac' that I expected? > > Yes given you showed in the list channels yourself that there was no VHT > given regdomain.xml for NONE/UA does not know about that. > > UA is close but not exactly matching the current ETSI regdomain > definition (careful, you are not allowed as many mW in some case, etc.) > from > what I can see in what linux wireless-regd has. > > > > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > > options=200001<RXCSUM,RXCSUM_IPV6> > > ether 08:be:ac:3e:a9:ee > > inet 192.168.0.130 netmask 0xffffffff broadcast 192.168.0.130 > > groups: wlan > > ssid HolyLan channel 149 (5745 MHz 11a) bssid 7a:d2:94:80:1f:ec > > regdomain NONE country UA indoor authmode WPA2/802.11i privacy ON > > deftxkey UNDEF AES-CCM 2:128-bit txpower 23 bmiss 7 mcastrate 6 > > mgmtrate 6 scanvalid 60 wme roaming MANUAL > > parent interface: rtwn0 > > media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11a > > status: associated > > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > > > Log: > > wpa_supplicant[2564]: wlan0: Trying to associate with 7a:d2:94:80:1f:ec > > (SSID='HolyLan' freq=5745 MHz) > > wpa_supplicant[2564]: wlan0: Associated with 7a:d2:94:80:1f:ec > > wpa_supplicant[2564]: wlan0: WPA: Key negotiation completed with > > 7a:d2:94:80:1f:ec [PTK=CCMP GTK=CCMP] > > wpa_supplicant[2564]: wlan0: CTRL-EVENT-CONNECTED - Connection to > > 7a:d2:94:80:1f:ec completed [id=0 id_str=] > > kernel: wlan0: link state changed to UP > > > > > > > > -- > Bjoern A. Zeeb r15:7 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 19 Aug 2025 at 16:39, Bjoern A. Zeeb <<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, 19 Aug 2025, Andriy Gapon wrote:<br> <br> > On 19/08/2025 18:33, Andriy Gapon wrote:<br> >> Weird thing... I set the AP to 20MHz:<br> >> # iw dev phy1-ap1 info<br> >> Interface phy1-ap1<br> >> ifindex 28<br> >> wdev 0x10000000b<br> >> addr 7a:d2:94:80:1f:ec<br> >> ssid HolyLan<br> >> type AP<br> >> wiphy 1<br> >> channel 149 (5745 MHz), width: 20 MHz, center1: 5745 MHz<br> >> txpower 20.00 dBm<br> >> multicast TXQ:<br> >> qsz-byt qsz-pkt flows drops marks overlmt hashcol <br> >> tx- bytes tx-packets<br> >> 0 0 67 0 0 0 0 <br> >> 20434 67<br> >> <br> >> Then I reset the client and tried again and it still wants to use channel <br> >> 153:<br> >> <br> >> wpa_supplicant[16180]: wlan0: Trying to associate with 7a:d2:94:80:1f:ec <br> >> (SSID='HolyLan' freq=5765 MHz)<br> >> wpa_supplicant[16180]: wlan0: Authentication with 7a:d2:94:80:1f:ec timed <br> >> out.<br> >> wpa_supplicant[16180]: wlan0: Added BSSID 7a:d2:94:80:1f:ec into ignore <br> >> list, ignoring for 10 seconds<br> >> wpa_supplicant[16180]: wlan0: CTRL-EVENT-DISCONNECTED <br> >> bssid=7a:d2:94:80:1f:ec reason=3 locally_generated=<br> ><br> > After a couple of dozens of retries the correct channel / frequency was <br> > finally selected and connection was successfully established.<br> <br> That's something for Adrian having worked on that driver.<br></blockquote><div><br></div><div>Yeah, that's hella odd and i don't like it. I'll go try to reproduce it here.</div><div>This just also really keeps reminding me/us that we sorely need a</div><div>channel config and regulatory support uplift during -16 development.</div><div><br></div><div><br></div><div><br></div><div>-adrian</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> <br> > But it looks like the connection is 'a', not 'ac' that I expected?<br> <br> Yes given you showed in the list channels yourself that there was no VHT<br> given regdomain.xml for NONE/UA does not know about that.<br> <br> UA is close but not exactly matching the current ETSI regdomain<br> definition (careful, you are not allowed as many mW in some case, etc.) from<br> what I can see in what linux wireless-regd has.<br> <br> <br> > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500<br> > options=200001<RXCSUM,RXCSUM_IPV6><br> > ether 08:be:ac:3e:a9:ee<br> > inet 192.168.0.130 netmask 0xffffffff broadcast 192.168.0.130<br> > groups: wlan<br> > ssid HolyLan channel 149 (5745 MHz 11a) bssid 7a:d2:94:80:1f:ec<br> > regdomain NONE country UA indoor authmode WPA2/802.11i privacy ON<br> > deftxkey UNDEF AES-CCM 2:128-bit txpower 23 bmiss 7 mcastrate 6<br> > mgmtrate 6 scanvalid 60 wme roaming MANUAL<br> > parent interface: rtwn0<br> > media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11a<br> > status: associated<br> > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL><br> ><br> > Log:<br> > wpa_supplicant[2564]: wlan0: Trying to associate with 7a:d2:94:80:1f:ec <br> > (SSID='HolyLan' freq=5745 MHz)<br> > wpa_supplicant[2564]: wlan0: Associated with 7a:d2:94:80:1f:ec<br> > wpa_supplicant[2564]: wlan0: WPA: Key negotiation completed with <br> > 7a:d2:94:80:1f:ec [PTK=CCMP GTK=CCMP]<br> > wpa_supplicant[2564]: wlan0: CTRL-EVENT-CONNECTED - Connection to <br> > 7a:d2:94:80:1f:ec completed [id=0 id_str=]<br> > kernel: wlan0: link state changed to UP<br> ><br> ><br> ><br> <br> -- <br> Bjoern A. Zeeb r15:7</blockquote></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokG4sds%2Bc%2B2XQLQ%2BfKQRrhHN6VzSy9KmFBmdskoDBVnug>