NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
BillYoung
Nov 21, 2019Luminary
2.5.0.40 Attached Devices Issue on RBR50/RBS50
To whom it may concern: I have upgraded my Orbi system to 2.5.0.40 from 2.5.0.38 to fix the issue with naming devices. After the upgrade, i noticed an issue with the Attached Devices screen. I ...
- Nov 21, 2019
Try a factory reset on the RBR and setup from scratch and see if this resolves what your seeing.
BillYoung wrote:To whom it may concern:
I have upgraded my Orbi system to 2.5.0.40 from 2.5.0.38 to fix the issue with naming devices. After the upgrade, i noticed an issue with the Attached Devices screen. I have captured the information below to show the issue clearly:
#: 4Device Name: Elaine's PC
DEV-D5:0E:7F
192.168.1.1
IP Address: 192.168.1.1
MAC Address: 00:23:6A:D5:0E:7FConnected Type: Wired
Connected ORBI: Orbi Router
A0:40:A0:54:AD:F2If you notice the device appears to be my wife's PC. But notice the IP address of 192.168.1.1 and that the device appears to be wired to the Orbi router. Rest assured, the device in question is indeed NOT WIRED to the ORBI router, and the IP address shown is the IP Address for the modem. As my Orbi router is in AP mode, I would expect to see the modem in the list.Now I know I can correct this issue easily enough through the recently fixed naming of devices. But why did this fix cause this issue to appear?
CrimpOn
Nov 21, 2019Guru
Alas, I fear there is no "whom it may concern" here. This community forum is built around some volunteers who found solutions to problems on the forum and decided to (attempt to) help people who have questions. We are not Netgear employees.
What is fairly obvious is that firmware 2.5.0.38 and 2.5.0.40 no longer appear as "available firmware" on the Orbi Firmware Update page. Read any of the posts with these numbers in the title and you will see complaints, frustration, anger, and disappointment. Some users have found that the firmware "works for them" and simply ignore the glaring issues which annoy others. It appears that most have decided to "go back" to firmware 2.3.5.30 and wait for Netgear to "try again."