This example provides an example for configuring static ARP.
ARP is a basic link layer protocol that maps devices' IP addresses to MAC addresses. ARP is simple to use but does not have any security guarantee. Attackers may send forged ARP packets to attack networks, interrupting normal services or even breaking devices down. Therefore, carriers want to enhance backbone network security.
As shown in Figure 1, hosts connect to the backbone network through routers. To protect the devices on the backbone network against ARP attacks and ensure stable data transmission, configure static ARP on routers.
The configuration roadmap is to configure static ARP entries on routers. These entries will not be aged or overwritten by dynamic ARP entries so that user data can be stably transmitted.
To complete the configuration, you need the following data:
IP addresses for which mapping needs to be performed
MAC addresses for which mapping needs to be performed
<HUAWEI> system-view [~HUAWEI] sysname DeviceA [*HUAWEI] commit [~DeviceA] arp static 10.1.1.1 00e0-fc41-0200 [*DeviceA] arp static 10.1.1.2 00e0-fc41-0202 [*DeviceA] arp static 10.1.1.3 00e0-fc41-0204 [*DeviceA] commit
<DeviceA> display arp all IP ADDRESS MAC ADDRESS EXPIRE(M) TYPE INTERFACE VPN-INSTANCE VLAN/CEVLAN PVC ------------------------------------------------------------------------------ 10.1.1.1 00e0-fc41-0200 S-- 10.1.1.2 00e0-fc41-0202 S-- 10.1.1.3 00e0-fc41-0204 S-- ------------------------------------------------------------------------------ Total:3 Dynamic:0 Static:3 Interface:0 Remote:0 Redirect:0
DeviceA configuration file
#
sysname DeviceA
#
arp static 10.1.1.1 00e0-fc41-0200
arp static 10.1.1.2 00e0-fc41-0202
arp static 10.1.1.3 00e0-fc41-0204
#
return
DeviceB configuration file
#
sysname DeviceB
#
arp static 10.1.2.1 00e0-fc41-0300
arp static 10.1.2.2 00e0-fc41-0302
arp static 10.1.2.3 00e0-fc41-0304
#
return