Hi @pesa1234 just a quick question seeing you have updated 3 different branches..
I'm currently using the r4.5.34 but with an older commit. Which is safest to try next? The 4.5.36 or 4.5.37? Or should I just stick with *.34 for now? My flint 2 is currently my primary router so can't do a lot of testing.
I'm testing... 36 is the correct one... As soon as I finished I clean the new branches
edit...
cleaned repo.
34 is stable with kernel 6.6.87
35 still testing with gcc14 and kernel 6.6.88
Did you make sure to select the region? With US selected you should be able to change the 2.4GHz to 30dBm and the 5GHz to 23dBm.
Snapshot just updated to 6.6.89 earlier today.
Yea in the stock gl firmware I have US as my region in openwrt but I still cant go beyond 20dbm and theres no 30dbm option. Even when I set it to 20dbm when I check wifiman its saying I'm only using 17dbm.
If you're using GL-Inet stock firmware, you cannot take any values in LUCI as honest, as the closed source MTK drivers do their own thing...
Getting on to snapshot or release - you should see in the US reg domain - 23 dBm for 5Ghz in the lower band, and 30 dBm for upper bands - in 2.4, 30 dBm should be available, again, if you're in the US reg domain
Appreciate it Im gonna be switching to pesa since GL limit their router to 20dbm. I guess they did it so its easier for them to comply with other countries regulation by .
Hi @pesa1234,
Is there an way to make the USB 3.0 flashdrive connected to MT6000 to use the USB 2.0 protocol on OpenWrt / Luci, as you suggested to them in 2024?
I noticed they added this feature on their 4.7 firmware.
Have you tried the procedure on this post? Or are you specifically requesting a GUI way to do this?
Can someone tell me why, when I manually set the channel to 40, there's a high chance that after a reboot it switches on its own to 36? And it stays stuck there at least until the device is restarted again or I try to force the change (but even doing both, it’s more likely to stay stuck on 36). Is it a bug or something the router is designed to do?
It's because when you select 160Mhz-wide, the channel ranges from 36 through 64, so selecting anything between there is actually setting the lowest channel to 36.
I understand, thanks for the clarification.
When selecting nothing, it should pick the center frequency on Channel 50, because the signal should spread to lower and higher frequencies, isn't?
For practical purposes, the control channel will reside in non-DFS channels when doing 160MHz on the lower end.
This is so that client stations can do discovery by active probing... if the control channel were running in a DFS channel, they would have to do passive scanning and the rest of the DFS procedures.
Sorry, I didn't know this post 
Just to make sure, before changing something:
On /sys/bus/usb/devices I can see USB1 and USB2
I know the post is saying to change the USB2, but this router has a single USB port. What is that USB1?
This change will not take effect until I reboot the router, correct?
Thanks! I'm still using Vanilla OpenWRT 24.10.1
Do you know if this recommendation is also valid for Vanilla OpenWRT 24.10.1 and why there is USB1 and USB2 in /sys/bus/usb/devices?
Sorry for asking, but because my current flashdrive is used to save some logs, I would like to make sure before changing something 
I don't know on vanilla, but it should work
Because you aren't following the advice make gives you.
Text in a codebox would be so much easier to read than an image, especially on mobile devices.
