Posted: Mon Jan 03, 2022 23:43 Post subject: NVRAM changes - old values still being used?
I noticed sometime in the past year or so that the wi-fi NVRAM variables all changed name from having a prefix of "wl0_" to "wlan0_" (and so on for wl1, wl2).
Can all the wl0_ variables be deleted? I ask because there are certain circumstances which cause a bunch of wl0_ and wl1_ variables to be populated though they don't seem to be used. For example, after an NVRAM erase and a reboot, a bunch of the old variables are populated and seem to just be taking up space in NVRAM.
Also, I am looking for what the replacement to the old NVRAM variable "landevs" is. It was a space separated list of active interfaces.
Joined: 04 Aug 2018 Posts: 1328 Location: Appalachian mountains, USA
Posted: Tue Jan 04, 2022 16:09 Post subject:
In my model router, the old vars like ath0_foo were replaced with wlan0_foo variables. Eventually I did delete the old variables with no apparent ill effects. YMMV. _________________ Six Linksys WRT1900ACSv2 routers on 48141: VLANs, VAPs, NAS, client mode, OpenVPN client (AirVPN), DDNS, wireguard servers and clients (AzireVPN), three DNSCrypt DNS providers (incl Quad9) via VPN clients.
Sometimes a hard reset is necessary, same for clearing your browser cache.
Agreed. But in this case, removing all the wl_, wl0_, wl1_, wl2_ vars causes defaults to be repopulated. Same thing with an nvram erase and reboot. I suspect that whatever tests for erased nvram and repopulates it with default values on reboot is still repopulating the old deprecated wl?_ variables. Which is why I was curious if the old ones were still used at all.
I went digging through the source and found about a bajillion references to the old variable format in the init process where it sets up default values. Whatever switch from wl0_ -> wlan0_ notation is happening, looks like it's not complete yet.