one feature you will find there is an advanced attached device list that will help see what devices are connect to the router or sat and what band they are connected to
The list of attached devices is in the normal (non-debug) admin page. Go to: http://orbilogin.net/index.htm, click on the Attached Devices link on the left.
I was interested in seeing the supposed advanced attached devices list on the debug page with what band the devices were attached to. That isn't shown on the regular attached devices lists. Alas I can't locate it on the debug page. That is what I was asking how to access, not the normal attached devices page.
The link is dead, can you re-post? I'm coming from ASUS routers and it's been extremely tough getting used to this very limited very basic user interface. The features I'm looking for the most are the ability to see which device is using up my bandwidth and also what the signal strength is of every device. If anyone finds this please post.
The link is dead, can you re-post? I'm coming from ASUS routers and it's been extremely tough getting used to this very limited very basic user interface. The features I'm looking for the most are the ability to see which device is using up my bandwidth and also what the signal strength is of every device. If anyone finds this please post.
to have that level of monitoring you are best to use your asus as a router and the orbi in AP mode and get the best of both worlds
Are you talking about the "attached devices list" or the debug.htm page itself?
Because I can't find anything in the normal firmware pages that links to debug.htm; I had to type it in myself. (And having seen it now, I'm curious to know what, exactly, the "Network Session" counter is counting, and what happens when it reaches the stated max...)
The attached devices list, of course, isn't hidden.
The "hidden feature" is the ability to see more detail about the connected devices, e.g. wired versus wireless, and connected band. As detailed in an earier post on this board, this feature can be enabled by changing a variable on the router. Do so at your own risk!
- Go to the debug page and enable telnet
- Telnet into the router
- Execute the following:
nvram set enable_adv_attached=1
nvram commit
- Exit telnet
- Go to the debug page and disable telnet (please don't forget this step!)
Yeah, the enable_adv_attached variant is somewhere between "way way better" and "infinitely better". Dunno why that isn't the default, but at least the functionality is still there!
I agree! It's very useful to see the additional details. A lot is still missing though.
I run another brand of access points at another site and they provide complete information for each client: mode, TX rate, RX rate, channel, RF band, signal strength, uptime. It's frustrating how little information is available on the consumer stuff.
I agree! It's very useful to see the additional details. A lot is still missing though.
I run another brand of access points at another site and they provide complete information for each client: mode, TX rate, RX rate, channel, RF band, signal strength, uptime. It's frustrating how little information is available on the consumer stuff.
but that is the point , the orbi is a coustomer level device that for the most point ppl want to plug and play and dont care about whats under the hood , make it too complex and you start to lose the concept it was initially designed around , i still see ppl wanting ethernet backhaul which to me makes no sense to buy the orbi if you already have structured cabling in place
I agree on the wired backhaul. I think access points are a better solution to extend WiFi coverage if you have the wires. The reason I have the Orbi here is because I have no easy way to wire the house, plus I have a large property that can use longer reach outside.
I understand your point about keeping things simple. However, I believe Netgear could include more details on attached clients without making the devices any more complex to use. It's just information, not a setting to fiddle with.
Yeah, the enable_adv_attached variant is somewhere between "way way better" and "infinitely better". Dunno why that isn't the default, but at least the functionality is still there!
So it turns out that changing the Orbi from router made to AP mode resets this option. No big deal, do the telnet dance and turn it back on. HOWEVER... it doesn't actually do anything in AP mode. My "attached devices" page still groups all client devices at the bottom no matter whether they're on the main Orbi or on a satellite.
yes it has changed and i assume will change again before its finished , however its easy enough to see whats connect to sats by accessing their web pages
I was able to get to the debug page and click on the enable telnet. However I don't know what to do next to be able to enter in the command suggested. Can someone provide detailed steps?
