nvram set and commit not holding

[rubyj]

I am running a few commands via ssh:

nvram set 0:ccode=#a
nvram set 1:ccode=#a
nvram set 0:regrev=0
nvram set 1:regrev=0
nvram set wl0_country_code=#a
nvram set wl0_country_rev=0
nvram set wl0_reg_mode=off
nvram set wl1_country_code=#a
nvram set wl1_country_rev=0
nvram set wl1_reg_mode=off
nvram commit
reboot

However when I reboot none of these settings hold. They seems to constantly go back to their original values. I am on a ac-rt68W. Any ideas?

 

[RMerlin]

You cannot change region-related parameters, they are hardcoded by the firmware for legal reasons.

 

[rubyj]

I see

 

[General5]

You cannot change region-related parameters, they are hardcoded by the firmware for legal reasons.

Could I update the sshd-port parameter to a new one by using `nvram set sshd-port=2222 && nvram commit`

 

[dukdukgoos]

Merlin, what country's law are you afraid of breaking here? If it's open source code used all over the world I'm not sure why we shouldn't be allowed to change it at our own risk. My situation is I moved from the USA to Japan and want to change the region info to reflect Japan's laws... it's actually more lawful to allow us to change it.

At minimum we should be able to change the region info based on your location via IP, or time zone...

 

[ColinTaylor]

Merlin, what country's law are you afraid of breaking here? If it's open source code used all over the world I'm not sure why we shouldn't be allowed to change it at our own risk. My situation is I moved from the USA to Japan and want to change the region info to reflect Japan's laws... it's actually more lawful to allow us to change it.

At minimum we should be able to change the region info based on your location via IP, or time zone...

There are already hundreds of posts discussing this elsewhere in these forums. The wireless code is not open source, it was moved to closed source by Asus/Broadcom as a regulatory requirement. Nothing to do with Merlin, it's entirely outside his control.

 

[joegreat]

At minimum we should be able to change the region info based on your location via IP, or time zone...

Nope, the FCC rules are forcing the vendors to lock down routers and you should only use them in the region for which they have build/sold for - otherwise you violate the FCC rules!

You can read many threads/posting in the forum about this and also on Google: WAY TO GO, FCC. NOW MANUFACTURERS ARE LOCKING DOWN ROUTERS

 

[dukdukgoos]

Yeah, but I don't care about the FCC, I'm in Japan!

US laws shouldn't dictate anything that people in the rest of the world do.

However, if I understand correctly you're saying that the code that controls this behavior is in a closed-source blob binary we can't change? It's not part of the code hosted on Github?

 

[joegreat]

However, if I understand correctly you're saying that the code that controls this behavior is in a closed-source blob binary we can't change? It's not part of the code hosted on Github?

Yep, it's in the CFE, closed source blobs and is respected in open source parts as well - so it's hard to overcome...

 

[ColinTaylor]

Yeah, but I don't care about the FCC, I'm in Japan!

US laws shouldn't dictate anything that people in the rest of the world do.

<sigh>You're about the thousandth person to say that. Take it up with the FCC, ARIB and ETSI (which includes Japan as an associate member).

However, if I understand correctly you're saying that the code that controls this behavior is in a closed-source blob binary we can't change? It's not part of the code hosted on Github?

Correct.

 

[dukdukgoos]

Okay, just wanted to make sure this wasn't a situation where the code *is* accessible to change in the OSS parts of the firmware but is being "respected" for some reason.

So I gather the only alternative is use the older LTS fork version that predates the move of the code to the binary blob? Or hack the binary blob with hex editor? Any other options I'm missing?

 

[Grisu]

thats a 2 years old thread, not relevant anymore!
read a bit more and you will find an easy way to make your changes durable in cfe as nvram will take them from cfe: https://www.snbforums.com/threads/rt-ac68u-change-region.14815/#post-178001
and on newer cfe you will need this too: https://www.snbforums.com/threads/rt-ac68u-change-region.14815/page-2#post-382218
works for RT-AC68U (and subtypes), not on others or dont know!