Yeah, but it's a PITA to do manually from the GUI. You have to delete everything, and then re-add them all in the proper order. If you skip one, or get a new device later, you have to repeat the process. It's much simpler to just extract the data, order it how you want, and then upload it again, and now it's in your preferred order. This makes it super easy to fix on the backend, and to reapply if it ever gets assorted. Plus, you're not running any code on the router, so there's little risk of cauing any problems this way. Plus, it's useful for more than just sorting by IP address. And it works across firmware updates.
Alternate ideas are always interesting to consider.
Just to clarify, the sort is not done on the router. Your browser makes a request for current device information table. That is a low priority request but still runs quickly. Once that info is returned to the browser, the sort and prep are done on your local machine.
I hope this isn't considered a completely stupid comment but I assume you realize that you can easily see attached devices in ip order on the access control page (advanced>security>access control) this gives status, name, address, mac, connection type. The only thing it lacks is the particular orbi it is attached to. Usefully this page also shows devices sometimes seen but not currently connected. Now since Netgear clearly knows how to do this easily why they don't do it elsewhere is a mystery, but at least it is here and easy to access without a lot of messing with the internals
Not a stupid comment at all. After I did the initial IP sort, I found it handy to actually be able to sort on any field. I added that in a second update.
I hope this isn't considered a completely stupid comment but I assume you realize that you can easily see attached devices in ip order on the access control page (advanced>security>access control) this gives status, name, address, mac, connection type. The only thing it lacks is the particular orbi it is attached to. Usefully this page also shows devices sometimes seen but not currently connected. Now since Netgear clearly knows how to do this easily why they don't do it elsewhere is a mystery, but at least it is here and easy to access without a lot of messing with the internals
My previously posted modification only wirh through v2.5.2.4. I have made the necessary updates for v2.7.1.60 and am looking for a couple of testers.
Tester much be able to telnet to router (RBR50) and have some Linux experience replacing files. vi is most likely method although netcat can also work.
If you are running v2.7.1.60 and interested in testing, please DM me.
After a bit more testing, I will most an update for the entire community.
I'm not ready to "take the plunge", however I seem to recall when I was doing "copy and paste" from Windows to Orbi that Notepad creates DOS end of line (<cr><lf>) and Orbi (being Linux) wants only <lf>. So I switched to Notepad++ which allows setting the end of line in the correct mode.
