NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Quick way to re-enter your IP reservations after factory reset
Many of us hesitate much to go for factory reset mainly because of the load of repetitive work you need to do to restore your IP reservations especially if you have many such reservations.
An easie...
CrimpOn wrote:
......... I am not confident that "saving configuration" would be of much use in my situation, because the ways that my Orbi is disappointing me have appeared since an automatic firmware upgrade and I have continued to enter new device reservations. At this point, I suspect that "something is amiss" that only a reset to factory would address, and I have avoided doing that because of the prospect of typing in all those MAC addresses.
......
Completely agree. usually why I choose to do a factory reset is that I suspect a data corruption somewere and a backup/restore will just get me back to where I was.
CrimpOn wrote:
.....
In addition to device reservations, the NVRAM dump also includes lines like this:
orbi_dev_name12=24:92:0E:31:52:FA Dicks New Tablet
The numbers do not match the "reservation" numbers. Any idea if this is something that could be entered with Telnet commands, or will it propogate automatically?
.......
The entry orbi_dev_name12=24:92:0E:31:52:FA Dicks New Tablet is the "Device Name" that you can edit in the "Attached Devices" list below (in the blue box):
You will also find another entry with the same MAC address like this
orbi_dev_name_ntgr9=24:92:0E:31:52:FA Samsung Tablet that corresponds to the device type (the red box) in the snapshot above.
The numbers do not match. The system uses only the MAC address to match the different entries with each other.
CrimpOn wrote:
........
And.... I presume that changing the device reservations to be in order by IP address would not cause a problem, since the "factory reset" creates a totally empty table. (This is one of my other disappointments with Orbi firmware: that we cannot sort displays by column. This would not help the "attached devices" display, but it would at least cause the reservation table to be in IP order for a little while.
Yes, you can edit the commands as you wish, everything should have been wiped after a factory reset. You can also use the telnet commands to change an existing setting, so if you enter the config command for the same variable twice like this:
config set reservation3="192.168.1.20 A0:99:9B:0B:3F:5B Dicks Macbook"
config set reservation3="192.168.1.20 A0:99:9B:0B:3F:5B The new Macbook"
Then the second command will override the first one.
CrimpOn wrote:
......... I am not confident that "saving configuration" would be of much use in my situation, because the ways that my Orbi is disappointing me have appeared since an automatic firmware upgrade and I have continued to enter new device reservations. At this point, I suspect that "something is amiss" that only a reset to factory would address, and I have avoided doing that because of the prospect of typing in all those MAC addresses.
......
Completely agree. usually why I choose to do a factory reset is that I suspect a data corruption somewere and a backup/restore will just get me back to where I was.
CrimpOn wrote:
.....
In addition to device reservations, the NVRAM dump also includes lines like this:
orbi_dev_name12=24:92:0E:31:52:FA Dicks New Tablet
The numbers do not match the "reservation" numbers. Any idea if this is something that could be entered with Telnet commands, or will it propogate automatically?
.......
The entry orbi_dev_name12=24:92:0E:31:52:FA Dicks New Tablet is the "Device Name" that you can edit in the "Attached Devices" list below (in the blue box):
You will also find another entry with the same MAC address like this
orbi_dev_name_ntgr9=24:92:0E:31:52:FA Samsung Tablet that corresponds to the device type (the red box) in the snapshot above.
The numbers do not match. The system uses only the MAC address to match the different entries with each other.
CrimpOn wrote:
........
And.... I presume that changing the device reservations to be in order by IP address would not cause a problem, since the "factory reset" creates a totally empty table. (This is one of my other disappointments with Orbi firmware: that we cannot sort displays by column. This would not help the "attached devices" display, but it would at least cause the reservation table to be in IP order for a little while.
Yes, you can edit the commands as you wish, everything should have been wiped after a factory reset. You can also use the telnet commands to change an existing setting, so if you enter the config command for the same variable twice like this:
config set reservation3="192.168.1.20 A0:99:9B:0B:3F:5B Dicks Macbook"
config set reservation3="192.168.1.20 A0:99:9B:0B:3F:5B The new Macbook"
Then the second command will override the first one.
Thanks for the confirmation. This is what I'll do.
Have you tried setting the orbi_dev_namexx and orbi_dev_name_ntgrxx entries through Telnet?(I'm not confident where I would click "apply" to have them take effect.)
CrimpOn wrote:
.......
Have you tried setting the orbi_dev_namexx and orbi_dev_name_ntgrxx entries through Telnet?(I'm not confident where I would click "apply" to have them take effect.)
Yes, I tried that, changing the device name by changing orbi_dev_namexx and orbi_dev_name_ntgrxx entries through Telnet does not need any apply. Once you send the config commands you will see the changes on the "Attached Devices"
Please note that there is another parameter in orbi_dev_name_ntgrxx parameter (orbi_dev_name_ntgrxx=24:92:0E:31:52:FA 14 Samsung Tablet) containing information about the device type as you can see in the following post:
Thanks for pointing that out. That's the index into the drop down menu of device types that (although an interesting concept) is worefully out of date. No entry for "Smart Plug", "Light Bulb", "Appliance" (like Microwave), Thermostat, etc.
Still gathering enthusiasm for a reset. I did a restart yesterday, and now my log file is reporting DHCP assignments again. Still no DoS and Port Scan reports.