NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Satellite starts DoS Attack: ARP Attack when connected to Ethernet
Router Firmware Version V2.1.4.16
Last night the internet access when down. After looking for a cause, I found that as soon as the satellite is conected to ethernet it starts an "ARP attack". Samp...
- Unplugging the TPLink switches while connecting the satellites worked! After verifying the network was happy I plugged the switches back in and everything works.
Thanks for the help!
I also have this same exact problem. I had to unplug one of my satellites today and when I powered it back up it initially connects via Ethernet but soon after the status page shows it’s connected wirelessly. Shortly after that my entire network dies. If I unplug the Ethernet from the satellite everything work. The router shows the same ARP attack messages.
It seems like the satellite is back hauling on both Ethernet and wireless and everything gets messed up.
It seems like the satellite is back hauling on both Ethernet and wireless and everything gets messed up.
What FW is currently loaded?
What is the Mfr and model# of the IP modem the Orbi is connected too?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.
I would do a factory reset on the router and satellite and set up from scratch. Try disabling the following:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s). Turn OFF ALL other devices accept for 1 wired PC with the router. Walk thru the setup wizard. Skip adding the satellites during the wizard. After you set up the router and give a new SSID and PW and the router is rebooted. Go in and sync the router and 1 satellite first. You can do this in the same room with the router and satellites. After you get one synced, set an IP address reservation for the 1 satellite. Add, Save and Apply. Turn of the 1st satellite and turn on the 2nd satellite and get it connected. Do the same IP address reservation for the 2nd satellite. Add, Save and Apply. Turn off the satellite and then place each satellite in there remote locations.
Check Connected devices after placing satellites. Check internet access. If good,
Begin to turn on the rest of the home devices.
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
RatChickens wrote:
I also have this same exact problem. I had to unplug one of my satellites today and when I powered it back up it initially connects via Ethernet but soon after the status page shows it’s connected wirelessly. Shortly after that my entire network dies. If I unplug the Ethernet from the satellite everything work. The router shows the same ARP attack messages.
It seems like the satellite is back hauling on both Ethernet and wireless and everything gets messed up.
- Firmware: 2.1.4.16
Modem: Netgear CM500-1AZNAS
4000 sq ft
~35 ft to one satellite, ~45 ft to the otherI'm not sure why any of the wireless settings matter. My problems are specific to ethernet backhaul. If I use wireless, I have no problems other than the satellite that is further away has problems getting a signal from the router (which is why i want to use ethernet backhaul). The second I start using ethernet, the satellite goes nuts, sending a ton of traffic over the wired interface, the router shows the ARP attack in the logs, and my network dies.. As soon as I unplug the ethernet from the satellite everything works fine.I had these problems when I initially setup the network, but after numerous power cycles, everything started working, and has worked for 10 months. Things only freaked out yesterday as I had to power off parts of the system to do electical work.When I try to reserve an IP for a satellite, I get400 Bad Request
This server does not support the operation requested by your client.I've heard that the 2.2 Beta Firmware helps resolve backhaul issues. How can i get involved with that Beta?
FURRYe38 wrote:
What FW is currently loaded?
What is the Mfr and model# of the IP modem the Orbi is connected too?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.I would do a factory reset on the router and satellite and set up from scratch. Try disabling the following:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s). Turn OFF ALL other devices accept for 1 wired PC with the router. Walk thru the setup wizard. Skip adding the satellites during the wizard. After you set up the router and give a new SSID and PW and the router is rebooted. Go in and sync the router and 1 satellite first. You can do this in the same room with the router and satellites. After you get one synced, set an IP address reservation for the 1 satellite. Add, Save and Apply. Turn of the 1st satellite and turn on the 2nd satellite and get it connected. Do the same IP address reservation for the 2nd satellite. Add, Save and Apply. Turn off the satellite and then place each satellite in there remote locations.Check Connected devices after placing satellites. Check internet access. If good,
Begin to turn on the rest of the home devices.
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
RatChickens wrote:
I also have this same exact problem. I had to unplug one of my satellites today and when I powered it back up it initially connects via Ethernet but soon after the status page shows it’s connected wirelessly. Shortly after that my entire network dies. If I unplug the Ethernet from the satellite everything work. The router shows the same ARP attack messages.
It seems like the satellite is back hauling on both Ethernet and wireless and everything gets messed up.What is the Mfr and model# of the ethernet switch if one is in the configuration
Turn OFF ALL other devices accept for 1 wired PC with the router. Walk thru the setup wizard. Skip adding the satellites during the wizard. After you set up the router and give a new SSID and PW and the router is rebooted. Go in and sync the router and 1 satellite first. You can do this in the same room with the router and satellites. After you get one synced, set an IP address reservation for the 1 satellite. Add, Save and Apply. Turn of the 1st satellite and turn on the 2nd satellite and get it connected. Do the same IP address reservation for the 2nd satellite. Add, Save and Apply. Turn off the satellite and then place each satellite in there remote locations.
Check Connected devices after placing satellites. Check internet access. If good,
Begin to turn on the rest of the home devices.
Yes, try the beta as well...
RatChickens wrote:
Firmware: 2.1.4.16
Modem: Netgear CM500-1AZNAS
4000 sq ft
~35 ft to one satellite, ~45 ft to the otherI'm not sure why any of the wireless settings matter. My problems are specific to ethernet backhaul. If I use wireless, I have no problems other than the satellite that is further away has problems getting a signal from the router (which is why i want to use ethernet backhaul). The second I start using ethernet, the satellite goes nuts, sending a ton of traffic over the wired interface, the router shows the ARP attack in the logs, and my network dies.. As soon as I unplug the ethernet from the satellite everything works fine.I had these problems when I initially setup the network, but after numerous power cycles, everything started working, and has worked for 10 months. Things only freaked out yesterday as I had to power off parts of the system to do electical work.When I try to reserve an IP for a satellite, I get400 Bad Request
This server does not support the operation requested by your client.I've heard that the 2.2 Beta Firmware helps resolve backhaul issues. How can i get involved with that Beta?
- None of this setup mentions Ethernet. When setting up Ethernet do you power everything up and get it working wirelessly then plug in Ethernet?
How do I get access to the Beta Firmware?
The central switch being used is a Netgear GS316. This is the main switch being used for backhaul. I also have a TPLink TL-SG108, and 2x TL-SG105. These distribute Ethernet in various rooms.