What's new

"wl" command doesn't work: FW 380.59 for AC88U

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

gdillainepub

New Around Here
hi guys,

I'm not sure if this has already been reported, but I couldn't find any mentioning of this.

I've just upgraded my RT-AC88U to firmware 380.90 and found the "wl" command no longer works. (It was ok with 380.57).

Now if I ssh into the router and run the command with arguments that it should be able to work with, it won't give any output; but if i give it an incorrect argument, like "xyz", it's still able to return a line:

Code:
wl: Unsupported

Now this is how the "wl" command behaves on AC88U w/ 380.59:

Code:
DHY@Router:/#
DHY@Router:/#
DHY@Router:/# wl txpwr_target_max
DHY@Router:/#
DHY@Router:/# wl txpwr1
DHY@Router:/#
DHY@Router:/# wl txpwr
DHY@Router:/#
DHY@Router:/# wl xyz
wl: Unsupported
DHY@Router:/#
DHY@Router:/#

If've tried everything including the 30-30-30 and re-flash the firmware but the same. And I also tried reverting the firmware back to 380.57, the "wl" functions normally again!

Any advice, guys?
 
wl txpwr_target_max

worked fine for me on my ac68, have to wait for someone with your router to confirm if it is just you or a new bug.
 
There's a chance this no longer works on power-related functions due to regulatory requirements. wl still works if you use other functions such as querying the list of associated clients.
 
There's a chance this no longer works on power-related functions due to regulatory requirements. wl still works if you use other functions such as querying the list of associated clients.

Thanks RMerlin.

Were you implying that during the development of 380.59, those power-related functions from the original wl command were deliberately removed?

Oh if thats the case I beg to differ:

1. Even the original "wl" command was only able to READ those power-related parameters, and display their values. But the command (wl) was not capable of making any changes to those values. right?

2. If the "wl" command is not capable of overriding the router's factory power presets, there is no need to *ban* those functions just because they can show you how much transmit power your router has got?

3. Even regulatory concerns have to be taken into consideration, the Asuswrt-Merlin firmware is used worldwide -- they don't have to follow FCC in Europe (actually i read somewhere saying in Germany they allow 500mW for home router).


But anyway, whether or not the user is trying to tamper with the router's radio power -- "wl" is not the way it can be done, right?


so.. i wish to ask @RMerlin and the Asuswrt-Merlin developing team to reconsider if its possible to restore the original "wl".

thanks guys great work!
 
The wl tool is closed source, so I have no control over it, nor can I tell what changes between each new versions.
 
The wl tool is closed source, so I have no control over it, nor can I tell what changes between each new versions.

The hybrid code itself isn't very helpful if examining... even the FOSS code isn't very "friendly" down that path.

Wouldn't matter much anyways - from the release notes on the OEM SDK.. but mine is pretty old...

https://www.broadcom.com/docs/linux_sta/README.txt

TX POWER EXPLAINED
------------------
'iwconfig eth1 txpower' & 'iwlist eth1 txpower' set and get the drivers
user-requested transmit power level. This can go up to 32 dbm and allows
the user to lower the tx power to levels below the regulatory limit.
Internally, the actual tx power is always kept within regulatory limits
no matter what the user request is set to.
 
The wl tool is closed source, so I have no control over it, nor can I tell what changes between each new versions.


Oh I see, thanks. But i'm think will that be possible to extract the "wl" file from 380.57 to replace the newer versions of "wl" in future builds?
 
Oh I see, thanks. But i'm think will that be possible to extract the "wl" file from 380.57 to replace the newer versions of "wl" in future builds?

You could give it a try, but personally I have no intention of downgrading it, as it could break other things in the firmware which relies on it.
 
Doesn't work on my N66U.

But it does return something:-

Code:
ASUSWRT-Merlin RT-N66U 380.59-0 Tue May 10 15:44:44 UTC 2016
admin@RT-N66U:/tmp/home/root# wl ver
6.30 RC163.2002
wl0: Mar  2 2016 09:47:22 version 6.30.163.2002 (r382208)

admin@RT-N66U:/tmp/home/root# wl txpwr_target_max
wl: Unsupported

There are other functions I see, but haven't tried using

Code:
admin@RT-N66U:/tmp/home/root# wl maxpower
wl_phy_maxpower: fail to get maxpower
maxp2ga0=6d
maxp2ga1=61
maxp5ga0=78
maxp5ga1=70
maxp5gla0=6f
maxp5gla1=77
maxp5gha0=65
maxp5gha1=72
maxpower
        Set temp maxp2g(5g)a0(a1) value
usage: wl maxpower maxp2ga0=0x1 maxp2ga1=0x2 maxp5ga0=0xff maxp5ga1=0xff
       maxp5gla0=0x3 maxp5gla1=0x4 maxp5gha0=0x5 maxp5gha1=0x6
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top