RT-AC68U - 3.0.0.4_378.50 Firmware - CFE modified

[ngerasimatos]

I installed RT-AC68U_3.0.0.4_378.50 this morning and wiped the NVRAM after. I then tried to apply the power settings but I don't think I am doing this correctly. I used the following to set the power:

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 commit

I then check the power output:

admin@RT-AC68U-3170:/# nvram show | grep -i maxp
size: 43309 bytes (22227 left)
1:maxp5ga0=120,120,120,120
1:maxp5ga1=120,120,120,120
1:maxp5ga2=120,120,120,120
0:maxp2ga0=120
0:maxp2ga1=120
0:maxp2ga2=120

After reboot and check the power output it shows the following:

admin@RT-AC68U-3170:/# nvram show | grep -i maxp
size: 43309 bytes (22227 left)
1:maxp5ga0=114,114,114,114
1:maxp5ga1=114,114,114,114
1:maxp5ga2=114,114,114,114
0:maxp2ga0=114
0:maxp2ga1=114
0:maxp2ga2=114

Any idea what I am doing wrong?

 

[Deleted member 22229]

The power settings with the newer firmwares can not be changed with out editing the boot loader now matter what cammands you run it will still default to a max of 80mw.

 

[ngerasimatos]

The power settings with the newer firmwares can not be changed with out editing the boot loader now matter what commands you run it will still default to a max of 80mw.

I modified the CFE before flashing. Is there something else that needed to be done?

 

[RMerlin]

378.50, just like Asus' 376_3626, upgrades the CFE on the RT-AC68U. Any previous change might have been overwritten by it.

 

[ngerasimatos]

378.50, just like Asus' 376_3626, upgrades the CFE on the RT-AC68U. Any previous change might have been overwritten by it.

Right, but after flashing 378.50 i then copy mtd0 to /tmp and then download it via SCP, then edit it in a hexeditor changing the values for the following:

"0:ccode" "1:ccode" change the values to "#a"
"0:maxp2ga0", "0:maxp2ga1", "0:maxp2ga2", "1:maxp5ga0", "1:maxp5ga1", "1:maxp5ga2" change all values to 120 from the default of 106.

I then save the updated cfe.bin upload it via SCP and then flash using mtd-write -i new_cfe.bin -d pmon and after doing so, reboot, and the international channels stay unlocked but the power options revert to the default settings.

What am I missing?

 

[RMerlin]

Right, but after flashing 378.50 i then copy mtd0 to /tmp and then download it via SCP, then edit it in a hexeditor changing the values for the following:

"0:ccode" "1:ccode" change the values to "#a"
"0:maxp2ga0", "0:maxp2ga1", "0:maxp2ga2", "1:maxp5ga0", "1:maxp5ga1", "1:maxp5ga2" change all values to 120 from the default of 106.

I then save the updated cfe.bin upload it via SCP and then flash using mtd-write -i new_cfe.bin -d pmon and after doing so, reboot, and the international channels stay unlocked but the power options revert to the default settings.

What am I missing?

No idea. Personally, I don't recommend (nor support) CFE-level modifications, as too many things can go wrong. Just setting the region code to #a for instance breaks things at the firmware level - DFS support specifically looks for the "EU" region, and won't work with #a.

 

[ngerasimatos]

No idea. Personally, I don't recommend (nor support) CFE-level modifications, as too many things can go wrong. Just setting the region code to #a for instance breaks things at the firmware level - DFS support specifically looks for the "EU" region, and won't work with #a.

I had no idea. The main reason why I wanted the newer firmware was to use features like adaptive QoS and such. DO you think I should rollback to an earlier firmware version which allows me to set these values in nvram?

 

[RMerlin]

I had no idea. The main reason why I wanted the newer firmware was to use features like adaptive QoS and such. DO you think I should rollback to an earlier firmware version which allows me to set these values in nvram?

Up to you. If you are willing to give up on the bug fixes and the new DPI engine as a trade-off, go for it.

 

[ngerasimatos]

Up to you. If you are willing to give up on the bug fixes and the new DPI engine as a trade-off, go for it.

Any performance loss/gain between the different versions?

 

[RMerlin]

Any performance loss/gain between the different versions?

As usual, I get some people telling me it's amazing, others telling me it's a disaster, and the rest reporting no difference.

So the answer is: no idea.

 

[ngerasimatos]

As usual, I get some people telling me it's amazing, others telling me it's a disaster, and the rest reporting no difference.

So the answer is: no idea.

I also heard the same mixed information. I guess I will leave it as is for now and will consider moving the router to a location that provides better coverage to the home.

 

[leszek]

Right, but after flashing 378.50 i then copy mtd0 to /tmp and then download it via SCP, then edit it in a hexeditor changing the values for the following:

"0:ccode" "1:ccode" change the values to "#a"
"0:maxp2ga0", "0:maxp2ga1", "0:maxp2ga2", "1:maxp5ga0", "1:maxp5ga1", "1:maxp5ga2" change all values to 120 from the default of 106.

I then save the updated cfe.bin upload it via SCP and then flash using mtd-write -i new_cfe.bin -d pmon and after doing so, reboot, and the international channels stay unlocked but the power options revert to the default settings.

What am I missing?

You flashed the cfe to the wrong device. pmon is only valid for mips (66u etc.) and not arm (68U etc.) Be thankful you didn't brick your router and in the future use boot for arm devices.