How to configure the switch to prevent IP scanning
In this example, we will use Anti-ARP Scan to prevent attackers from identifying all network devices in the local area network. ARP Scanning is a method by which attackers send multiple ARP request packets in a very short period of time to flood across the entire broadcast domain.
All network IP addresses and subnet masks are used as examples in this article. The Access Point in this section uses the default Radio and SSID Profile. For this section, we will refer to “Zenmap” as the IP Scanning tool. All UI displayed in this article are taken from the XGS4600 series switch.
1. Configuration in the Switch
1-1. Access the Switch’s Web GUI.
1-2. Go to Advance Application > Anti-Arpscan > Configure. Check the Active box and configure the uplink port (port 24) as “Trusted” state. Click Apply.
1-3. (Optional) Go to Advance Application > Errdisable > Errdisable Recovery. Check the Active box and anti-arpscan box. Click Apply.
2. Test the Result
2-1. Download and install an IP Scanning software into Host-A and Host-C.
2-2. Connect Host-A and Host-B via the Wireless Access Point.
2-3. Host-A should initiate a scan for IP address 192.168.1.1 to 192.168.1.20.
2-4. Host-A should no longer be able to reach the USG.
2-5. Access the Switch’s Web GUI. Go to Advance Application > Anti-Arpscan > Host Status. An entry for Host-A should appear with an “Err-Disable” state.
If Errdisable Recovery has been configured, the Host-A entry should recover after the Errdisable Recovery Interval. Host-A will be able to reach the USG, afterwards.
2-6. Host-B should still be able to reach the USG.
2-7. Connect Host-C to the Switch.
2-8. Host-C should perform a quick scan for IP address 192.168.1.1 to 192.168.1.100.
2-9. Host-C should no longer be able to reach the USG.
2-10. Access the Switch’s Web GUI. Go to Advance Application > Anti-Arpscan. Port 2 should now be in an Err-disabled state.
If Errdisable Recovery has been configured, Port 2 state should change to forwarding after the Errdisable Recovery Interval. Host-C will be able to reach the USG, afterwards.
3. What Could Go Wrong
3-1. If access to servers or the local gateway is no longer possible after enabling Anti-Arpscan, make sure that only ports directly connected to hosts or Wireless Access Points are “untrusted”. Ports to servers and the local gateway should be “trusted”.
3-2. If all hosts connected through a Wireless Access Point can no longer reach the local gateway, check whether the port to the Wireless Access Point has changed to the err-disable state in Advance Application > Anti-Arpscan. If so, consider increasing the Port Threshold in Advance Application > Anti-Arpscan > Configure.
- 7.4K All Categories
- 1.5K Nebula
- 46 Nebula Ideas
- 49 Nebula Status and Incidents
- 4.2K Security
- 212 Security Ideas
- 845 Switch
- 34 Switch Ideas
- 731 WirelessLAN
- 11 WLAN Ideas
- 4.8K Consumer Product
- 123 Service & License
- 252 News and Release
- 81 Success Stories
- 44 Security Advisories
- 6 Education Center
- 559 FAQ
- 266 Nebula FAQ
- 127 Security FAQ
- 73 Switch FAQ
- 70 WirelessLAN FAQ
- 7 Consumer Product FAQ
- 34 Nebula Monthly Express
- 62 About Community
- 37 Security Highlight