On Tue, 19 Aug 2025 at 16:39, Bjoern A. Zeeb <b...@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
