Following instructions are provided without any warranty, and may even get you in trouble legally. The instructions are provided for testing, learning, preventing e-waste, and should be use with care. We (including contributers + commentators) are not responsible for any damage to your device(s) or any legal issues.
Instructions have been moved to https://github.com/francoism90/asus-router. :)
@Euri007 You don't have to flash back to stock, just stay on the fork if you want to test channels and such.
Ok perfect. I'll try
@RE3CON I have an AX86S, but I cannot raise tx power. I've tried all possible commands and also cross-tried all commands. On my "old" AC86U, I could raise tx power with an "init-start" script in jffs, but this does not work anymore with the AX86S. Any idea how I can raise tx power? It's an EU-model.
Edit: I got it working now! I think, I made some mistakes earlier, like not making the init-start script executable. Here is my init-start:
#!/bin/sh nvram set asuscfe0:ccode=#a nvram set asuscfe1:ccode=#a nvram set asuscfe0:regrev=0 nvram set asuscfe1:regrev=0 nvram set asuscfecommit=1 nvram set 0:regrev=0 nvram set 1:regrev=0 nvram set 0:ccode=#a nvram set 1:ccode=#a nvram set pci/1/1/ccode=#a nvram set pci/1/1/regrev=0 nvram set pci/2/1/ccode=#a nvram set pci/2/1/regrev=0 nvram set regulation_domain=#a nvram set regulation_domain_5G=#a nvram set wl_country_code=#a nvram set wl_country_rev=0 nvram set wl0_country=#a nvram set wl0_country_code=#a nvram set wl0_country_rev=0 nvram set wl0_reg_mode=off nvram set wl1_country=#a nvram set wl1_country_code=#a nvram set wl1_country_rev=0 nvram set wl1_reg_mode=off nvram set 0:maxp2ga0=120 nvram set 0:maxp2ga1=120 nvram set 0:maxp2ga2=120 nvram set 1:maxp5ga0=120,120,120,120 nvram set 1:maxp5ga1=120,120,120,120 nvram set 1:maxp5ga2=120,120,120,120 nvram set wl_txpower=708 nvram set wl0_txpower=708 nvram set wl1_txpower=708 nvram commit
wl txpwr_target_max is now showing 26.00 All connected clients also show much better connection now! Any suggestions to these settings above?
Edit2: Only one problem left: My AC86U-AI-mesh node won't transmit with maximum tx anymore. I also use an executable init-start script on the mesh node with jffs scrips enabled:
nvram set jffs2_exec=/jffs/scripts/init-start nvram set jffs2_scripts=1 nvram commit reboot
The mesh-node starts with wl txpwr_target_max showing 22.50 but after a few seconds it's going back down to 13,75. I think my AX86S is saying to the AC86U-AI-mesh node, to power down tx performance. How can I solve this?
Edit3: Also solved: I had to downgrade the fw of the AC86U to 386.5_2. Now it's transmitting with 22.50 again.
How to change in node with ssh? Whai ip can I use? And how to enable ssh in node?
solved
Hi,
I have ASUS 66U B1 , I am trying to follow this guide. I enabled ssh and logged in through putty, I did the dump and enable jfss. But can understand the next steps, can some oone guide what I need to run or using putty? Thanks
@Limpi1978 Download this modified init-start script: https://mega.nz/file/is4FSDgD#9m4A7N-r6BomeU1n7SfrF9ZE9_036454nwAjmzA9_nM Copy this init-start script to your router into the folder jffs/scripts. (I use WinSCP to copy files onto my router) Make the init-start script executable (x in file properties). Make sure you "Enable JFFS custom scripts and configs" in System settings on your router. You don't need to format JFFS. SSH into your router and enter these commands:
nvram set jffs2_exec=/jffs/scripts/init-start nvram set jffs2_scripts=1 nvram commit reboot
You can modify the init-start script to your likings. See if it works.
Btw. I use channel 48 for 5GHz after extensive testing. With 48, I get the best results in range and speed. (80MHz channel bandwidth)
You seem very knowledgeable on this. Can you please explain how I can enable all the channels on it? Mine has many locked out.
Hi all, I think my question is off topic, but does anyone know which variable in nvram to enable 4x4 (4T4R) streams on the 5ghz band? Or maybe use the wl command?
I have an asus tuf-ax3000 (v1), the 5ghz chipset is capable of 4x4 streams, but it is locked to 2x2 by asus.
@alfky12 Interesting! :)
You could run nvram dump, and check if it's being exposed.
@alfky12 Interesting! :)
You could run
nvram dump, and check if it's being exposed.
Thanks for responding. What does "check if it's being exposed" mean? I've dumped it and it's not encrypted.
is there a nvram show / get / set guide for Mediatech based TUF-AX6000?
Hi all. Firstly, many thanks for doing this. It is greatly appreciated! Managed to get this going on an ASUS RC-AX58U V2 running a Merlin fork: RT-AX58U_V2_3004_388.8_2 and an ASUS RC-AX88U running Merlin firmware RT-AX88U_3004_388.8_2.
Downloaded the:
init-start
File available at:
https://mega.nz/file/is4FSDgD#9m4A7N-r6BomeU1n7SfrF9ZE9_036454nwAjmzA9_nM
Copied the file into my:
jffs/scripts
Folder using WinSCP. One thing not mentioned regarding this is that when setting up WinSCP, you need to choose the session file protocol:
SCP
I didn’t know that although do now and as these routers are Linux based, this will also work when accessing a Raspberry Pi.
Other things worth mentioning. Although I got this working, I can’t select any Wireless channels above 140 on 5G on my RC-AX88U. No idea why and the only way that I can select above channels 128 is to set this to 20/40/80 MHz Not running 160Mhz on WIFI6 as 80MHz is fast enough. Wonder if anyone can access channels above 140 on an RT-AX-88U? BTW, can access all 5G channels including 149 on my RC-AX58U V2 with this script running.
Hi all.
Thank you for all informations you posted here.
These are my settings for my router RT-AX5400, firmware 3004.388.8_2-gnuton1.
#!/bin/sh
nvram set 0:ccode=#a
nvram set 0:regrev=0
nvram set 1:ccode=#a
nvram set 1:regrev=0
nvram set location_code=#a
nvram set territory_code=US/02
nvram set wl_country_code=#a
nvram set wl_country_rev=0
nvram set wl0_country_code=#a
nvram set wl0_country_rev=0
nvram set wl1_country_code=#a
nvram set wl1_country_rev=0
nvram set 0:maxp2ga0=120
nvram set 0:maxp2ga1=120
nvram set 1:maxp5gb0a0=120
nvram set 1:maxp5gb0a1=120
nvram set 1:maxp5gb0a2=120
nvram set 1:maxp5gb0a3=120
nvram set 1:maxp5gb1a0=120
nvram set 1:maxp5gb1a1=120
nvram set 1:maxp5gb1a2=120
nvram set 1:maxp5gb1a3=120
nvram set 1:maxp5gb2a0=120
nvram set 1:maxp5gb2a1=120
nvram set 1:maxp5gb2a2=120
nvram set 1:maxp5gb2a3=120
nvram set 1:maxp5gb3a0=120
nvram set 1:maxp5gb3a1=120
nvram set 1:maxp5gb3a2=120
nvram set 1:maxp5gb3a3=120
nvram set 1:maxp5gb4a0=120
nvram set 1:maxp5gb4a1=120
nvram set 1:maxp5gb4a2=120
nvram set 1:maxp5gb4a3=120
nvram set 1:maxp5gb5a0=120
nvram set 1:maxp5gb5a1=120
nvram set 1:maxp5gb5a2=120
nvram set 1:maxp5gb5a3=120
nvram set 1:maxp5gb6a0=120
nvram set 1:maxp5gb6a1=120
nvram set 1:maxp5gb6a2=120
nvram set 1:maxp5gb6a3=120
nvram set wl_txpower=708
nvram set wl0_txpower=708
nvram set wl1_txpower=708
nvram commit
These are my results.
I hope it helps.
Trying to set 36/160 in my main ax86u permanently but no success. I use an AIMESH, whenever a device connects to my main ax86u router in 80mhz it drops the entire network to this bandwidth. If i only connect this device in the nodes this doesnt happen. Any clues how could I solve this matter? Using the latest asus fw, also tried Merlin latest.
PS: If I use an old FW *46061 this never happens and also I can view all the cannels in GUI for 160mhz.
following is my log
country=US
fb_country=US
modem_country=US
size: 91808 bytes (39264 left)
wl0_country=#a
wl0_country_code=ALL
wl0_country_rev=0
wl1_country=#a
wl1_country_code=ALL
wl1_country_rev=0
wl2_country_code=#a
wl2_country_rev=0
wl_country=US
wl_country_code=#a
wl_country_rev=0
wl1_chansps=36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165 169 173 177 36l 40u 44l 48u 52l 56u 60l 64u 100l 104u 108l 112u 116l 120u 124l 128u 132l 136u 140l 144u 149l 153u 157l 161u 165l 169u 173l 177u 36/80 40/80 44/80 48/80 52/80 56/80 60/80 64/80 100/80 104/80 108/80 112/80 116/80 120/80 124/80 128/80 132/80 136/80 140/80 144/80 149/80 153/80 157/80 161/80 165/80 169/80 173/80 177/80 36/160 40/160 44/160 48/160 52/160 56/160 60/160 64/160 100/160 104/160 108/160 112/160 116/160 120/160 124/160 128/160 149/160 153/160 157/160 161/160 165/160 169/160 173/160 177/160
wl2_chansps=36 40 44 48 52 56 60 64 36l 40u 44l 48u 52l 56u 60l 64u 36/80 40/80 44/80 48/80 52/80 56/80 60/80 64/80 36/160 40/160 44/160 48/160 52/160 56/160 60/160 64/160 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165 169 173 177 100l 104u 108l 112u 116l 120u 124l 128u 132l 136u 140l 144u 149l 153u 157l 161u 165l 169u 173l 177u 100/80 104/80 108/80 112/80 116/80 120/80 124/80 128/80 132/80 136/80 140/80 144/80 149/80 153/80 157/80 161/80 165/80 169/80 173/80 177/80 100/160 104/160 108/160 112/160 116/160 120/160 124/160 128/160 149/160 153/160 157/160 161/160 165/160 169/160 173/160 177/160
@pabrognara In the GitHub repo, I've added an example for AiMesh.
If you want to force a channel, you have to adjust the main, Ai-node and global value. I also do this on my AiMesh node.
@francoism90 already used these commands to try to force main:
Pedro@RT-AC68U-C6D0:/tmp/home/root# nvram set wl1_chanspec=36/160
Pedro@RT-AC68U-C6D0:/tmp/home/root# nvram set wl1_channel=36
Pedro@RT-AC68U-C6D0:/tmp/home/root# nvram commit
The main still not showing channels only auto. It starts wih 36/160 but once some device connect to it at 80mhz it drops the entire wireless network to this BW.
The nodes ever since are ok.
Is there any else command I should try to force the main?
Curiously as I said using firmware 46061 it works perfectly but really cant use the lastest firmwares to keep 160mhz in the main ax86u router. I also tried to reset without Ai mesh and didnt work. Once a 80mhz device connect to it, it downgrades to this bandwidth.
Interesting on my GT-AC2900 160mhz becomes unavailable if these entries are set to anything but undefined (default setting):
nvram set location_code=
nvram set wl_country_code=
nvram set wl_country_rev=
I have to clear nvram to enable 160mhz again, nvram unset doesn't work. Not sure if all three entries cause it to break or just one of them.
@pabrognara You could test the latest changes I've pushed. It basically removes the cap limit, but I'm still finding out how it actually works. So I don't recommend actually doing nvran commit after (unless you don't mind a hard reset on connection issues).
For me after those changes, I finally have 160mhz working. Strangely enough it's only working for radio-1 on my AiMesh node. I think it's because they want you to use radio-2 for AiMesh to work when using it as a wireless node, and they don't allow to have multiple 160mhz bands. Hopefully I can get both working, radio-2 is stuck at 20mhz/149.
@Sildurs-shaders Are you testing on multiple devices? Some may decline upper channels or use LAR (see README), meaning you may have to force a channel.
You could test my latest commit (uncomment those lines), which basically removes the cap limit as well. But I still don't fully understand how they work. So use it at your own risk.
I've also added tools/reset.txt. I use ACS again, which may work getting them connected again.
Did a lot of rebooting and nvram clearing to figure out which entries broke it and tested it by going in media bridge mode and connecting it to my main router. It forces my main router in to 80mhz mode if those entries are changed and if I check the GT-AC2900 in router mode the tick box / selection for 160mhz is also gone. Nvram clear and changing everything but those three entries restores 160mhz functionality. (or one of them, haven't tried them one by one because it's pain in the ass to wipe nvram all the time)
@Sildurs-shaders Is this an AiMesh node? If so, is it wired backhaul or wireless?
You don't need to do nvram commit. You can test/set the nvram setting, and restart the wireless of your router. This is actually the recommended approach. I'll try to add the restart command later. It's something like service restart wireless, but cannot test right now.
If you don't have any cable/ethernet, you could also use the 2.4GHz channels as a backup.
@francoism90 > @pabrognara You could test the latest changes I've pushed. It basically removes the cap limit, but I'm still finding out how it actually works. So I don't recommend actually doing nvran commit after (unless you don't mind a hard reset on connection issues).
Would u pls copy those lines here? So I can try nvram and commiting without creating a script
BTW I am testing an ax88upro and last FW with my settings backup and it is working flawlessly without "dropping" to 80mhz when a non 160mhz device is connected to it.
@pabrognara Please see repo in first post.
@Euri007 You don't have to flash back to stock, just stay on the fork if you want to test channels and such.