NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Repeated broadcast storms when using a wired satellite with RBR50
I am using RBR50 with one RBS50 satellite wired to a port on the Router. The RBR50 is in router mode. I have the latest firmware (V2.1.4.16) on both the router and satellite. I have read the threads ...
What all connected to the RBR and Satellite when this happens?
The reserved IP address of the satellite needs to fall in the range of the default IP address pool of the router. Now out side of it. If it's out side then a STATIC IP address would be placed ON the satellite. Not the router.
Is Daisy Chain enabled or disabled on the router? Should be disabled for wire connected satellites
What all connected to the RBR and Satellite when this happens?
>> In addition to what I mentioned below, there is a connection from a netgear fast ethernet switch to the RBR50 with other wired devices (PC's, printer) behind it. All other devices (about a dozen) are connecting over wifi to either the RBR50 or RBS50 depending on where they are in the house.
Interesting that the reserved IP address needs to be in the range of DHCP assigned IP address. What does that have anything to do with a broadcast storm? Yes, I could put a static ip address on the satellite and the reason I didn't do it is to avoid messing with multiple devices and forgetting about it, as well as avoiding the potential of a DHCP bug in the RBR50 causing IP address conflicts. (if Netgear can let broadcast storm slip out like these, anything is possible). --- disclosure: I am IP and DHCP literate, if its not already obvious.
Daisy Chain was enabled and I have just disabled it. Will boot up the Satellite now and see how things go. The network was stable for a few days before this happened again, so let's see if the daisy chain switch does something. My bet is that Netgear has a pretty serious bug hiding in there that they need to debug and fix.
>>Daisy Chain was enabled and I have just disabled it. Will boot up the Satellite now and see how things go.
Well, this failed miserably! The moment the satellite came up, the network went nuts. Wireshark shows ARP storms galore originating from multiple machines (including my desktop). Powered down the satellite and everyone calms down immediately.
Any other suggestions?
NETGEAR, are you listening??
Standard Networking configurations with static IPs are that they are designed to work outside of the routers IP address pool. The pool is meant for reserved IP addresses. Handling of Static IP addresses is assigned ON devices, not on the router. Any reservation IPs are done on the router with in the default DHCP IP address pool. Just trying to help you keep a good working configuration and avoid any issues that maybe causing problems. Lets do it the right way if possible. :smileywink:
Yes, Daisy Chain should be distable for wired backhaul connections with satellites.
Also you can swap out this one satellite and test with the other one if needed...Keep us posted.
Thanks for trying to help. I *do* appreciate it :-)
I think at this time, the one item remaining to try and isolate is to move my desktop PC off of the port on the RBR50 and behind the nertgear switch. If that doesn't work, I am out of ideas. Will post the result once I get around to it.