Re: AX210 testing, problems connecting 11ac
- In reply to: Peter Miller: "Re: AX210 testing, problems connecting 11ac"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 24 Apr 2025 07:52:27 UTC
On Wed, 23 Apr 2025, Peter Miller wrote: Hi, Cc: Adrian for the mode vs. cahnnel > doas wlandebug -i wlan0 +scan > net.wlan.0.debug: 0x200000<scan> > > Is there something else to go along with that? Seems like I'm not getting > info you need with that one. It would log to console and may show up in a log file or dmesg. > OK.. now for something *new*. > > To make this reply even more confusing. I noticed while testing that > my 11ac connection quietly drops back to 11ng and/or even 11g when I'm > right in the middle of documenting things!! At least according to > ifconfig. When I run a speed test, I'm clearly not on 11g. > > I tested this a bit more, and when ifconfig initially says I'm on 11ng > I get corresponding speeds. If I get connected with 11ac and ifconfig > later shows it 11ng etc. I still get 11ac speeds. 300+ mbit. > > Below see reported 11g yet 300+ mbit speeds. > > ifconfig > lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384 > options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > groups: lo > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=0 > ether a0:80:69:f4:02:4f > inet 192.168.1.207 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::a280:69ff:fef4:24f%wlan0 prefixlen 64 scopeid 0x2 > inet6 2600:1702:6251:ef0:a280:69ff:fef4:24f prefixlen 64 autoconf pltime 3600 vltime 3600 > groups: wlan > ssid MaeAutoDetail channel 36 (5180 MHz 11a vht/80+) bssid 14:91:82:8b:5b:15 The channel is a 11a VHT/80 > regdomain FCC country US authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7 mcastrate 6 > mgmtrate 6 scanvalid 60 -ampdutx ampdurx ampdulimit 64k > -amsdutx amsdurx shortgi -ldpctx ldpcrx -uapsd vht vht40 vht80 vht160 > -vht80p80 wme roaming MANUAL > parent interface: iwlwifi0 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g but media is indeed 11g. Never seen this before. @adrian, this smells like a ieee80211_node_txrate gone wrong in ieee80211_rate2media() or some place around this? I further assume this has to do with IEEE80211_RATECTL_STATUS_FINAL_RATE not being used anywhere as feedback and net80211 having no idea what happens in the TX path otherwise on firmware based drivers? I wouldn't mind seeing an 11a or 11an there if no 11ac but an 11a channel and an 11g mode seems wrong. > status: associated > nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> If in doubt check the sysctl compat.linuxkpi.80211.wlan0 as well, which is closer to what firmware reports back to iwlwifi and LinuxKPI for now. /bz -- Bjoern A. Zeeb r15:7