Can't change icons of attached devices

As a further troubleshooting of this issue I suggest doing the following telnet printout which will give us some information about why Orbi is behaving the way it does:

1. Check the MAC address of the device you have issue with, let's say it's xx.xx.xx.xx.xx
2. Enable telnet on the Router (from the /debug.htm page of the web interface)
3. telnet to router from your computer
4. After loggin in, run the following print comands on the command line:
1. nvram show | grep xx.xx.xx.xx.xx
5. Repeater the same procedure and do the same printout in the Satellite.

I'll go first... One day last week I added 3 switches to my network, and tried to rename/remodel/retype all three, just like I had done with 4 other switches, exact same models, successfully. But this time, two of them were a success, the remaining one only took the name. To this day, I cannot set the model/type on that one. Plus, since then I added more devices to my network, things like PC/XBox/BluRay etc., and I could rename/remodel/retype them all. Netgear Support is insisting on "Save config, reset, reboot, restore, try again" and I am NOT doing that because I don't trust the firmware that seems to have such silly bugs destroy my TONS of settings & customizations that built up over the last two months.

So, I did nvram show on all three recent equivalent devices. "Gameroom1" and "Gameroom2" seem to have everything. Noticeably, "North Bedroom" is missing both of the orbi_dev_name_ntgrXX and orbi_dev_type_ntgrXX entries, and has an extra orbi_hid_mac that the other two don't; what is that?

*** nvram show | grep 08:36:C9:16:04:C4

access_control51=0 08:36:C9:16:04:C4 0 56335 Unknown 1 0
orbi_dev_name_ntgr49=08:36:C9:16:04:C4 34 Netgear
orbi_dev_type_ntgr49=08:36:C9:16:04:C4 1 1
orbi_dev_name57=08:36:C9:16:04:C4 Gameroom2 8x Switch GS108Tv3
reservation10=192.168.1.12 08:36:C9:16:04:C4 Gameroom2 8x Switch GS108Tv3

*** nvram show | grep 08:36:C9:15:FF:9C

access_control52=0 08:36:C9:15:FF:9C 0 56340 Unknown 1 0
orbi_dev_name_ntgr50=08:36:C9:15:FF:9C 34 Netgear
orbi_dev_type_ntgr50=08:36:C9:15:FF:9C 1 1
orbi_dev_name56=08:36:C9:15:FF:9C Gameroom1 8x Switch GS108Tv3
reservation9=192.168.1.11 08:36:C9:15:FF:9C Gameroom1 8x Switch GS108Tv3

*** nvram show | grep 08:36:C9:16:03:10

orbi_hid_mac=08:36:C9:16:03:10
access_control56=0 08:36:C9:16:03:10 0 56333 Unknown 1 0
orbi_dev_name58=08:36:C9:16:03:10 North Bedroom 8x Switch GS108Tv3
reservation11=192.168.1.13 08:36:C9:16:03:10 North Bedroom 8x Switch GS108Tv3

So, I am now wondering if I could set them through telnet. I am not at all pro with that stuff. But, looking at all the nvram show | grep dev_name and nvram show | grep dev_type, it seems "54" is the next unused slot for model/type. Could I do the following?

nvram set orbi_dev_name_ntgr54=08:36:C9:16:03:10 34 Netgear
nvram set orbi_dev_type_ntgr54=08:36:C9:16:03:10 1 1

nvram commit

Would that hurt/brick my router?

Thanks

Tuna

PS: These switches are directly connected to the router via a wired path. No satellite is involved.

Not sure if that will help.  I 'dumped' NVRAM on my RBR50 and RBS50, sorted everything alphabetically, and set up a comparison.  (At least on my system) the router has two tables that are not present on the satellite:

Router                Satellite

reservationxx         Not present on satellite

orbi_dev_namexx       Present, but not identical

orbi_dev_name_ntgrxx  Not present on satellite

The satellite has nothing to do with assigning IP addresses, so it does not need the "reseravation" table, and

the satellite Connected Devices (not "Attached") does not show the icons, so it does not have that table, either.

I was surprised to learn that the orbi_dev_name table on the satellite was missing an entry that is on the router.  My guess is that this device has never connected to the satellite, and thus the satellite has never had occasion to ask for its name.  Actually, that is totally incorrect because the satellite has names for devices which are wired directly to the router.  Thus, I have no explanation.

All my stuff is connected to the router. Nothing is wire-connected to a satellite. By hanging my satellites' wired backhaul to switches, I make sure that they are ONLY responsible for extending the wireless SSID network instead of also acting as wired network switches. So, every wired device on my network, including the satellites, and essentially wired back to the router via wired switches. So, missing variables for type+model in my case are only relevant on the router.

Tuna

---

tuna_ertemalp wrote:

.........

nvram set orbi_dev_name_ntgr54=08:36:C9:16:03:10 34 Netgear
nvram set orbi_dev_type_ntgr54=08:36:C9:16:03:10 1 1

nvram commit

........

---

