On Wed, 30 Apr 2025 at 20:40, Adrian Chadd <adr...@freebsd.org> wrote:
I think there's a bug in whether I'm /transmitting/ VHT80 frames due to > some net80211 > code I wrote recently, and I'll go fix that soon. > > But, ifconfig shows it detects fine for me with rtwn with today's -HEAD: > > $ ifconfig wlan0 > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=200001<RXCSUM,RXCSUM_IPV6> > ether 54:af:97:ec:0a:e6 > inet 192.168.0.110 netmask 0xffffff00 broadcast 192.168.0.255 > inet6 fe80::56af:97ff:feec:ae6%wlan0 prefixlen 64 scopeid 0x2 > groups: wlan > ssid CACHEBOY_HOME channel 161 (5805 MHz 11a vht/80-) bssid > 9c:53:22:c7:43:9d > regdomain FCC country US authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 3:128-bit txpower 17 bmiss 7 mcastrate 6 > mgmtrate 6 scanvalid 60 ampdulimit 64k shortgi -stbc ldpctx -ldpcrx > -uapsd vht vht40 vht80 -vht160 -vht80p80 wme roaming MANUAL > parent interface: rtwn0 > media: IEEE 802.11 Wireless Ethernet VHT mode 11ac > status: associated > nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> > > .. i wonder if there is something odd going on for non-VHT operating modes? > Or other drivers that aren't setting ni_txrate? Hm. > > > Oops! https://reviews.freebsd.org/D50095 and https://reviews.freebsd.org/D50096 :-) -adrian
