I gave it a test, everything works (WiFi7/BE; Intel BE200 compatibility...) except 320Mhz (on radio2/6Ghz) and (kinda expected at this stage) MLO.
if you do a iw reg get
do you have 320Mhz showing ?
like this (5925 - 6425 @ 320), (N/A, 26), (N/A), NO-OUTDOOR
most likely you only have 160Mhz for the country you are using
pls use it just a workaround for something going on with github action ... and pls note it doesn't support mt7927
I use mt7927 on my computer as a client. I will test your build. Thank you.
This is what I get
root@OpenWrt:~# iw reg get
global
country FR: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 71000 @ 2160), (N/A, 40), (N/A)
French regulations allow broadcasting at 320Mhz though.
Should I use my country in the access points settings? If so, which country should I use?
UPDATE: US seems to work
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR
(57240 - 71000 @ 2160), (N/A, 40), (N/A)
yes US will work although with a very low power setting... JP from what others were saying on earlier posts works fine ...
I upgraded latest snapshot to your build with sysupgrade and it work!!! I change all bands name to OpenWrt, region to RU and able to connect to 6ghz band from my mediatek mt7927 wifi card on pc. Thanks for your work Rudy Andram.
This is amazing. I got 2.5 Gbps on the 6 GHz band now with the Qualcomm NCM865. On the other hand, Intel BE200 is pretty slow and unstable. Could be a Linux thing though, as Intel currently has no 802.11be support in Windows and I had to use Linux (latest 6.11 kernel) for BE200 specifically.
What speed You had on be200, i have one with mint mini hp pc but without antenas yet, this qualcom qcn865 is bit pricey yet.
In fact, I couldn't even establish a stable connection with a BE200. It barely worked to log into the router via SSH. Previously I tried it on a stock Banana Pi firmware, and it was roughly twice as slow as Qualcomm. It seems to me that Intel had a good reason to limit the Windows driver to WiFi 6E for now. Qualcomm is slower on Linux too though.
The BE200 works fine in Windows, you just have to install the latest intel wireless drivers, I can connect just fine in 802.11be mode.
I got 2.8gbps down and 900mbps up using the BE200 on Windows 11 24H2 using the 6Ghz band at 320Mhz.
Keep in mind that intel forces LAR (Location-Aware Regulatory) on its wireless NICs, it basically scans all the APs on the 2.4ghz and 5ghz band to determine what country you are in and only allows 6Ghz if it detects you are in a country that allows it (like the US, EU or Japan), otherwise it blocks it. Unfortunately it's not 100% accurate either. That's one reason I prefer Qualcomm NICs but those cost over twice the price and I had a lot of equipment to equip with WiFi 7, I also live in France so that's not too much of an issue for me.
Thanks, I didn't realize you could already use EHT320 on BE200. I'll give it a try. Release notes for the latest driver look like self-contradicting nonsense to me:
-
- The Wi-Fi 7 features are not currently available because of pending OS global availability (Windows 11* 24H2). As a result, after installing the drivers, the Intel® Wi-Fi 7 products function with Wi-Fi 6E capabilities on Windows 11*.
- The Intel’s Wi-Fi 7 products “Intel® Wi-Fi 7 BE201 ” and “Intel® Wi-Fi 7 BE200 ” will support Wi-Fi 6E + 320 MHz/4K QAM (known as EHT - Extremely High Throughput) by default when connecting to a Wi-Fi 7 wireless router/AP.
And yes, I have to spin up a dozen of virtual APs with the 'correct' region to create a majority for LAR whenever I'm testing the BE200 on a 6 GHz network.
So I tried the BE200 on Windows with the latest driver, and couldn't get over 0,5 Gbps because the NIC would only use 80 MHz bandwidth at best, never switching to 160 or 320 MHz. The country is set to JP as recommended above.
I had to upgrade to 24h2 and driver version 23.70.2.3 but yes at the moment very slow.
bear in mind that there is no mlo also qam (which packs more data on each slice) is limited to 1024 instead of 4096 on the mt7996e I also suspect that a lot is also to do with antennas both on the clients and and the router
btw - also wed i don't think is working ...
With the sysupgrade file you listed, for the first time. my mobile devices are able to connect to 6Ghz. On all my builds everything else would connect, but not my phones, and they are high end devices. So it sounds like your fix works on more than just the be200, keep up the good work. Tomorrow will use your repo to make a build of my own. Thanks for all your hard work.
I've also noticed that whenever I run a duplex test (iperf3 --bidir), Rx (to the router) always largely exceeds Tx (from the router), sometimes on the several orders of magnitude. That happens on wire too, and I wonder if this is normal behavior. As I haven't done in-depth network benchmarks before on different hardware, I have nothing to compare it with.
6ghz works on UK region too very nicely at 25dbi
note this is a wireless-regdb hack i did for testing ....
ah ok, but uk supports 6ghz anyways