Use wl commands?

[francoism90]

See instructions given by @pasko-zh.

@pasko-zh I have tried your tweaks:

wl -i eth6 down
wl -i eth6 country ALL
wl -i eth6 country_abbrev_override "US"
wl -i eth6 regulatory 1
wl -i eth6 chanspec 36/160
wl -i eth6 up
wl -i eth6 5g_rate auto
wl -i eth6 txpwr1 -o -m 1496

The problem is that the interface/UI isn't in sync, and without running your commands, it still shows the correct nvram adjustments:

wl -i eth6 country (#a (#a/0) <unknown>)
wl -i eth6 chanspec (48/160 (0xeb32))
wl -i eth6 txpwr1 (TxPower is 127 qdbm, 31.75 dbm, 1496 mW  Override is Off)

[pasko-zh]

With wl command you modify the driver directly, i.e. in RAM, without changing anything in NVRAM. The GUI reads everything from NVRAM, therefore, you will only see what is stored there and not what you changed via wl command.

If one would like to persist wl command instructions, then a) put them in shell script and or b) put them in a startup script.

btw, was a good idea to move it from gist to github repo

[francoism90]

@pasko-zh Thanks for your reply. :)

I'm confused, since it's NVRAM passing changing to the wireless-interface(s). If you save in the GUI (or CLI), it should read and overwrite the current NVRAM parameters, and restart/reload the wireless service. By not using nvram commit, is should only overrule in memory, right?

Setting values using wl can also become an issue when you use AiMesh (like I do), since the NVRAM parameters aren't being synced.

I think you may need both of them, but my testing with wl overruling only, didn't work.

[pasko-zh]

Maybe we could add also a section in the readme how to work with wl commands?
When I find time, I could do pull request.

[francoism90]

@pasko-zh That's perfectly fine, ty.

I was thinking of moving a few things to the Wiki, this will keep the README minimal.