RussellInCincinnati
Senior Member
With RMerlin's observations in mind, that fiddling with transmit power is not likely to do anything great...and having no intention to boost routers above FCC regulatory limits of 36dBm EIRP in my US region (see parts of this thread below)...from the initial guidance of "Engineer", have further followed "Vaesel" suggestions for editing a 1.0.2.0 (US) boot loader CFE for AC68U routers (you only need to look at the notes after the heading "Edit CFE" in his post):
http://forums.smallnetbuilder.com/showthread.php?t=19262
), for maxing transmitted WiFi signal milliwatts from 100 to 780.
By the way Vaesel describes steps of changing firmware post-CFE change, that are at least not essential in the case of router already running Merlin ...49. That is to say, after you install the new CFE and issue a "reboot" command, your Merlin ...49 firmware is still good. All you have to do with the Merlin menus is go in and do a "restore factory default" action. And you're back in ...49 with a new potential for higher transmit power, that you will soon finalize with some nvram set commands later.
A compliment to that post describing a specific CFE (bootloader) mod, is this "hggomes" post suggested by "Engineer" on the general procedure for burning CFE 1.0.2.0 US (or any other CFE) into RT-AC68U or TMobile TMAC1900 routers, using the "mtd-write v2" Linux utility:
http://slickdeals.net/forums/showpost.php?p=70991738&postcount=2576
After copying out, editing and burning the changed CFE back into a router that was already running the latest Dec 2014 ...49 firmware, had to reset the thing back to factory defaults through the Merlin menus. Then you must reconfigure all your custom settings, but particularly finish up re-establishing any wireless settings.
Now there are a few Xshell4/SSH or telnet login and then "nvram set" commands AFTER using the Merlin menus...to finish setting up the higher-powered wireless connections. That is to say the several nvram set commands you need to do to polish off this power boost, apparently get overwritten, each time you change wireless settings through the Merlin menus. So you do the "nvram set" commands last.
Not forgetting that you have to enable SSH or telnet to be able to reach the Linux prompt in the router, to do the nvram set commands or indeed any CFE retrieval or reflashing.
Am reporting that the increase in range and link stability, and reduction in ping times, to distant iPad, tiny USB WiFi adapters and cheap Alcatel smart phones is immediately and pleasantly noticeable. And works great with Merlin ...49 firmware.
In my busy areas have confined 2.4ghz router settings to 20mhz bandwidth only, so the speeds are not mind-blowing. But being able to walk out of my large brick building where the router is several walls away from the outdoors, and go out to a parked car on the street and still have a 2.4ghz connection, is a little bit of an eye-opener.
Am also surprised because am sure RMerlin knows what he is talking about, and he has lucidly described the probable uselessness of increasing the transmit power of just one side of a WiFi "conversation". After all every WiFi transaction involves both a transmit AND a receive.
Considering also that you may be hurting something by sending more power through tiny bits, am offering this non-statistically-significant experimental result more as a fun topic for weekend fiddling. Rather than a broad recommendation that we can all get closer to Heaven this way. Especially since it is real easy to destroy a router by loading it up with a bootloader you have edited by hand, that has a single wrong character anywhere in the Ethernet MAC addresses you copy into your new CFE.
Anyway thanks much, RMerlin, Engineer, hggomes and Vaesel.
Not sure exactly what nvram show output to look for, to verify that the transmit power is higher. But testing certainly shows the difference anyway.
http://forums.smallnetbuilder.com/showthread.php?t=19262
), for maxing transmitted WiFi signal milliwatts from 100 to 780.
By the way Vaesel describes steps of changing firmware post-CFE change, that are at least not essential in the case of router already running Merlin ...49. That is to say, after you install the new CFE and issue a "reboot" command, your Merlin ...49 firmware is still good. All you have to do with the Merlin menus is go in and do a "restore factory default" action. And you're back in ...49 with a new potential for higher transmit power, that you will soon finalize with some nvram set commands later.
A compliment to that post describing a specific CFE (bootloader) mod, is this "hggomes" post suggested by "Engineer" on the general procedure for burning CFE 1.0.2.0 US (or any other CFE) into RT-AC68U or TMobile TMAC1900 routers, using the "mtd-write v2" Linux utility:
http://slickdeals.net/forums/showpost.php?p=70991738&postcount=2576
After copying out, editing and burning the changed CFE back into a router that was already running the latest Dec 2014 ...49 firmware, had to reset the thing back to factory defaults through the Merlin menus. Then you must reconfigure all your custom settings, but particularly finish up re-establishing any wireless settings.
Now there are a few Xshell4/SSH or telnet login and then "nvram set" commands AFTER using the Merlin menus...to finish setting up the higher-powered wireless connections. That is to say the several nvram set commands you need to do to polish off this power boost, apparently get overwritten, each time you change wireless settings through the Merlin menus. So you do the "nvram set" commands last.
Not forgetting that you have to enable SSH or telnet to be able to reach the Linux prompt in the router, to do the nvram set commands or indeed any CFE retrieval or reflashing.
Am reporting that the increase in range and link stability, and reduction in ping times, to distant iPad, tiny USB WiFi adapters and cheap Alcatel smart phones is immediately and pleasantly noticeable. And works great with Merlin ...49 firmware.
In my busy areas have confined 2.4ghz router settings to 20mhz bandwidth only, so the speeds are not mind-blowing. But being able to walk out of my large brick building where the router is several walls away from the outdoors, and go out to a parked car on the street and still have a 2.4ghz connection, is a little bit of an eye-opener.
Am also surprised because am sure RMerlin knows what he is talking about, and he has lucidly described the probable uselessness of increasing the transmit power of just one side of a WiFi "conversation". After all every WiFi transaction involves both a transmit AND a receive.
Considering also that you may be hurting something by sending more power through tiny bits, am offering this non-statistically-significant experimental result more as a fun topic for weekend fiddling. Rather than a broad recommendation that we can all get closer to Heaven this way. Especially since it is real easy to destroy a router by loading it up with a bootloader you have edited by hand, that has a single wrong character anywhere in the Ethernet MAC addresses you copy into your new CFE.
Anyway thanks much, RMerlin, Engineer, hggomes and Vaesel.
Not sure exactly what nvram show output to look for, to verify that the transmit power is higher. But testing certainly shows the difference anyway.
Last edited: