I thought Merlin had stopped using the EM driver quite a few versions ago after some confusion over it.All forks uses the same em driver, and should be all equal when it comes to the signal strengths. The only con with the forks, in my experience, it drains my iPhone's battery quicker than the latest SDK6.
I thought Merlin had stopped using the EM driver quite a few versions ago after some confusion over it.
Please help me with http://forums.smallnetbuilder.com/showpost.php?p=147373&postcount=537 this.
At least in the driver used in this fork, there is a compile option in target.mak to enable Engineering Mode. I tracked it down, and what this does is alter the country and regulation domain codes from what is contained in the CFE to some other values during the wireless initialization. So it's entirely possible that this was added without changing the wireless driver version.
Right now, I haven't done anything to change the defaults from what was set in the base Merlin code....EM is set for the N66 and disabled for all other routers.
I thought Merlin had stopped using the EM driver quite a few versions ago after some confusion over it.
nvram set pci/1/1/ccode
nvram set pci/2/1/ccode
nvram set wl0_country_code
nvram set wl1_country_code
nvram set regulation_domain
nvram set regulation_domain_5G
Today I played (again) a bit with regional stuff.
Code:nvram set pci/1/1/ccode nvram set pci/2/1/ccode nvram set wl0_country_code nvram set wl1_country_code nvram set regulation_domain nvram set regulation_domain_5G
If I change from EU to NL, I see a serious drop in RF signal on both bands.
Playing with nvram commands to set higher RF output, doesn't do anything.
Unfortunately the "nvram set wl0_chlist" and "nvram set wl1_chlist" commands don't stick if the country code is EU.
Best setting for me would be using "EU" setting with all possible channels.
All this #a stuff doesn't give the same RF level compared to "EU" setting.
Am I the only one seeing this?
At least in the driver used in this fork, there is a compile option in target.mak to enable Engineering Mode. I tracked it down, and what this does is alter the country and regulation domain codes from what is contained in the CFE to some other values during the wireless initialization. So it's entirely possible that this was added without changing the wireless driver version.
Right now, I haven't done anything to change the defaults from what was set in the base Merlin code....EM is set for the N66 and disabled for all other routers.
No, the latest official firmware is dated/built in June.So basically this is the same wireless driver as the official sdk6 Asus implements in their official firmware builds?
wl0: Jun 16 2014 19:31:20 version 6.30.163.2002 (r382208)
Today I played (again) a bit with regional stuff.
Code:nvram set pci/1/1/ccode nvram set pci/2/1/ccode nvram set wl0_country_code nvram set wl1_country_code nvram set regulation_domain nvram set regulation_domain_5G
If I change from EU to NL, I see a serious drop in RF signal on both bands.
Playing with nvram commands to set higher RF output, doesn't do anything.
Unfortunately the "nvram set wl0_chlist" and "nvram set wl1_chlist" commands don't stick if the country code is EU.
Best setting for me would be using "EU" setting with all possible channels.
All this #a stuff doesn't give the same RF level compared to "EU" setting.
Am I the only one seeing this?
No, the latest official firmware is dated/built in June.
Code:wl0: Jun 16 2014 19:31:20 version 6.30.163.2002 (r382208)
Maybe bad wording on my part.....the driver itself is still closed source (always has been). Inside the closed source driver are the country and regulation mode definitions, so can't change what those do as well.
Engineering mode did a tweak to the country/reg parameters passed to the closed source driver thru an nvram variable. This is also why the '#a' nvram commands worked.
Then in 376 code they closed that door somehow such that the nvram variables no longer have an effect and you have to modify the CFE/bootloader to make any changes. I haven't tried to figure out what they did (am going to follow Merlin's position here about not trying to circumvent it).
Yes, it's the same version number but different build date. Asus does this whenever they change something in the drivers codes. Probably, Merlin can explain better when he comes around.That probably just means the last time they edited the code. Isn't that the same version number that is on all of Asus's firmware builds with the sdk6 driver? Asus did not mention a wireless driver change with the RT-N66U in their changelog with the most recent 376 firmware builds. They probably never list every exact little change though, like maybe say an edit of a coding that is not a fix for a bug.
Yes, it's the same version number but different build date. Asus does this whenever they change something in the drivers codes. Probably, Merlin can explain better when he comes around.
To be honest, I'm not sure I follow what you are asking. The #a mod in and of itself does not alter the throughput capabilities of the router....it gives you more channels and maybe some additional range towards the capability of the router. The two screenshots you show (both are the same) show that it supporting the highest possible N attachment of N450 per client.
Load balancing doesn't work that way, summing up the speeds for a single data connection (hence the name balancing, not bonding). The balancing is done for separate data connections. If you had two single-threaded downloads for example, one will be routed through one connection, and the second one through the other.But with a loadbalance of 3:1 i still only get a max of 152mb when i set it to 1:1 i get 50mb. Which ratio do i need to have if i want to combine my 152mb connection with my 50mb for a speed of around 200mb?
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!