ARP Reply by Yilong Geng
arp_reply
contrib-projects/arp_reply
- NetFPGA-10G Specific cores
- Xilinx AXI Peripheral
- Microblaze Subsystem
- Other
This is a testing project for the arp_reply module. This project added the arp_reply module into the NIC data path. It can reply ARP requests according to the IP-MAC address pairs set in the configuration registers.
In the following sections, we will show how to test the ARP reply module on the NetFPGA.
To run the test, you need two machines, A and B. Let's say Machine A is equipped with NetFPGA and Machine B is equipped with a third-party 10G NIC.
Download the arp_reply bitfile from contrib-projects/arp_reply/bitfiles/arp_reply.bit. (Refer to Production Test Manual if you don't know how to download the bitfile and/or not setup JTAG cable yet.)
Connect Machine A and Machine B using a 10G cable. Assume we use nf0 (the port nearest to the PCI Express) on Machine A and eth1 on Machine B.
Make the driver in the sw/host/driver directory and insert it as a module.
cd sw/host/driver
make
sudo insmod nf10.ko
dmesg
If everything went smoothly dmesg will output that nf10 device is ready.
On Machine A
sudo ifconfig nf0 192.168.1.1
On Machine B
sudo ifconfig eth1 192.168.1.2
The base address of the ARP reply module in this project is 0x78a00000.
On Machine A, under folder arp_reply/sw/host/apps
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00000
AXI reg 0x78a00000=0x6401a8c0
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00001
AXI reg 0x78a00001=0x33445566
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00002
AXI reg 0x78a00002=0x1122
The above says the default first IP-MAC address pair is 192.168.1.100 --- 66:55:44:33:22:11.
Still on machine A, under folder arp_reply/sw/host/apps
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00010
AXI reg 0x78a00010=0x6501a8c0
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00011
AXI reg 0x78a00011=0x44556677
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00012
AXI reg 0x78a00012=0x2233
The above says the default second IP-MAC address pair is 192.168.1.101 --- 77:66:55:44:33:22.
On machine A, under folder arp_reply/sw/host/apps
[gengyl08@machine_A apps]$ sudo ./wraxi 0x78a00010 0x0a01a8c0
[gengyl08@machine_A apps]$ sudo ./wraxi 0x78a00011 0x12345678
[gengyl08@machine_A apps]$ sudo ./wraxi 0x78a00012 0x3210
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00010
AXI reg 0x78a00010=0xa01a8c0
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00011
AXI reg 0x78a00011=0x12345678
[gengyl08@machine_A apps]$ sudo ./rdaxi 0x78a00012
AXI reg 0x78a00012=0x3210
The above sets the second IP-MAC address pair to 192.168.1.10 --- 87:65:43:21:10:32 and tests it.
First ping machine A from machine B to validate the link connectivity.
[gengyl08@machine_B ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.252 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.127 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.123 ms
Second ping on machine B some IP addresses in or out of the configuration registers in the ARP_Reply module to test its function. In theory, we would get no ICMP replies on machine B. But if the target IP address is in the configuration register, we would capture ARP replies on machine B.
On machine B:
[gengyl08@machine_B ~]$ ping 192.168.1.50
PING 192.168.1.50 (192.168.1.50) 56(84) bytes of data.
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
From 192.168.1.2 icmp_seq=2 Destination Host Unreachable
From 192.168.1.2 icmp_seq=3 Destination Host Unreachable
From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
[gengyl08@machine_B ~]$ ping 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
--- 192.168.1.10 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms
