NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBS850 Incorrectly Connects Powerline Adapter as a Backhaul on Power Failure
I have an RBR850 and multiple RBS850 satelites. One of my satelites has a TP-Link Powerline WiFi Extender plugged into the Ethernet port. This works to use Ethernet over Power Line to get a network...
Inside the safe is the TL-WPA8631P which is an EoP to WiFi AP. Also in the safe are WiFi-based monitors.
That’s an interesting idea to delay the inside device. I did find a delay timer, RIBTD2401B, and it is exterior rated and connects with a knockout mount so I think I can make it work. Probably a couple extra dollars than another solution, but I am one and done here vs. patching something together.
Fingers crossed!
That’s an interesting idea to delay the inside device. I did find a delay timer, RIBTD2401B, and it is exterior rated and connects with a knockout mount so I think I can make it work. Probably a couple extra dollars than another solution, but I am one and done here vs. patching something together.
Fingers crossed!
This note on the Amazon description of the TP-Link product gives me concern:
I have not yet found an actual User Manual for this product. There appears to be software for different operating systems to set up and manage the device. Perhaps there is a setting that might say, "Turn off the OneMesh feature on this device."
- You may be on to something there. OneMesh was off, but I poked around and I see a way to turn DHCP off vs. automatic. Maybe when it comes up and cannot get an IP it turns on DHCP. I’ll try that tomorrow and report back.
Hope you have been able to disable DHCP on the TP-Link and see what happens.
There is a very real possibility that the satellite has accepted the DHCP offer from the TP-Link and is "stuck" trying to sync with the router. My reasoning is as follows:
- The satellite "knows" that the router is the DHCP server. (Correct for 99.9% of residential users, but not 100%.)
- When a satellite powers up, it broadcasts a DHCP request through every port (WAN, LAN, WiFi, perhaps even the WiFi backhaul channel) It accepts the first DHCP offier it gets.
- When the router is the only DHCP server, then the satellite may get the same IP offer through both a 'wired' and a 'WiFi' pathway. It can now communicate with the router.
- When the satellite gets a totally different offer from the TP-Link:
- It now believes it has an IP address that may not be compatible with the router LAN subnet at all.
- It cannot communicate with the router, not over the Ethernet link and not over any WiFi link.
- You’re probably right. Since this does not have bridge mode (that I can find) disabling DHCP pretty much killed it.
I’ll just delay startup and call it good. I would think that if the TP-Link does not perform DHCP, that it would send the device broadcasts "up the network" until the Orbi DHCP server responded. I do not know how long devices keep asking for DHCP when they do not get a response. (hmmm one more thing to research).
Closing this out. It does indeed seem that the Power Line Adapter was seen as a "wired backhaul" and I was not able to configure my way out of it. I put a time delay relay on it, set for 6 minutes, and the Satellite now correctly connects to the wireless backhaul before the Power Line Adapter comes up.
All is well, just a few more bucks. 🙂