Old news? - ASUS GT-AX11000, no 160 Mhz bandwidth option on 5G-2

[KLFDRO]

This topic has been bandied about for years, but I have been recently chasing my tail with it. I have found many descriptions of suggested rituals, but no definitive or consistent resolution.
None of the 4 varieties of "reset" options have worked. (2 via buttons, 2 via web GUI)
And here's my additional twist - I have 3 GT-AX11000 devices which share:
(1) the same HW version,
(2) same location of manufacture
(3) the same firmware, and
(4) the same settings file.

Of the 3 devices, only 1 is missing the 160Mhz bandwidth option on the 5G-2 band. That would seem to effectively eliminate any resolution by changing the firmware or some available system setting.
Perhaps not a huge issue in the overall scheme of things, but is the one device destined to forever live without the 160Mhz/5G-2option?

 

[ColinTaylor]

Perhaps not a huge issue in the overall scheme of things, but is the one device destined to forever live without the 160Mhz/5G-2option?

Probably. SSH into each router and compare their territory codes.

nvram get territory_code

 

[Tech9]

They are only 2x available 160MHz wide channels on 5GHz band, Ch.50 (36-64) and Ch.114 (100-128). Depending on how ASUS split the band and the available channels in the region you may or may not have available 160MHz on 5GHz-2 radio. There is Ch.163 (149-177) available only in the US and no client device supports it, can be used between two identical routers for wireless backhaul. Perhaps one of the routers has different region code.

 

[KLFDRO]

Probably. SSH into each router and compare their territory codes.

nvram get territory_code

It appears we have a winner. Territory codes are US/01, US/01 and . . . . . CA/01 for the rogue device.
I can see that, in theory, I could change that with an SSH "nvram set" command (and I am in the US).
Does that theory play out in reality?
Or will I just be trading my tail chasing for a wild goose chase?

With some trial and error on one of the US/01 code devices I was also able to retrieve the following nvram parameters:
wl0_country_code=US
wl0_country_rev=821
wl1_country_code=US
wl1_country_rev=821
wl2_country_code=US
wl2_country_rev=821
1:ccode= US
2:ccode= US
3:ccode= US

 

[ColinTaylor]

I can see that, in theory, I could change that with an SSH "nvram set" command (and I am in the US).
Does that theory play out in reality?

No that won't work.

Or will I just be trading my tail chasing for a wild goose chase?

Indeed.

And in case you're wondering, discussions about circumventing a router's regional restrictions are against these forums rules. Any such discussions will be deleted.