This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
The devices connected wirelessly to my R7900P router are listed mostly by MAC address alone. The device name is blank in most cases. How can I edit this field in the routerlogin.net screen so I can see a "simple" name for each device, rather than have to look up each MAC address each time? This router is running under Windows 10, firmware version V1.0.1.8_1.0.68.
The simple name field appeared to be editable when QoS was enabled. In fact, many of the columns of data in the attached devices screen change (for unknown, and non-understandable reasons) when you enable QoS. It's really irritating and limiting. Also, the name field isn't stored with permanence in a database...it can change across reboots-which is really strange. You'd think that the device would keep a database with MAC addys in non-volatile memory, but it doesn't appear to-which is disappointing, tbh.
I downloaded and installed the firmware update, but I still don't see any setting to provide device names to my connected devices. I see the MAC addresses and IPs, but the device names are mostly blank.
The simple name field appeared to be editable when QoS was enabled. In fact, many of the columns of data in the attached devices screen change (for unknown, and non-understandable reasons) when you enable QoS. It's really irritating and limiting. Also, the name field isn't stored with permanence in a database...it can change across reboots-which is really strange. You'd think that the device would keep a database with MAC addys in non-volatile memory, but it doesn't appear to-which is disappointing, tbh.
Thanks much for that answer. Enabing QoS allowed me to edit and rename the devices that were missing names. I posted this question five months ago, but yours was the first response that did anything to solve the problem.
I found that with QoS enabled I got all those nifty whiz-bang features like naming and whatnot, but it caused my VoIP phone and conference call services to hang up and disconnect. So I ended up reverting, unfortunately.
Too bad, too-I'm the perfect candidate for it with my many devices and limited bandwidth.