This is exactly what you need to do.

If you're sure that slot 54 is empty then please go ahead and enter the commands as you stated above, but adding quotations to the commands or follow the following:

You can first print the existing values to make sure they're empty and to set them back to their original back if ou want to roll back the changes.

1. config get orbi_dev_name_ntgr54
2. config get orbi_dev_type_ntgr54
3. config set orbi_dev_name_ntgr54="08:36:C9:16:03:10 34 Netgear"
4. config set orbi_dev_type_ntgr54="08:36:C9:16:03:10 1 1"
5. config commit

YES! YES! OMG! YES! THAT WORKED! YES!

:smileylol:

I am so glad I stuck my nose into this thread and got this solution. Thank you!

Only if the Netgear Support asked for this info instead of telling me to backup/reset/reboot/restore the router first...

Tuna

I don't know if this sort of approach will fix it for Rikerrock or CrimpOn, so I am not marking your response as a Solution. It certainly solved mine, but I will leave the honor of marking it as such to the person who started the thread...

---

tuna_ertemalp wrote:

......

I am so glad I stuck my nose into this thread and got this solution. Thank you!

......

 

---

I'm glad that this helped! :)

---

CrimpOn wrote:

......

I was surprised to learn that the orbi_dev_name table on the satellite was missing an entry that is on the router.  My guess is that this device has never connected to the satellite, and thus the satellite has never had occasion to ask for its name.  Actually, that is totally incorrect because the satellite has names for devices which are wired directly to the router.  Thus, I have no explanation.

---

The orbi_dev_name table should be identical between Router and Satellite. It's the Router who always update the Satellite when you click Apply when setting the IP reservations or when changing the device names in the Attached Devices list.

In fact, if you factory reset the Satellite. Then the Router will -while doing "Config Sync" when you add the Satellite to the Router- will copy -among other things- this table to the Satellites completely as it is in the Router.

---

ekhalil wrote:

As a further troubleshooting of this issue I suggest doing the following telnet printout which will give us some information about why Orbi is behaving the way it does:

1. Check the MAC address of the device you have issue with, let's say it's xx.xx.xx.xx.xx
2. Enable telnet on the Router (from the /debug.htm page of the web interface)
3. telnet to router from your computer
4. After loggin in, run the following print comands on the command line:
1. nvram show | grep xx.xx.xx.xx.xx
5. Repeater the same procedure and do the same printout in the Satellite.

---

Rikerrock Please follow this procedure for your printer so we can get this fixed.

I'll try that when I get home

THanks

---

ekhalil wrote:

---

tuna_ertemalp wrote:

1. config set orbi_dev_type_ntgr54="08:36:C9:16:03:10 1 1"
2. config commit

---

I remain "confused".  When I dump NVRAM, I do not see any variables named orbi_div_type_ntgrxx

So, there are variables that respond to "get" and "set", but not to "show"?

Just to make sure (and, I might have been blind and missed the answer in the earlier parts of the thread): Have you ever gone into the router's web admin page, click on Attached Devices, and then click on at least one device on your network, and change the Device Model, Device Name and Device Type settings from the screen that would show up? If you didn't, these variables might have never been created because the router didn't need them. Since I have done this for every single device on my network, something like ~50-55 devices by now, I do see them in my "nvram show" output: 54 names and 11 types, actually. And, that is a bit strange. I did a nvram show on another switch that I properly and manually typed as switch, but its data doesn't have a orbi_dev_type_ntgrXX associated with its MAC address althought it has orbi_dev_name_ntgrXX. So, there must also be some other way each device's type is known to the router. Weird.

Oh, yes.  The reason I dread a "factory reset" is that I have (a) assigned IP addresses, (b) given specific names, and (c) changed the device type spelling (and icon) on over 30 devices.

I just now did a telnet to my Orbi router and entered

config get orbi_dev_type_ntgr2

and got... nothing.  tried a bunch of other numbers as well, such as 3, 4, 5, 6, 7, 8, 9, 10, 21, 31.

And, when I do nvram show there is not a single line spelled orbi_dev_type_ntgrxx. Not one.

I realize that the integer "numbers" are related to icon files.  Would be interesting to see where the heck they are.

---

CrimpOn wrote:

Oh, yes.  The reason I dread a "factory reset" is that I have (a) assigned IP addresses, (b) given specific names, and (c) changed the device type spelling (and icon) on over 30 devices.

Yup. Exactly the boat I am on... :( 

---

CrimpOn wrote:

Oh, yes.  The reason I dread a "factory reset" is that I have (a) assigned IP addresses, (b) given specific names, and (c) changed the device type spelling (and icon) on over 30 devices.

 

I just now did a telnet to my Orbi router and entered

config get orbi_dev_type_ntgr2

and got... nothing.  tried a bunch of other numbers as well, such as 3, 4, 5, 6, 7, 8, 9, 10, 21, 31.

And, when I do nvram show there is not a single line spelled orbi_dev_type_ntgrxx. Not one.

 

I realize that the integer "numbers" are related to icon files.  Would be interesting to see where the heck they are.

---

Do you have any orbi_dev_nameXX and orbi_dev_name_ntgrXX? If so, I wonder if at times the icon implies the type. In which case, why do I even have ANY orbi_dev_type_ntgrXX variables. Lol!

Tuna

Not sure what any of this means:

root@Matrix:/# root@Matrix:/# nvram show | grep 08:36:C9:0B:37:21 satellite1=08:36:C9:11:90:95 192.168.1.90 RBS50 5VF1935K02D98 -95 V2.3.5.30 1 08:36:C9:0B:37:21 wired 1 -95 satellite2=28:80:88:DD:24:99 192.168.1.88 RBS20 5DL88C5X0C61D -95 V2.3.5.26 1 08:36:C9:0B:37:21 wired 1 -95 orbi_dev_name2=08:36:C9:0B:37:21 Matrix satellite3=08:36:C9:11:90:31 192.168.1.43 RBS50 5VF1935L02D99 -95 V2.3.5.30 1 08:36:C9:0B:37:21 wired 1 -95 satellite4=28:80:88:E0:E8:FB 192.168.1.56 RBS20 5DL88C5N0E7B6 -95 V2.3.5.26 1 08:36:C9:0B:37:21 wired 1 -95 access_control46=0 08:36:C9:0B:37:21 0 32966 Unknown 0 0 disconn_sate1=08:36:C9:11:90:95,0,0,08:36:C9:0B:37:21,0 disconn_sate2=28:80:88:DD:24:99,0,0,08:36:C9:0B:37:21,0 disconn_sate3=08:36:C9:11:90:31,0,0,08:36:C9:0B:37:21,0 disconn_sate4=28:80:88:E0:E8:FB,0,0,08:36:C9:0B:37:21,0 root@Matrix:/# root@Matrix:/#

Not sure what any of this means:

root@Matrix:/# root@Matrix:/# nvram show | grep 08:36:C9:0B:37:21 satellite1=08:36:C9:11:90:95 192.168.1.90 RBS50 5VF1935K02D98 -95 V2.3.5.30 1 08:36:C9:0B:37:21 wired 1 -95 satellite2=28:80:88:DD:24:99 192.168.1.88 RBS20 5DL88C5X0C61D -95 V2.3.5.26 1 08:36:C9:0B:37:21 wired 1 -95 orbi_dev_name2=08:36:C9:0B:37:21 Matrix satellite3=08:36:C9:11:90:31 192.168.1.43 RBS50 5VF1935L02D99 -95 V2.3.5.30 1 08:36:C9:0B:37:21 wired 1 -95 satellite4=28:80:88:E0:E8:FB 192.168.1.56 RBS20 5DL88C5N0E7B6 -95 V2.3.5.26 1 08:36:C9:0B:37:21 wired 1 -95 access_control46=0 08:36:C9:0B:37:21 0 32966 Unknown 0 0 disconn_sate1=08:36:C9:11:90:95,0,0,08:36:C9:0B:37:21,0 disconn_sate2=28:80:88:DD:24:99,0,0,08:36:C9:0B:37:21,0 disconn_sate3=08:36:C9:11:90:31,0,0,08:36:C9:0B:37:21,0 disconn_sate4=28:80:88:E0:E8:FB,0,0,08:36:C9:0B:37:21,0 root@Matrix:/# root@Matrix:/#

This is the key to my problem.  How can some of you have a variable named orb_dev_typexx and I do not?

My orbi_dev_name_ntgrxx entries have the MAC address, followed by a number, followed by a description.  I believe the number is an index into the table of device icons.

Just to put an update on this thread: Since my last post here, I have added a bunch of devices to my network, and rather randomly either the Device Model (orbi_dev_name_ntgrXX; I am up to XX=66) and/or the Device Type (orbi_dev_type_ntgrXX) on the Edit Device page didn't result in the correct setting actually taking place, therefore requiring me to go through telnet to create/set the proper config variables. I had also created a support case for this exact issue the first time I had run into it (Case #41517573), but as soon as I "fixed" it manually via telnet and config variable shenanigans, it got closed.

I am not sure if the firmware dev team even has this on their radar, but they absolutely should. This is clearly a bug in the firmware code dealing with the creation of these config variables. It must be error'ing out at certain device names/types or at a certain XX value, or some local buffer is just not big enough and the config creation code is running out of space while trying to do the right thing.

Therefore, I am tagging Blanca_O. This really does need to be escalated.

Thanks

Tuna

I have the same issue. Using the genie interface leads to some devices refusing to accept the device name I enter or not switching to the icon I chose. In the Android app, it readily accepts the name, but sometimes won't display the icon I selected and revert back to whatever it was before I saved.

(Also, changing icons in the Android app updates the icons in the genie interface, but the only problem is that some icons just revert back mysteriously in Android.)

I am having the exact same issue. I can change the names no problem. But only some of the icons change. The remainder go back almost instantly.