ARP experiment under RedHatLinux9

Lab environment: VMware7.0, RedHatLinux9 Host IP Address: 192.168.0.132 (Linux host), Windows xp Host IP Address: 192.168.0.150 (xp host), and two virtual hosts are mounted on the vmnet2 switch. Packet capture tool: wireshark-win32-1.2.9, installed on an xp host. Objective: 1. to deeply understand the significance and principles of arp caching; 2. To master

Lab environment:

VMware7.0, Red Hat Linux 9 Host IP Address: 192.168.0.132 (hereinafter referred to as Linux host), windows xp Host IP Address: 192.168.0.150 (hereinafter referred to as xp host), and two virtual hosts are mounted on the vmnet2 switch.

Packet capture tool:

Wireshark-win32-1.2.9, installed on the xp host.

Purpose:

1. profound understanding of the significance and principles of arp caching;

2. Master arp commands in Linux.

Lab operation:

1. Clear the arp cache on Linux and xp hosts, ping the xp host on Linux, analyze the packets intercepted by wireshark, and check the arp cache on the Linux host and xp host respectively;

2. Clear the arp cache of the xp host, run the arp-s 192.168.0.150 xp host mac address command on the Linux host, and ping the xp host on the Linux host, analyze the packets intercepted by wireshark, and check the arp cache of the Linux host and the xp host respectively.

First case:

Packet status: the Linux host broadcasts an arp request packet asking the mac address of the xp host. The xp host sends an arp response packet to the Linux host after receiving the request packet and tells the Linux host, what is your mac address. Then there are four ICMP (ping request-response) packets, such:

Arp cache: The arp cache records the relationship between the IP address of the other host and the mac address.

Case 2:

Packet: There is no arp request packet that the Linux host broadcasts first. Only four pairs of ICMP (ping request-response ).

Arp cache: The arp cache records the relationship between the IP address of the other host and the mac address.