My home automation system is happier making connections to devices by IP address.... Alarm system, cameras, Sonos X8, stereo amps, TVs (to turn them off at night), ceiling fans x4 etc.
And then the 8 alexa devices with static IPs makes debugging log files in the HA platform easier.
It just makes things more organized and easier to see what is going on when I add a new device with having ranges for device types.
My home automation system is happier making connections to devices by IP address.... Alarm system, cameras, Sonos X8, stereo amps, TVs (to turn them off at night), ceiling fans x4 etc.
And then the 8 alexa devices with static IPs makes debugging log files in the HA platform easier.
It just makes things more organized and easier to see what is going on when I add a new device with having ranges for device types.
Getting that script to work reliably for people moving from 380 to 384 will be tricky. Asus now enforces size limitations on each nvram setting. It means that if you are importing settings from a version that didn't have such validation and now some of these settings are too large to fit on the new firmware, you will end up with either truncated/corrupted settings, unless the script can somehow validate the size of each and every setting.
The big problem with using the tool to migrate from 380 up to 382/384 is the new length limits imposed on the nvram vars (there's a separate allowed length parameter specified for each variable). If you have a variable that exceeds the limits, dhcp_staticlist for example for someone with a lot of manual assignments) it will silently fail the restore.
Can you run a quick test for me to see if when running 'nvram set' from the command line and attempt to exceed the byte limit on a variable.....does it truncate or does the command line tie into the validation code and post a fail?
Can you run a quick test for me to see if when running 'nvram set' from the command line and attempt to exceed the byte limit on a variable.....does it truncate or does the command line tie into the validation code and post a fail?
I've run into this via SSH when you hit the limit it simply stops allowing any more characters. You can type/paste all you want and the cursor won't move. (this is with Putty)
I've run into this via SSH when you hit the limit it simply stops allowing any more characters. You can type/paste all you want and the cursor won't move. (this is with Putty)
Wow, that totally saved me a day's work reloading all those reservations. I've been putting off changing my IP schema because I thought it was going to be a complete PITA but you've made light work of it with that little nugget. Cheers bro
Wow, that totally saved me a day's work reloading all those reservations. I've been putting off changing my IP schema because I thought it was going to be a complete PITA but you've made light work of it with that little nugget. Cheers bro
Paste the contents of the saved value. Be careful not to paste any line breaks. It may be too long, too. If you have problems you may want to move to using dnsmasq config for static leases.
In that case you can edit /jffs/dnsmasq.config.add and add a line like the following for each static host:
nvram set dhcp_staticlist="`cat dhcp_staticlist`"
nvram set custom_clientlist="`cat custom_clientlist`"
How does one get the wireless log entries to reflect the same dhcp list as present in Network Map - view List -
Ive restored using the above commands but my wireless log entries are still not aligned to this list
nvram set dhcp_staticlist="`cat dhcp_staticlist`"
nvram set custom_clientlist="`cat custom_clientlist`"
How does one get the wireless log entries to reflect the same dhcp list as present in Network Map - view List -
Ive restored using the above commands but my wireless log entries are still not aligned to this list
therestore command worked fine for the network map - view list AND for DHCP manual assignments. BUT not for Wireless Log. Obviously there is another nvram command to restore the wireless log assignments since it defaults to original and not customised as per above. Im just missing the nvram command to backup and restore wireless log - Anyone know what that is please?
No there isn't another variable. It's meant to get that information from the network map, but (AFAICT) only if the device doesn't have a hostname. This feature was only introduced in 384.7-beta1.
Code:
hostname = client[2]; // Name
if (nmapentry && (hostname == "*" || hostname == "<unknown>")) {
if (clientList[mac].nickName != "")
hostname = clientList[mac].nickName;
else if (clientList[mac].name != "")
hostname = clientList[mac].name;
}