Why is 2.1.102 sending spurious arp request?
sugar> ping -i20 donald
donald> tcpdump
tcpdump: listening on eth0
20:27:00.175626 arp who-has donald tell sugar
20:27:00.175626 arp reply donald is-at 0:0:21:50:21:6c
20:27:00.175626 sugar > donald: icmp: echo request
20:27:00.175626 donald.sam.de > sugar: icmp: echo reply
20:27:20.155626 sugar > donald: icmp: echo request
20:27:20.155626 donald > sugar: icmp: echo reply
20:27:25.155626 arp who-has donald tell sugar
20:27:25.155626 arp reply donald is-at 0:0:21:50:21:6c
20:27:40.155626 sugar > donald: icmp: echo request
20:27:40.155626 donald > sugar: icmp: echo reply
20:28:00.145626 sugar > donald: icmp: echo request
20:28:00.145626 donald > sugar: icmp: echo reply
20:28:20.135626 sugar > donald: icmp: echo request
20:28:20.135626 donald > sugar: icmp: echo reply
20:28:25.135626 arp who-has donald tell sugar
20:28:25.135626 arp reply donald is-at 0:0:21:50:21:6c
20:28:40.135626 sugar > donald: icmp: echo request
20:28:40.135626 donald > sugar: icmp: echo reply
and so on. Every minute at :25 an arp request is send.
The timeout timer should be reset when a packet was
send/received from the appropriate card, shouldn't it?
Ciao, ET.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu