NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Where are the device names located when in a telnet session?
Several of us are having issues renaming devices on our network. I want to take the GUI out and go to the source via a telnet session. So my question is - where is the device name stored so that I ca...
If the Orbi is on firmware 3.5.0.38, there are a plethora of posts complaining that device tables are "broken". I believe several of them tried the telnet method (and failed). (I am often incorrect, but I recommend browsing through the posts that have 2.5.0.38 in the title.)
Upon reading the post again, my response seems a bit presumptuous. It's not my place to tell someone "don't try that!!!"
There is a detailed post showing how to display what the Orbi has for device registrations, names, and types, and how to edit those into telnet commands to set them.
I actually maintain a Notepad++ file (linux, you know, not Windows) that has all my devices. When I want to do a factory reset, I can enter all of my devices in one "copy and paste".
Fearing that 2.5.0.38 has "screwed the pooch" and my telnet file will no longer work, I am thinking seriously of sitting this one out.
Thanks for the post.
V2.5.0.38
This latest FW has done some very strange things when it comes to naming devices.
Ex: See below. This is how one device is listed. Most of the others are crazy named like this too.
It's also listed later with slightly different names and a different IP.
Philips hue bridge BSB002
Dell C1765nf Color MFP
192.168.2.2
v38 has a problem of device naming and detection. NG is aware of it. If it doesn't work for you, you can revert back to last working FW. v38 doesn't effect other operations.
v40 is available however this only fixes the invalid certifiicate problem that has been invalid since v30:
https://kb.netgear.com/000061393/RBR50-RBS50-Firmware-Version-2-5-0-40-Hot-Fix
Up to you if you want to apply it or not.
Looks like the naming issues have been resolved with v2.5.0.40
