@danpawlik thanks for this support ...
Packages : modemmanager luci-proto-modemmanager , mostly for some modems yes its working ,and others no...
Need
Package : kmod-mtk-t7xx kmod-mhi-net kmod-mhi-wwan-ctrl kmod-usb-serial-wwan kmod-usb-net-qmi-wwan usb-modeswitch kmod-usb-serial-option
@KFO which one is missing?
once again: kmods needs to be added into the image, other packages you can install from OpenWRT repo. If you think, that I will create an image with all packages just for you - you are wrong. In that case, please read documentation or create a GitHub workflow and apply all what you need. It is not difficult, it just require to make something, not expect.
Edit: issue that the 6GHz is not working is because there is an error in the config. I assume that Janusz has tested own change on main branch, but after bumping hostapd to new version in my branch, the config seems to be broken or need update of the related scripts.
Later I will do a build that will revert changes related to hump hostapd
Yeah I don't need eht modes, just 6e he160 channels on 6g is good enough.
I would prefer an mt76 build with fully functional wifi6 than wifi7. Mainly due to issues with eht320 and lack of wifi7 clients. IME well tuned wifi6 clients are able to push 1.5gbit on 5gh 160 channels which is more than adequate.
I cannot agree, 5ghz seems crowded more than before. It is usable only on short distance (160), and you still hit radar frequencies. 6Ghz is silent (at least around me, and having 3 clients make sense to concentrate also on this. Just my 5 cents.
No radar, but even shorter distance (or more precise, worse wall/ object penetration).
--
Don't get me wrong, I'm not against 6 GHz - on the contrary.
when the 160 MHz channel width is enabled, there are only two continuous blocks of channels that you can actually use - these are channels 36 to 64 and 100 to 128 (DFS) where 116-132 are weather radars...I think at least in EU is like that. On other hand 80Mhz should be enough. True, 5 and 6 is rubbish against the walls 
Buy a Bananapi R3 :))
6ghz is working EHT & HE although EHT is very very slow. Also, only could get MTK and RTL clients to connect ... Intel (AX210 and BE200) clients can't find the router.
Check my repo ... but yes there's useful stuff on the mtk feeds.
Ah, right. I take the config from @Janusz for the wireless and it seems to work on Intel be200.
config wifi-device 'radio2'
option type 'mac80211'
option path 'soc/11300000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0+2'
option band '6g'
option channel '1'
option htmode 'EHT320'
option country 'JP'
option cell_density '0'
option log_level '1'
config wifi-iface 'default_radio2'
option device 'radio2'
option network 'lan'
option mode 'ap'
option ssid 'Majki_6G'
option encryption 'sae'
option key 'testkey'
option ocv '0'
Alternatively we could just add a test wireless-regdb without restrictions for testing, for example mine looks like this:
country 00:
(2402 - 2494 @ 40), (30)
(5030 - 5925 @ 160), (30)
(5990 - 7125 @ 320), (30)
country AD:
(2402 - 2494 @ 40), (30)
(5030 - 5925 @ 160), (30)
(5990 - 7125 @ 320), (30)
etc.
This will satisfy chipsets that don't like custom countries on the AP side like 00 or ZZ. So it will allow you to set any country without restrictions. For testing
Patch:
Compiled .ipk package:
This replaces /target-aarch64_cortex-a53_musl/wireless-regdb-2024.07.04/db.txt
So you checked the 6g operation with the intel be200 adapter? It's a pity I can't check, because I live in Russia and my intel be200 adapter is blocked from working with 6g frequencies. I ordered mediatek mt7927, when it arrives I will test the 6g operation.
Excellent solution, maybe my intel be200 will work if I use this .ipk?!
No, the BE200 will enable 6 GHz band only if the majority of discovered APs have the 'correct' region. Create a dozen of virtual APs (no matter which band) with the US region and you'll see 6 GHz. Still, there's no EHT support in Windows driver yet, and in Ubuntu you might have to launch a scan for networks in Terminal before the 6 GHz one appears in GUI.
Did you try to check on Linux or you are using Windows?
Just FYI, wifi 6GHz is not working on Windows 10.
Yes, i check it on linux and windows 11 latest release preview and my intel be200 not see 6g bands, maybe, because intel used LAR technology and block 6g usage in Russia country. Later i test with created more than 10 virtual AP with region US, maybe after this be200 see 6g.
I haven’t understood this anal low watt thing , the yearly cost for something consuming 30w is <30$. Is it that big of a deal if it’s $10 or $30 in yearly cost to call it “ exorbitant power consumption”
I did some extra research on Intel wireless NICs. According to Intel, since AX210 all of them have updated firmware with up to date regional restrictions. But they also look into BIOS on the motherboard for the certification for each region. I've found mentions of new regions being added to the 6 GHz list in patch notes for some laptop BIOSes. But most laptop and motherboard manufacturers didn't bother. I guess now that 6 GHz routers become widely available a lot of people who have previously bought 'future-proof' Intel NICs are in for a surprise.
Intel is a garbage choice for NICs anyway, and it didn't start here.
Both LAN and wireless.
Since the 802.11n times their adapters were always lacking or crippled.
Yes, they are cheap, and usually integrated in laptops, but that's a bad
choice if you want good performance.
I have to totally agree with you. People buy a dev board(!) with first ever WiFI7 support and expect it to be:
This is simply not how it works, on many levels.
Yes, I get that a device that is not commercially optimized will consume a few more watts. Still didn’t answer my question? You are making your kvetching arguments based on a few watts difference? Is it a question of personal fixation regarding w/performance or real life issues?