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...
Really? Did you apply the v40 FW and continue or did you do a factory reset? Just curious here.
gadget13 wrote:Looks like the naming issues have been resolved with v2.5.0.40
I simply applied the v40FW to the router and satelites.
After they reboot the device name duplication was gone and I was able to start setting names as I wanted.
I manually updated my firmware from V2.5.0.38 to V2.5.0.40 to see if it would also fix the device naming issue. It did for some devices, but others it will not allow me to change. So the v40 hot fix did not resolve the device naming issue. Note that I did not do a factory reset as it takes me hours to reconfigure the device manually.
Netgear has abosolutely no clue whatsoever about how to fix this devices issue. And, it may be because nobody at Netgear is in sync with respect to this issue existing. Device renaming and devicy type selection is completey BROKEN at all levels and it exists with Orbi and RAXxxx series routers. And, it has been there for several firmware level nows. I've tried 3 fresh RBR50's and they all exhibit the devices issue so has nothing to do with resetting to factory default to fix it. And, today I received a note from Netgear support to update to 2.5.0.30 to address my issue (unless he meant 2.5.0.40) which I see here as may or may not fixing the devices issue. I'm at 2.5.0.38 and devices is broken there as it is broken on 2.5.0.30. And, like I said in another post - they release 2.5.0.38 with updated device type selections as a feature of this release BUT device renaming and device type selection doesn't work - how would they have tested this as passed????
You might give v40 a try and see if it works for you, if not you can always revert back. Won't know unless you try.
I would factory reset the RBR and setup from scratch to give the new FW a chance to detect your devices correctly if you choose to give v40 a try.
migsta wrote:Netgear has abosolutely no clue whatsoever about how to fix this devices issue. And, it may be because nobody at Netgear is in sync with respect to this issue existing. Device renaming and devicy type selection is completey BROKEN at all levels and it exists with Orbi and RAXxxx series routers. And, it has been there for several firmware level nows. I've tried 3 fresh RBR50's and they all exhibit the devices issue so has nothing to do with resetting to factory default to fix it. And, today I received a note from Netgear support to update to 2.5.0.30 to address my issue (unless he meant 2.5.0.40) which I see here as may or may not fixing the devices issue. I'm at 2.5.0.38 and devices is broken there as it is broken on 2.5.0.30. And, like I said in another post - they release 2.5.0.38 with updated device type selections as a feature of this release BUT device renaming and device type selection doesn't work - how would they have tested this as passed????
This was all good until I logged in from my phone using the ORBI app. As soon as I did that the names all went to crap. Duplicates came back, names changed, etc. It was working just fine when I was only using the web interface on the PC.
It looks like there are multiple database entries for different names used at one time or another and when I used the phone app it started pulling from one of those.
It's possible this is a orbi app issue as well.
If you don't use the app and just use the UI, do the device names remain correct if you get them back in a correct condition?
gadget13 wrote:This was all good until I logged in from my phone using the ORBI app. As soon as I did that the names all went to crap. Duplicates came back, names changed, etc. It was working just fine when I was only using the web interface on the PC.
It looks like there are multiple database entries for different names used at one time or another and when I used the phone app it started pulling from one of those.
I haven't tried that.
Also having a new issue - two lockups on the router over the last two days with this firmware.
Since you said that you didn't seem to do a factory reset after loading this version of FW, and now your seen these lock ups, I would give a factory reset on the RBR and setup from scratch a try. Something maybe getting hung up with the newer version of FW and some lingering older FW code may need to be cleared out.
gadget13 wrote:I simply applied the v40FW to the router and satelites.
After they reboot the device name duplication was gone and I was able to start setting names as I wanted.
FURRYe38 wrote:Since you said that you didn't seem to do a factory reset after loading this version of FW, and now your seen these lock ups, I would give a factory reset on the RBR and setup from scratch a try. Something maybe getting hung up with the newer version of FW and some lingering older FW code may need to be cleared out.
gadget13 wrote:I simply applied the v40FW to the router and satelites.
After they reboot the device name duplication was gone and I was able to start setting names as I wanted.
I did a factory reset which seems to have resored my router stability. The naming problems continue - what a mess.
It's really goofy to see things like one of my satellites listed as wirelessly connnected to my other satelite and both of them name the same thing. I can set my static assignments - and names - just fine. These do not, however, get reflected anywhere else. These firmware releases continue to name things whatever they want.
Oh well - it's on the internet, it routes my packets, and I can continue to do internety things :) Nice work NETGEAR!
