Flint 4 WiFi UK country code not available

Pro4TLZZ · August 30, 2026, 10:56pm

Yes it’s time to start with this farce. I was reading Flint 4 with Elan connect + inter net radio - #3 by miker and discovered that UK units ship with the WiFi country code set to DE.

Anyways this should be easy to set in the Gl-iNet admin console but I think Mediatek are making it harder to set currently because I didn’t find the UI setting till after running the commands.

I ran the below from a SSH session to my Flint 4

uci set wireless.MT7990_1_1.country='GB'
uci set wireless.MT7990_1_1.rd_region='GB'
uci set wireless.MT7990_1_2.country='GB'
uci set wireless.MT7990_1_2.rd_region='GB'
uci set wireless.MT7990_1_3.country='GB'
uci set wireless.MT7990_1_3.rd_region='GB'
uci commit wireless
wifi reload

When I went to verify this in Luci using the MTK tools I saw there is no UK country code option and it’s fallen back to the US country code.

Can we please have the UK regulatory values added along with the UK country code?

xize11 · August 31, 2026, 3:17am

Hi,

Please check here:

I think in your case it is probably not visible in the luci app, but by using the iw command I see it is set with your method inside the wireless config.

Can you confirm if the channels are actually valid for GB ?

PoweredByVeg · August 31, 2026, 6:37am

Why is it not part of the initial router setup in the GUI to select the country? This should have been implemented years ago. How many Gl-iNet users are running their routers with the incorrect country selected? I’m betting a lot!

bryer · August 31, 2026, 9:09am

Same with the Flint 3, mine was showing as DE, had to manually change mine as well.

Pro4TLZZ · August 31, 2026, 9:24am

Pro4TLZZ:

uci set wireless.MT7990_1_1.country='GB'
uci set wireless.MT7990_1_1.rd_region='GB'
uci set wireless.MT7990_1_2.country='GB'
uci set wireless.MT7990_1_2.rd_region='GB'
uci set wireless.MT7990_1_3.country='GB'
uci set wireless.MT7990_1_3.rd_region='GB'
uci commit wireless

Looks like it does work

iw reg get

global
country 98: DFS-ETSI
	(2400 - 2483 @ 40), (N/A, 20), (N/A)
	(5150 - 5250 @ 100), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
	(5250 - 5350 @ 100), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
	(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
	(5725 - 5730 @ 5), (N/A, 13), (0 ms), DFS
	(5725 - 5730 @ 5), (N/A, 13), (0 ms), NO-OUTDOOR, DFS
	(5725 - 5850 @ 80), (N/A, 13), (N/A), NO-OUTDOOR
	(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
	(57000 - 66000 @ 2160), (N/A, 40), (N/A)

phy#2
country GB: 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 - 5730 @ 160), (N/A, 26), (0 ms), DFS
	(5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
	(5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
	(57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#1
country GB: 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 - 5730 @ 160), (N/A, 26), (0 ms), DFS
	(5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
	(5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
	(57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0
country GB: 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 - 5730 @ 160), (N/A, 26), (0 ms), DFS
	(5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
	(5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
	(57000 - 71000 @ 2160), (N/A, 40), (N/A)

Although I’m not sure about the global setting

mainufer · August 31, 2026, 10:07am

@will Is there a way for Flint 4, to change the country code to Panama to increase the WiFi output?
This was possible with the MT6000 alias Flint 2.

Void · August 31, 2026, 10:38am

Hi
AI said something a bit different:

uci set wireless.MT7990_1_1.rd_region='CE'
uci set wireless.MT7990_1_2.rd_region='CE'
uci set wireless.MT7990_1_3.rd_region='CE'

uci set wireless.MT7990_1_1.country='GB'
uci set wireless.MT7990_1_2.country='GB'
uci set wireless.MT7990_1_3.country='GB'

uci commit wireless
wifi reload

Yes, you should change rd_region to CE when setting the country code to the UK (GB).

On OpenWrt devices using MediaTek proprietary drivers (such as the MT7990 driver), the ISO country code and the driver-level regulatory parameters work together:

rd_region (Radar Detection Region): Controls DFS (Dynamic Frequency Selection) radar signatures and compliance algorithms. Leaving this set to FCC causes the driver to use US radar detection patterns instead of the ETSI/CE rules required in the UK and Europe.

region / aregion (Channel Maps): Dictates allowable channel ranges (e.g., enabling channels 12 and 13 on 2.4 GHz and applying ETSI 5 GHz / 6 GHz channel masks).

Driver Enum Values: MediaTek drivers hardcode radar pattern algorithms into four primary categories: CE (ETSI/Europe), FCC (North America), MKK (Japan), and NCC (Taiwan). There is no separate GB code for rd_region.

Regulatory Compliance: The UK spectrum regulator (Ofcom) mandates ETSI standards (specifically EN 301 893 for 5 GHz DFS radar signatures and EN 303 687 for 6 GHz). In MediaTek driver firmware, all ETSI radar pattern detection is compiled under the CE flag.

Separation of Duties:

country='GB' sets UK-specific maximum transmit power (EIRP in dBm) and legal channel sub-band allocations.

rd_region='CE' tells the chip's physical layer (PHY) which radar pulse patterns to listen for when operating on DFS channels (52–64, 100–144).

Setting rd_region='CE' alongside country='GB' is 100% the correct combination for the UK.

Pro4TLZZ · August 31, 2026, 11:51am

Interesting

root@GL-BE14000:~# iw reg get
global
country 98: DFS-ETSI
        (2400 - 2483 @ 40), (N/A, 20), (N/A)
        (5150 - 5250 @ 100), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
        (5250 - 5350 @ 100), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
        (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
        (5725 - 5730 @ 5), (N/A, 13), (0 ms), DFS
        (5725 - 5730 @ 5), (N/A, 13), (0 ms), NO-OUTDOOR, DFS
        (5725 - 5850 @ 80), (N/A, 13), (N/A), NO-OUTDOOR
        (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
        (57000 - 66000 @ 2160), (N/A, 40), (N/A)

phy#2
country GB: 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 - 5730 @ 160), (N/A, 26), (0 ms), DFS
        (5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
        (5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
        (57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#1
country GB: 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 - 5730 @ 160), (N/A, 26), (0 ms), DFS
        (5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
        (5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
        (57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0
country GB: 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 - 5730 @ 160), (N/A, 26), (0 ms), DFS
        (5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
        (5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
        (57000 - 71000 @ 2160), (N/A, 40), (N/A)

root@GL-BE14000:~#

charles2 · September 2, 2026, 4:15am

Hi,

Thank you for sharing your testing and feedback.

The related country/region options in LuCI are still being adapted and improved, so it will take some more time to complete.
Regarding the Region setting, it is not related to Wi-Fi transmit power and has little practical impact. The available values are CE , FCC , and JAP , and you may select the corresponding region as needed.

Thank you for your understanding and patience.