- Table of Contents
-
- 16-Security Configuration Guide
- 00-Preface
- 01-ACL configuration
- 02-Packet filter configuration
- 03-Time range configuration
- 04-User profile configuration
- 05-Password control configuration
- 06-Keychain configuration
- 07-Public key management
- 08-PKI configuration
- 09-IPsec configuration
- 10-IKE configuration
- 11-IKEv2 configuration
- 12-SSH configuration
- 13-SSL configuration
- 14-SSL VPN configuration
- 15-Session management
- 16-Connection limit configuration
- 17-Attack detection and prevention configuration
- 18-IP-based attack prevention configuration
- 19-IP source guard configuration
- 20-ARP attack protection configuration
- 21-ND attack defense configuration
- 22-Protocol packet rate limit configuration
- 23-Security policy configuration
- 24-Object group configuration
- 25-ASPF configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
20-ARP attack protection configuration | 309.20 KB |
Contents
Configuring ARP attack protection
ARP attack protection tasks at a glance
Configuring unresolvable IP attack protection
About unresolvable IP attack protection
Configuring ARP source suppression
Configuring ARP blackhole routing
Verifying and maintaining unresolvable IP attack protection
Configuring ARP packet rate limit
Configuring source MAC-based ARP attack detection
About source MAC-based ARP attack detection
Verifying and maintaining source MAC-based ARP attack detection
Example: Configuring source MAC-based ARP attack detection
Configuring ARP packet source MAC consistency check
About ARP packet source MAC consistency check
Verifying and maintaining ARP packet source MAC consistency check
Configuring ARP active acknowledgement
Example: Configuring authorized ARP on a DHCP server
Example: Configuring authorized ARP on a DHCP relay agent
Configuring ARP attack detection
Restrictions and guidelines: ARP attack detection
Configuring user validity check
Configuring ARP packet validity check
Configuring ARP restricted forwarding
Ignoring ingress ports of ARP packets during user validity check
Enabling ARP attack detection logging
Verifying and maintaining ARP attack detection
Example: Configuring user validity check
Configuring ARP scanning and fixed ARP
Configuring automatic ARP scanning
Configuring ARP sender IP address checking
About ARP sender IP address checking
Enabling SNMP notifications for ARP
Configuring ARP attack protection
About ARP attack protection
The device can provide multiple features to detect and prevent ARP attacks and viruses in the LAN. An attacker can exploit ARP vulnerabilities to attack network devices in the following ways:
· Sends a large number of unresolvable IP packets to have the receiving device busy with resolving IP addresses until its CPU is overloaded. Unresolvable IP packets refer to IP packets for which ARP cannot find corresponding MAC addresses.
· Sends a large number of ARP packets to overload the CPU of the receiving device.
· Acts as a trusted user or gateway to send ARP packets so the receiving devices obtain incorrect ARP entries.
ARP attack protection tasks at a glance
All ARP attack protection tasks are optional.
· Preventing flood attacks
¡ Configuring unresolvable IP attack protection
¡ Configuring ARP packet rate limit
¡ Configuring source MAC-based ARP attack detection
· Preventing user and gateway spoofing attacks
¡ Configuring ARP packet source MAC consistency check
¡ Configuring ARP active acknowledgement
¡ Configuring ARP attack detection
¡ Configuring ARP packet validity check
¡ Configuring ARP restricted forwarding
¡ Ignoring ingress ports of ARP packets during user validity check
¡ Enabling ARP attack detection logging
¡ Configuring ARP scanning and fixed ARP
¡ Configuring ARP sender IP address checking
· Enabling SNMP notifications for ARP
Configuring unresolvable IP attack protection
About unresolvable IP attack protection
If a device receives a large number of unresolvable IP packets from a host, the following situations can occur:
· The device sends a large number of ARP requests, overloading the target subnets.
· The device keeps trying to resolve the destination IP addresses, overloading its CPU.
To protect the device from such IP attacks, you can configure the following features:
· ARP source suppression—Stops resolving packets from an IP address if the number of unresolvable IP packets from the IP address exceeds the upper limit within 5 seconds. The device continues ARP resolution when the interval elapses. This feature is applicable if the attack packets have the same source addresses.
· ARP blackhole routing—Creates a blackhole route destined for an unresolved IP address. The device drops all matching packets until the blackhole route is deleted. A blackhole route is deleted when its aging timer is reached or the route becomes reachable.
After a blackhole route is created for an unresolved IP address, the device immediately starts the first ARP blackhole route probe by sending an ARP request. If the resolution fails, the device continues probing according to the probe settings. If the IP address resolution succeeds in a probe, the device converts the blackhole route to a normal route. If an ARP blackhole route ages out before the device finishes all probes, the device deletes the blackhole route and does not perform the remaining probes.
This feature is applicable regardless of whether the attack packets have the same source addresses.
Configuring ARP source suppression
1. Enter system view.
system-view
2. Enable ARP source suppression.
arp source-suppression enable
By default, ARP source suppression is disabled.
3. Set the maximum number of unresolvable packets that the device can process per source IP address within 5 seconds.
arp source-suppression limit limit-value
By default, the maximum number is 10.
Configuring ARP blackhole routing
Restrictions and guidelines
Set the ARP blackhole route probe count to a big value, for example, 25. If the device fails to reach the destination IP address temporarily and the probe count is too small, all probes might finish before the problem is resolved. As a result, non-attack packets will be dropped. This setting can avoid such situation.
Procedure
1. Enter system view.
system-view
2. Enable ARP blackhole routing.
arp resolving-route enable
By default, ARP blackhole routing is enabled.
3. (Optional.) Set the number of ARP blackhole route probes for each unresolved IP address.
arp resolving-route probe-count count
The default setting is three probes.
4. (Optional.) Set the interval at which the device probes ARP blackhole routes.
arp resolving-route probe-interval interval
The default setting is 1 second.
Verifying and maintaining unresolvable IP attack protection
To display ARP source suppression configuration information, execute the following command in any view:
display arp source-suppression
Configuring ARP packet rate limit
About this task
The ARP packet rate limit feature allows you to limit the rate of ARP packets delivered to the CPU. An ARP attack detection-enabled device will send all received ARP packets to the CPU for inspection. Processing excessive ARP packets will make the device malfunction or even crash. To solve this problem, configure ARP packet rate limit. When the receiving rate of ARP packets on the interface exceeds the rate limit, those packets are discarded.
You can enable sending notifications to the SNMP module or enable logging for ARP packet rate limit.
· If notification sending is enabled, the device sends the highest threshold-crossed ARP packet rate within the sending interval in a notification to the SNMP module. You must use the snmp-agent target-host command to set the notification type and target host. For more information about notifications, see SNMP configuration in Network Management and Monitoring Configuration Guide.
· If logging for ARP packet rate limit is enabled, the device sends the highest threshold-crossed ARP packet rate within the sending interval in a log message to the information center. You can configure the information center module to set the log output rules. For more information about information center, see System Management Configuration Guide.
Restrictions and guidelines
As a best practice, configure this feature when ARP attack detection, ARP snooping, or ARP fast-reply is enabled, or when ARP flood attacks are detected.
If excessive notifications and log messages are sent for ARP packet rate limit, you can increase notification and log message sending interval.
If you enable notification sending and logging for ARP packet rate limit on an aggregate interface, the features apply to all aggregation member ports.
Procedure
1. Enter system view.
system-view
2. (Optional.) Enable SNMP notifications for ARP packet rate limit.
snmp-agent trap enable arp [ rate-limit ]
By default, SNMP notifications for ARP packet rate limit are disabled.
3. (Optional.) Enable logging for ARP packet rate limit.
arp rate-limit log enable
By default, logging for ARP packet rate limit is disabled.
4. (Optional.) Set the notification and log message sending interval.
arp rate-limit log interval interval
By default, the device sends notifications and log messages every 60 seconds.
5. Enter interface view.
interface interface-type interface-number
Supported interface types include Layer 2 Ethernet interface and Layer 2 aggregate interface,.
6. Enable ARP packet rate limit.
arp rate-limit [ pps ]
By default, ARP packet rate limit is enabled.
Configuring source MAC-based ARP attack detection
About source MAC-based ARP attack detection
This feature checks the number of ARP packets delivered to the CPU. If the number of packets from the same MAC address within 5 seconds exceeds a threshold, the device generates an ARP attack entry for the MAC address. If the ARP logging feature is enabled, the device handles the attack by using either of the following methods before the ARP attack entry ages out:
· Monitor—Only generates log messages.
· Filter—Generates log messages and filters out subsequent ARP packets from the MAC address.
When an ARP attack entry ages out, ARP packets sourced from the MAC address in the entry can be processed correctly.
To enable the ARP logging feature, use the arp check log enable command. For information about the ARP logging feature, see ARP in Network Connectivity Configuration Guide.
Source MAC-based ARP attack detection checks the number of ARP packets delivered to the CPU on a per-slot basis. If the number of ARP packets received from the same MAC address within 5 seconds on the slot to which a VLAN interface belongs exceeds the threshold, the device determines that an attack has occurred.
Restrictions and guidelines
If you change the attack handling method from monitor to filter, the configuration takes effect immediately.
If you change the attack handling method from filter to monitor, the device works as follows:
· Uses the filter attack handling method to process the ARP packets that match the existing ARP attack entries before the entries age out.
· Uses the monitor attack handling method to process the ARP packets that match the newly-generated ARP attack entries.
You can exclude the MAC addresses of some gateways and servers from this detection. This feature does not inspect ARP packets from those devices even if they are attackers.
Procedure
1. Enter system view.
system-view
2. Enable source MAC-based ARP attack detection and specify the handling method.
arp source-mac { filter | monitor }
By default, this feature is disabled.
3. Set the threshold.
arp source-mac threshold threshold-value
By default, the threshold is 30.
4. Set the aging timer for ARP attack entries.
arp source-mac aging-time time
By default, the lifetime is 300 seconds.
5. (Optional.) Exclude specific MAC addresses from this detection.
arp source-mac exclude-mac mac-address&<1-n>
By default, no MAC address is excluded.
Verifying and maintaining source MAC-based ARP attack detection
Displaying source MAC-based ARP attack detection entries
To display ARP attack entries detected by source MAC-based ARP attack detection, execute the following commands in any view:
display arp source-mac { interface interface-type interface-number [ slot slot-number ] | slot slot-number }
Maintaining statistics for source MAC-based ARP attack packets
To display statistics for packets dropped by source MAC-based ARP attack detection, execute the following commands in any view:
display arp source-mac statistics slot slot-number
To clear statistics of packets dropped by source MAC-based ARP attack detection, execute the following commands in user view:
reset arp source-mac statistics { all | [ slot slot-number ] }
Example: Configuring source MAC-based ARP attack detection
Network configuration
As shown in Figure 1, the hosts access the Internet through a gateway (AC). If malicious users send a large number of ARP requests to the gateway, the gateway might crash and cannot process requests from the clients. To solve this problem, configure source MAC-based ARP attack detection on the gateway.
Procedure
# Enable source MAC-based ARP attack detection, and specify the handling method as filter.
<AC> system-view
[AC] arp source-mac filter
# Set the threshold to 30.
[AC] arp source-mac threshold 30
# Set the lifetime for ARP attack entries to 60 seconds.
[AC] arp source-mac aging-time 60
# Exclude MAC address 0012-3f86-e94c from this detection.
[AC] arp source-mac exclude-mac 0012-3f86-e94c
Configuring ARP packet source MAC consistency check
About ARP packet source MAC consistency check
This feature enables a gateway to filter out ARP packets whose source MAC address in the Ethernet header is different from the sender MAC address in the message body. This feature allows the gateway to learn correct ARP entries.
Procedure
1. Enter system view.
system-view
2. Enable ARP packet source MAC address consistency check.
arp valid-check enable
By default, ARP packet source MAC address consistency check is disabled.
Verifying and maintaining ARP packet source MAC consistency check
display arp valid-check statistics slot slot-number
To clear statistics for packets dropped by ARP packet source MAC consistency check, execute the following command in user view:
reset arp valid-check statistics { all | slot slot-number }
Configuring ARP active acknowledgement
About this task
Use the ARP active acknowledgement feature on gateways to prevent user spoofing.
This feature enables the device to perform active acknowledgement before creating an ARP entry.
· Upon receiving an ARP request that requests the MAC address of the device, the device sends an ARP reply. Then, it sends an ARP request for the sender IP address in the received ARP request to determine whether to create an ARP entry for the sender IP address.
¡ If the device receives an ARP reply within the probe interval, it creates the ARP entry.
¡ If the device does not receive an ARP reply within the probe interval, it does not create the ARP entry.
· Upon receiving an ARP reply, the device examines whether it was the reply to the request that the device has sent.
¡ If it was, the device creates an ARP entry for the sender IP address in the ARP reply.
¡ If it was not, the device sends an ARP request for the sender IP address to determine whether to create an ARP entry for the sender IP address.
- If the device receives an ARP reply within the probe interval, it creates the ARP entry.
- If the device does not receive an ARP reply within the probe interval, it does not create the ARP entry.
To improve validity and reliability of ARP entries, you can enable ARP active acknowledgement in strict mode. In this mode, the device creates ARP entries only for the IP addresses that the device actively initiates the ARP resolution.
Procedure
1. Enter system view.
system-view
2. Enable ARP active acknowledgement.
arp active-ack [ strict ] enable
By default, ARP active acknowledgement is disabled.
For ARP active acknowledgement to take effect in strict mode, make sure ARP blackhole routing is enabled.
Configuring authorized ARP
About authorized ARP
Authorized ARP entries are generated based on the DHCP clients' address leases on the DHCP server or dynamic client entries on the DHCP relay agent. For more information about DHCP server and DHCP relay agent, see Network Connectivity Configuration Guide.
Use this feature to prevent user spoofing and to allow only authorized clients to access network resources.
Procedure
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
Only VLAN interfaces are supported.
3. Enable authorized ARP on the interface.
arp authorized enable
By default, authorized ARP is disabled.
Example: Configuring authorized ARP on a DHCP server
Network configuration
As shown in Figure 2, the client obtains an IPv4 address through DHCP. Configure authorized ARP on VLAN-interface 10 of the AC (a DHCP server) to ensure user validity.
Procedure
# Configure DHCP.
<AC> system-view
[AC] dhcp enable
[AC] dhcp server ip-pool 1
[AC-dhcp-pool-1] network 10.1.1.0 mask 255.255.255.0
[AC-dhcp-pool-1] quit
# Specify the IP address for VLAN-interface 10.
[AC] vlan 10
[AC-vlan10] quit
[AC] interface vlan-interface 10
[AC-Vlan-interface10] ip address 10.1.1.1 24
# Enable authorized ARP on VLAN-interface 10.
[AC-Vlan-interface10] arp authorized enable
[AC-Vlan-interface10] quit
Verifying the configuration
# Display authorized ARP entry information on the AC.
[AC] display arp
Type: S-Static D-Dynamic O-Openflow R-Rule I-Invalid
IP address MAC address VLAN/VSI name Interface/Link ID Aging Type
10.1.1.2 0012-3f86-e94c -- GE1/0/1 20 D
The output shows that IP address 10.1.1.2 has been assigned to the client.
The client must use the IP address and MAC address in the authorized ARP entry to communicate with AC. Otherwise, the communication fails. Thus user validity is ensured.
Example: Configuring authorized ARP on a DHCP relay agent
Network configuration
As shown in Figure 3, the switch acts as the DHCP server and assigns IP addresses on subnet 10.10.1.0/24 to the DHCP client. The AC acts as the DHCP relay agent. Configure authorized ARP on VLAN-interface 20 of the AC to ensure user validity.
Procedure
1. Configure the switch:
# Specify the IP address for VLAN-interface 10.
<Switch> system-view
[Switch] interface vlan-interface 10
[Switch-Vlan-interface10] ip address 10.1.1.1 24
[Switch-Vlan-interface10] quit
# Configure DHCP.
[Switch] dhcp enable
[Switch] dhcp server ip-pool 1
[Switch-dhcp-pool-1] network 10.10.1.0 mask 255.255.255.0
[Switch-dhcp-pool-1] gateway-list 10.10.1.1
[Switch-dhcp-pool-1] quit
[Switch] ip route-static 10.10.1.0 24 10.1.1.2
2. Configure the AC:
# Enable DHCP.
<AC> system-view
[AC] dhcp enable
# Specify the IP addresses of VLAN-interface 10 and VLAN-interface 20.
[AC] interface vlan-interface 10
[AC-Vlan-interface10] ip address 10.1.1.2 24
[AC-Vlan-interface10] quit
[AC] interface vlan-interface 20
[AC-Vlan-interface20] ip address 10.10.1.1 24
# Enable DHCP relay agent on VLAN-interface 20.
[AC-Vlan-interface20] dhcp select relay
# Specify DHCP server address 10.1.1.1 on the DHCP relay agent.
[AC-Vlan-interface20] dhcp relay server-address 10.1.1.1
# Enable authorized ARP.
[AC-Vlan-interface20] arp authorized enable
[AC-Vlan-interface20] quit
# Enable the recording of relay entries on the relay agent.
[AC] dhcp relay client-information record
Verifying the configuration
# Display authorized ARP information on the AC.
[AC] display arp
Type: S-Static D-Dynamic O-Openflow R-Rule I-Invalid
IP address MAC address VLAN/VSI name Interface/Link ID Aging Type
10.10.1.2 0012-3f86-e94c -- GE1/0/2 20 D
The output shows that the AC assigned the IP address 10.10.1.2 to the client.
The client must use the IP address and MAC address in the authorized ARP entry to communicate with the AC. Otherwise, the communication fails. Thus the user validity is ensured.
Configuring ARP attack detection
About ARP attack detection
ARP attack detection enables access devices to block ARP packets from unauthorized clients to prevent user spoofing and gateway spoofing attacks.
ARP attack detection provides the following features:
· User validity check.
· ARP packet validity check.
· ARP restricted forwarding.
· ARP packet ingress port ignoring during user validity check
· ARP attack detection logging.
If both ARP packet validity check and user validity check are enabled, the former one applies first, and then the latter applies.
Do not configure ARP attack detection together with ARP snooping. Otherwise, ARP snooping entries cannot be generated.
Restrictions and guidelines: ARP attack detection
A Layer 2 Ethernet interface is enabled with ARP attack detection after you enable ARP attack detection in the VLAN to which the interface belongs.
A Layer 2 Ethernet interface is disabled with ARP attack detection only after you disable ARP attack detection in the VLAN to which the interface belongs.
Configuring user validity check
About this task
User validity check does not check ARP packets received on ARP trusted interfaces. This feature compares the sender IP and sender MAC in the ARP packet received on an ARP untrusted interface with the matching criteria in the following order:
1. User validity check rules.
¡ If a match is found, the device processes the ARP packet according to the rule.
¡ If no match is found or no user validity check rule is configured, proceeds to step 2.
2. DHCP snooping entries.
¡ If a match is found, the device determines that the ARP packet is valid. Then, the device forwards the packet by searching for an entry that contains the target IP address.
- If a match is found and the receiving interface is different from the interface in the entry with a matching sender IP address, the device performs Layer 3 forwarding.
- If a match is found but the receiving interface is the same as the interface in the entry with a matching sender IP address, the device performs Layer 2 forwarding.
- If no match is found, the device performs Layer 2 forwarding.
¡ If no match is found, the device discards the ARP packet.
DHCP snooping entries are automatically generated by DHCP snooping. For more information, see Security Configuration Guide.
Restrictions and guidelines
When you configure user validity check, make sure one or more of the following items are configured:
· User validity check rules.
· DHCP snooping.
If none of the items is configured, all incoming ARP packets on ARP untrusted interfaces are forwarded.
Specify an IP address, a MAC address, and a VLAN where ARP attack detection is enabled for an IP source guard binding. Otherwise, no ARP packets can match the IP source guard binding.
Configuring user validity check rules
1. Enter system view.
system-view
2. Configure a user validity check rule.
arp detection rule rule-id { deny | permit } ip { ip-address [ mask ] | any } mac { mac-address [ mask ] | any } [ vlan vlan-id ]
By default, no user validity check rules are configured.
Enabling ARP attack detection in a VLAN
1. Enter system view.
system-view
2. Enter VLAN view.
vlan vlan-id
3. Enable ARP attack detection.
arp detection enable
By default, ARP attack detection is disabled. The device does not perform user validity check.
4. (Optional.) Configure an interface that does not require ARP user validity check as a trusted interface.
a. Return to system view.
quit
b. Enter interface view.
interface interface-type interface-number
Supported interface types include Layer 2 Ethernet interface and Layer 2 aggregate interface.
c. Configure the interface as a trusted interface excluded from ARP attack detection.
By default, an interface is untrusted.
Configuring ARP packet validity check
About this task
ARP packet validity check does not check ARP packets received on ARP trusted interfaces. To check ARP packets received on untrusted interfaces, you can specify the following objects to be checked:
· src-mac—Checks whether the sender MAC address in the message body is identical to the source MAC address in the Ethernet header. If they are identical, the packet is forwarded. Otherwise, the packet is discarded.
· dst-mac—Checks the target MAC address of ARP replies. If the target MAC address is all-zero, all-one, or inconsistent with the destination MAC address in the Ethernet header, the packet is considered invalid and discarded.
· ip—Checks the sender and target IP addresses of ARP replies, and the sender IP address of ARP requests. All-one or multicast IP addresses are considered invalid and the corresponding packets are discarded.
Prerequisites
Before you configure ARP packet validity check, you must first configure user validity check. For more information about user validity check configuration, see "Configuring user validity check."
Procedure
1. Enter system view.
system-view
2. Enter VLAN view.
vlan vlan-id
3. Enable ARP attack detection.
arp detection enable
By default, ARP attack detection is disabled. The device does not perform ARP packet validity check.
4. Enable ARP packet validity check.
a. Return to system view.
quit
b. Enable ARP packet validity check and specify the objects to be checked.
arp detection validate { dst-mac | ip | src-mac } *
By default, ARP packet validity check is disabled.
5. (Optional.) Configure the interface that does not require ARP packet validity check as a trusted interface.
a. Enter interface view.
interface interface-type interface-number
Supported interface types include Layer 2 Ethernet interface and Layer 2 aggregate interface.
b. Configure the interface as a trusted interface excluded from ARP attack detection.
arp detection trust
By default, an interface is untrusted.
Configuring ARP restricted forwarding
About this task
ARP restricted forwarding does not take effect on ARP packets received on ARP trusted interfaces and forwards the ARP packets correctly. This feature controls the forwarding of ARP packets that are received on untrusted interfaces and have passed user validity check as follows:
· If the packets are ARP requests, they are forwarded through the trusted interface.
· If the packets are ARP replies, they are forwarded according to their destination MAC address. If no match is found in the MAC address table, they are forwarded through the trusted interface.
Restrictions and guidelines
ARP restricted forwarding does not apply to ARP packets that use multiport destination MAC addresses.
Prerequisites
Configure user validity check before you configure ARP restricted forwarding. For information about user validity check configuration, see "Configuring user validity check."
Procedure
1. Enter system view.
system-view
2. Enter VLAN view.
vlan vlan-id
3. Enable ARP restricted forwarding.
arp restricted-forwarding enable
By default, ARP restricted forwarding is disabled.
Ignoring ingress ports of ARP packets during user validity check
About this task
ARP attack detection performs user validity check on ARP packets from ARP untrusted interfaces. The sender IP and sender MAC in the received ARP packet are compared with the entries used for user validity check. In addition, user validity check compares the ingress port of the ARP packet with the port in the entries. If no matching port is found, the ARP packet is discarded. For more information about user validity check, see "Configuring user validity check."
You can configure the device to ignore the ingress ports of ARP packets during user validity check. If an ARP packet passes user validity check, the device directly performs Layer 2 forwarding for the packet. It no longer searches for a matching static IPSG binding, 802.1X security entry, or DHCP snooping entry by the target IP address of the ARP packet.
Procedure
1. Enter system view.
system-view
2. Ignore ingress ports of ARP packets during user validity check.
arp detection port-match-ignore
By default, ingress ports of ARP packets are checked during user invalidity.
Enabling ARP attack detection logging
About this task
The ARP attack detection logging feature enables a device to generate ARP attack detection log messages when illegal ARP packets are detected. An ARP attack detection log message contains the following information:
· Receiving interface of the ARP packets.
· Sender IP address.
· Total number of dropped ARP packets.
Procedure
1. Enter system view.
system-view
2. Enable ARP attack detection logging.
arp detection log enable [ interval interval | number number | threshold threshold-value ]*
By default, ARP attack detection logging is disabled.
Verifying and maintaining ARP attack detection
Displaying VLANs with ARP attack detection enabled
To display the VLANs enabled with ARP attack detection, execute the following command in any view:
display arp detection
Displaying and clearing statistics for packets dropped by ARP attack detection
To display statistics for packets dropped by ARP attack detection, execute the following command in any view:
display arp detection statistics packet-drop [ interface interface-type interface-number ]
To clear statistics for packets dropped by ARP attack detection, execute the following command in user view:
reset arp detection statistics packet-drop [ interface interface-type interface-number ]
Displaying and clearing statistics for ARP attack sources
To display statistics for ARP attack sources, execute the following command in any view:
display arp detection statistics attack-source slot slot-number
To clear statistics for ARP attack sources, execute the following command in user view:
reset arp detection statistics attack-source [ slot slot-number ]
Example: Configuring user validity check
Network configuration
As shown in Figure 4, the switch acts as the DHCP server and the AC supports 802.1X. Enable ARP attack detection in VLAN 10 to perform user validity check based on 802.1X security entries for the clients.
Client 1 and Client 2 are 802.1X local users and supports uploading IP addresses.
Procedure
1. Add all interfaces on the AC to VLAN 10, and specify the IP address of VLAN-interface 10 on the switch. (Details not shown.)
2. Configure the DHCP server on the switch, and configure DHCP address pool 0.
<Switch> system-view
[Switch] dhcp enable
[Switch] dhcp server ip-pool 0
[Switch-dhcp-pool-0] network 10.1.1.0 mask 255.255.255.0
3. Configure Client 1 and Client 2 as 802.1X clients and configure them to upload IP addresses for ARP attack detection. (Details not shown.)
4. Configure the AC:
# Configure the AC to perform EAP termination and use CHAP to communicate with the RADIUS server.
[AC] dot1x authentication-method chap
# Create an ISP domain named local and enter ISP domain view.
# Configure the ISP domain to use local authentication, local authorization, and local accounting for LAN clients.
[AC-isp-local] authentication lan-access local
[AC-isp-local] authorization lan-access local
[AC-isp-local] accounting lan-access local
[AC-isp-local] quit
# Create a service template named wlas_local_chap and enter its view.
[AC] wlan service-template wlas_local_chap
# Set the authentication mode to 802.1X authentication for WLAN clients in the service template.
[AC-wlan-st-wlas_local_chap] client-security authentication-mode dot1x
# Specify ISP domain local for the service template.
[AC-wlan-st-wlas_local_chap] dot1x domain local
# Set the SSID to wlas_local_chap.
[AC-wlan-st-wlas_local_chap] ssid wlas_local_chap
# Enable the service template.
[AC-wlan-st-wlas_local_chap] service-template enable
[AC-wlan-st-wlas_local_chap] quit
# Create AP ap1, and specify the AP model and serial ID.
[AC-wlan-ap-ap 1] serial-id 219801A28N819CE0002T
[AC-wlan-ap-ap 1] quit
# Configure channel 149 as the working channel for radio 1 of the AP, and enable radio 1.
[AC-wlan-ap-ap1] radio 1
[AC-wlan-ap-ap1-radio-1] channel 149
[AC-wlan-ap-ap1-radio-1] radio enable
# Bind service template wlas_local_chap to radio 1.
[AC-wlan-ap-ap1-radio-1] service-template wlas_local_chap
[AC-wlan-ap-ap1-radio-1] quit
[AC-wlan-ap-ap1] quit
# Add a network access user named test.
[AC] local-user test class network
[AC-luser-network-test] service-type lan-access
[AC-luser-network-test] password simple test
[AC-luser-network-test] quit
# Enable ARP attack detection for VLAN 10 to check user validity based on 802.1X entries.
[AC] vlan 10
[AC-vlan10] arp detection enable
# Configure the upstream interface as an ARP trusted interface. By default, an interface is an untrusted interface.
[AC-vlan10] interface gigabitethernet 1/0/3
[AC-GigabitEthernet1/0/3] arp detection trust
[AC-GigabitEthernet1/0/3] quit
Verifying the configuration
# Verify that ARP packets received on interfaces GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are checked against 802.1X entries.
Configuring ARP scanning and fixed ARP
About this task
ARP scanning is typically used together with the fixed ARP feature in small-scale and stable networks.
ARP scanning automatically creates ARP entries for devices in an address range. The device performs ARP scanning in the following steps:
1. Sends ARP requests for each IP address in the address range.
2. Obtains their MAC addresses through received ARP replies.
3. Creates dynamic ARP entries.
Enabled with automatic ARP scanning, the device periodically sends ARP requests to all IP addresses in the specified scanning range at the rate set by using the arp scan auto send-rate command.
You can limit the ARP packet sending rate if the scanning range has a large number of IP addresses. to avoid high CPU usage and heavy network load caused by a burst of ARP traffic.
If you specify the scanning range and source address for the sending ARP requests, the interface scans all IP addresses in the scanning range. If you only specify the scanning range, the interface scans the IP addresses that belong to both the scanning range and the subnet addresses of the interface.
Fixed ARP converts existing dynamic ARP entries (including those generated through ARP scanning) to static ARP entries. These static ARP entries are of the same attributes as the ARP entries that are manually configured. This feature prevents ARP entries from being modified by attackers.
Restrictions and guidelines
IP addresses in existing ARP entries are not scanned.
If you trigger ARP scanning and enable automatic ARP scanning, both of them take effect. As a best practice, use automatic ARP scanning only on networks where users come online and go offline frequently.
Due to the limit on the total number of static ARP entries, some dynamic ARP entries might fail the conversion.
The arp fixup command is a one-time operation. You can use this command again to convert the dynamic ARP entries learned later to static.
To delete a static ARP entry converted from a dynamic one, use the undo arp ip-address command. You can also use the reset arp all command to delete all ARP entries or the reset arp static command to delete all static ARP entries.
You can use the arp scan auto enable [ start-ip-address to end-ip-address [ source-addr source-ip-address ] ] command to specify a maximum of 16 scanning ranges for different subnets. The subnet addresses for each scanning range cannot overlap with each other.
Triggering an ARP scanning
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
3. Trigger an ARP scanning.
arp scan [ start-ip-address to end-ip-address ]
CAUTION: ARP scanning will take some time. To stop an ongoing scan, press Ctrl + C. Dynamic ARP entries are created based on ARP replies received before the scan is terminated. |
Configuring automatic ARP scanning
1. Enter system view.
system-view
2. Set the ARP packet sending rate for automatic ARP scanning.
arp scan auto send-rate { ppm ppm | pps }
By default, the device sends ARP packets at the rate of 48 pps during automatic ARP scanning.
3. Enter interface view.
interface interface-type interface-number
4. Enable automatic ARP scanning.
arp scan auto enable [start-ip-address to end-ip-address [ source-addr source-ip-address ] ]
By default, automatic ARP scanning is disabled.
Configuring fixed ARP
1. Enter system view.
system-view
2. Convert existing dynamic ARP entries to static ARP entries.
arp fixup
Configuring ARP sender IP address checking
About ARP sender IP address checking
This feature allows a gateway to check the sender IP address of an ARP packet in a VLAN before ARP learning. If the sender IP address is within the allowed IP address range, the gateway continues ARP learning. If the sender IP address is out of the range, the gateway determines the ARP packet as an attack packet and discards it.
Restrictions and guidelines
If the VLAN is a sub-VLAN and is associated with a super VLAN, configure this checking feature only in the sub-VLAN.
If Layer 3 communication is configured between the secondary VLANs associated with a primary VLAN, configure this feature in the primary VLAN. If Layer 3 communication is not configured between the secondary VLANs associated with a primary VLAN, configure this feature in the intended VLAN.
Procedure
1. Enter system view.
system-view
2. Enter VLAN view.
vlan vlan-id
3. Enable the ARP sender IP address checking feature and specify the IP address range.
arp sender-ip-range start-ip-address end-ip-address
By default, the ARP sender IP address checking feature is disabled.
Enabling SNMP notifications for ARP
About this task
Enable SNMP notifications for ARP as required.
· If you enable ARP active acknowledgement notifications, the device sends a notification to the SNMP module when it does not establish an ARP entry due to active acknowledgement. The notification includes the sender IP address in the received ARP packet and the interface that receives the ARP packet.
· If you enable rate limit notifications for sending ARP Miss messages or ARP packets, the device sends the highest threshold-crossed rate as a notification to the SNMP module when the sending rate exceeds the custom threshold.
· If you enable notifications for packet dropping due to ARP attack detection, the device sends a notification to the SNMP module when a packet is dropped by ARP attack detection. The notification includes the VLAN ID, service ID, and VSI for the dropped packet and packet drop reason.
· If you enable ARP entry modification notifications, the device sends a notification to the SNMP module when it detects that the ARP entry for a user might be changed to the attacker's ARP entry. The notification includes the sender IP and MAC addresses in the ARP attack packet.
· If you enable ARP entry limit notifications, the device sends the current number of ARP entries as a notification to the SNMP module when the number of global ARP entries exceeds the alarm threshold.
· If you enable ARP gateway protection notifications, the device sends a notification to the SNMP module when it is attacked by gateway spoofing attacks. The notification includes the sender IP and MAC addresses in the ARP attack packet dropped by ARP gateway protection, and index of the interface that receives the ARP attack packet. When an ARP packet with the same sender IP address triggers the SNMP notification again within 3 minutes, the device sends a recovery notification to the SNMP module.
· If you enable endpoint and local device conflict notifications, the device sends a notification to the SNMP module when an endpoint and local device conflict occurs. The notification includes the sender IP address, sender MAC address, target IP address, and target MAC address in the conflicting ARP packet.
· If you enable MAC address inconsistency notifications, the device sends a notification to the SNMP module when the MAC address in the configured static ARP entry and user's actual MAC address are inconsistent. The notification includes the IP address, VPN instance, and MAC address in the ARP entry.
· An invalid ARP packet contains an invalid hardware address type, protocol address type, hardware address length, protocol address length, operation code, or VLAN. For example, when the operation code value is not 1 (ARP request) or 2 (ARP reply), the operation code is invalid and the ARP packet is invalid. If you enable invalid ARP packet check notifications, the device sends a notification to the SNMP module when it receives an invalid ARP packet. The notification includes the name of the interface that receives the ARP packet, sender MAC and IP addresses, user VLAN ID, and VLAN ID of the service provider.
· If you enable rate limit notifications for receiving ARP packets, the device sends the highest threshold-crossed rate as a notification to the SNMP module. For more information about ARP packet rate limit, see "Configuring ARP packet rate limit."
· If you enable user IP address conflict notifications, the device sends a notification to the SNMP module when a user IP address conflict occurs. The notification includes the sender IP and MAC addresses in the conflicting ARP packet, and MAC address in the corresponding local ARP entry. For more information about enabling recording user IP address conflicts, see ARP configuration in Network Connectivity Configuration Guide.
· If you enable user port migration notifications, the device sends a notification to the SNMP module when a user port changes. The notification includes the IP address, MAC address, port before migration, and port after migration of the user. For more information about enabling recording user port migrations, see ARP configuration in Network Connectivity Configuration Guide.
For ARP event notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see Network Management and Monitoring Configuration Guide.
Procedure
1. Enter system view.
system-view
2. Enable SNMP notifications for ARP.
snmp-agent trap enable arp [ active-ack | arp-miss | detection-drop | entry-check | entry-limit | gateway-check | local-conflict | mac-mismatch | packet-check | rate-limit | user-ip-conflict | user-move ] *
By default, SNMP notifications for ARP are disabled.
If you do not specify any keywords, this command enables all SNMP notifications for ARP.