Builder71
Very Senior Member
...
Which one is correct ...
Always do a "nvram get" first.
This way you can go back without a restore to factory default.
e.g. "nvram get 0:ccode" doesn't give me an answer.
So I would say don't use these set commands.
...
Which one is correct ...
I noticed a small typo in the instructions here:
nvram ser regulation_domain=#a
should be:
nvram set regulation_domain=#a
I also found similar instructions elsewhere in the forum which are:
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
Which one is correct and I am assuming that this will allow maximum transmission that the hardware is capable of. Does that mean that using these settings could increase transmission power levels above what is allowed in the US? Only asking because I live in a remote area.
Thank you very much for the enormous amount of value you are producing by giving us your Merlin-releases.
I am using a sixxs.net IPv6 tunnel on my AC66U rather than native IPv6.
I start IPv6 with "/opt/sbin/aiccu start /opt/etc/aiccu.conf" from /jffs/scripts/wan-start.
Since this release radvd no longer gets configured and started automatically.
/etc/radvd.conf is no longer created and even if I put a radvd.conf into /jffs/configs it is not copied to /etc automatically and radvd is not started.
I had to create my own startup script that copies radvd.conf into /etc and starts radvd -u admin. The radvd.conf I use is the one I saved from the last release.
Is this behavior on purpose?
I wouldn't use these commands, they look messed up. If you go back and find the original post by XVortex you will see that they are for a Linksys EA6900.Which one is correct and I am assuming that this will allow maximum transmission that the hardware is capable of.
Sorry for the typo. give you the opportunity to behave like a responsible citizen. You could indeed increase the 5 GHz power level above the Us allowed 100mw. But it would not bring you much. Twice the power is just a minor step in dbm.
From the latest info that I have, the USA allows more than 100mW on the 5GHz band. Please see attachment.Sorry for the typo. It gives you the opportunity to behave like a responsible citizen. You could indeed increase the 5 GHz power level above the Us allowed 100mw. But it would not bring you much. Twice the power is just a minor step in dbm.
Thank you for this. I just ran these commands on one of my ac68u's and did in fact gain a little range in both 2.4 an 5 GHz channels, verified by inssider.
From the latest info that I have, the USA allows more than 100mW on the 5GHz band. Please see attachment.
I have run the commands you supplied and it looks as if power may still be limited. I do not wish to run higher than the 200mW allowed in my area, just saying.
Can't confirm that on RT-N66U, I'm using dnscrypt-proxy with .42.
Howdy,
374.42 feedback;
traffic manager, global and individual numbers are right on the money. working very good here.
client list, is working the fastest update and response time.
overall, I am really liking this build. I am not finding any issues here at this time.
Again, thank you very much for your passion and this hobby. Job well done.
Rmerlin, as a Mac user I can confirm that the spurious error messages in the log related to PCP are gone in 42. PCP is otherwise working fine. I assume this is what you mentioned in the release notes about fixes to PCP in this build.
need factory reset for .5517 ---->.42?
No, rc-code is preparing dnsmasq config (including hosts.add and dnsmasq.conf.add) and only then restarting dnsmasq daemon.Interesting. I had to add a "service restart_dnsmasq" to my wan-start script after putting the NTP addresses into hosts.add and that fixed things. Maybe a race condition with appending to hosts.add and dnsmasq reading it?
Howdy,
374.42 feedback;
traffic manager, global and individual numbers are right on the money. working very good here.
client list, is working the fastest update and response time.
overall, I am really liking this build. I am not finding any issues here at this time.
Again, thank you very much for your passion and this hobby. Job well done.

Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!