tcpdump experiment

[Bill Moss <bmoss clemson edu>]

cvs1117 works for me but DHCP fails for cvs1208. Here are some tcpdump 
experiments for both. Notice the length difference in line 5 and the arp 
differences in line 6.

cvs1117 produces the following output
13:07:20.173645 :: > ff02::16: HBH icmp6: type-#143 [hlim 1]
13:07:20.195869 :: > ff02::1:ff14:60d0: icmp6: neighbor sol: who has 
fe80::20e:35ff:fe14:60d0
13:07:20.196240 fe80::20e:35ff:fe14:60d0 > ff02::2: icmp6: router 
solicitation
13:07:22.948661 fe80::20e:35ff:fe14:60d0 > ff02::2: icmp6: router 
solicitation
13:07:24.950224 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 548
13:07:24.960485 arp who-has 192.168.2.3 tell 192.168.2.1
13:07:25.973574 IP 192.168.2.1.bootps > 192.168.2.3.bootpc: BOOTP/DHCP, 
Reply, length: 548
13:07:25.974640 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 548
13:07:25.990785 IP 192.168.2.1.bootps > 192.168.2.3.bootpc: BOOTP/DHCP, 
Reply, length: 548
13:07:26.948056 fe80::20e:35ff:fe14:60d0 > ff02::2: icmp6: router 
solicitation

cvs1208 produces the following output
13:11:03.552788 :: > ff02::16: HBH icmp6: type-#143 [hlim 1]
13:11:03.553790 :: > ff02::1:ff14:60d0: icmp6: neighbor sol: who has 
fe80::20e:35ff:fe14:60d0
13:11:03.554386 fe80::20e:35ff:fe14:60d0 > ff02::2: icmp6: router 
solicitation
13:11:06.438687 fe80::20e:35ff:fe14:60d0 > ff02::2: icmp6: router 
solicitation
13:11:08.411772 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
13:11:08.412292 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:09.412228 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:10.411992 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:10.438080 fe80::20e:35ff:fe14:60d0 > ff02::2: icmp6: router 
solicitation
13:11:11.412572 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
13:11:13.412620 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:14.412383 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:15.412317 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:16.412748 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
13:11:18.412779 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:19.412708 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:20.412553 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:21.412988 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
13:11:23.413102 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:24.412947 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:25.412795 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:26.413138 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
13:11:28.413341 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:29.413103 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:30.413033 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:31.413385 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
13:11:33.413582 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:34.413428 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:35.413190 arp who-has 192.168.2.1 tell 0.0.0.0
13:11:36.413708 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
13:11:38.417364 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:0e:35:14:60:d0, length: 281
tcpdump: pcap_loop: recvfrom: Network is down

--
Bill Moss
Professor, Mathematical Sciences
Clemson University