NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Satellite does not see Wired device
I'm connecting a wired Ethernet RTU to teh RBR50 Satellite and when configured for DHCP it is not "seen". If I configure the RTU device with a static IP - it is seen and connects perfectly. Why ...
The Ethernet RTU is produced by Eybond: http://www.eybond.com/page193?_l=en#bb
Again it works with other routers in DHCP mode and works fine with a static IP - just doesn't seem to accept DHCP from the Orbi RBR50 (main or satellite). Access Control is disabled. Since it seems no IP is assigned, "arp -p" does not see the device either (not unexpected).
Any further diagnostic suggestions welcomed!
mikebp wrote:The Ethernet RTU is produced by Eybond: http://www.eybond.com/page193?_l=en#bb
Any further diagnostic suggestions welcomed!
My "go to" for issues such as this is Wireshark. On the Orbi debug page (http://orbilogin.net/debug.htm) check the box to Enable LAN/WAN Packet Capture. Click on Start Capture. Perform the test by plugging in the RTU (Remote Terminal Unit. These things look fascinating. Wish I had something to monitor!) Click on Save Debug file and a zip file will be written to the browser Download location. Inside the zip file are WinPCAP files for every packet that appeared on the WAN port and that hit the Orbi router LAN.
Wireshark should show the RTU sending a DHCP request. (Wireshark can filter the display by MAC address and protool.)