View Single Post
Old 2nd January 2010
mayuka mayuka is offline
Fdisk Soldier
 
Join Date: Dec 2009
Posts: 64
Default

And here's the tcpdump from the client:

Code:
14:40:12.215883 xx:xx:xx:xx:xx:xx > yy:yy:yy:yy:yy:yy, ethertype EAPOL (0x888e), length 135: EAPOL key (3) v1, len 117
14:40:12.215900 yy:yy:yy:yy:yy:yy > xx:xx:xx:xx:xx:xx, ethertype EAPOL (0x888e), length 113: EAPOL key (3) v1, len 95
14:40:12.219956 xx:xx:xx:xx:xx:xx > yy:yy:yy:yy:yy:yy, ethertype EAPOL (0x888e), length 113: EAPOL key (3) v1, len 95
14:40:12.219977 yy:yy:yy:yy:yy:yy > xx:xx:xx:xx:xx:xx, ethertype EAPOL (0x888e), length 193: EAPOL key (3) v1, len 175
14:40:12.220487 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 0.0.0.0, length 28
14:40:12.620561 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 0.0.0.0, length 28
14:40:13.020662 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 0.0.0.0, length 28
14:40:13.420787 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 192.168.2.101, length 28
14:40:13.821017 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 192.168.2.101, length 28
14:40:13.821408 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.254 tell 192.168.2.101, length 28
14:40:13.825223 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
14:40:13.825279 yy:yy:yy:yy:yy:yy > xx:xx:xx:xx:xx:xx, ethertype ARP (0x0806), length 42: Reply 192.168.2.254 is-at yy:yy:yy:yy:yy:yy, length 28
14:40:14.225363 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
14:40:14.625490 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
14:40:15.025592 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
14:40:15.834600 xx:xx:xx:xx:xx:xx > 01:00:5e:00:00:02, ethertype IPv4 (0x0800), length 46: 192.168.2.101 > 224.0.0.2: igmp leave 224.0.0.251
14:40:15.834659 xx:xx:xx:xx:xx:xx > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 46: 192.168.2.101 > 224.0.0.251: igmp v2 report 224.0.0.251
14:40:16.072058 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 92: 192.168.2.101.51625 > 192.168.2.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:40:16.342945 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 92: 192.168.2.101.51625 > 192.168.2.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:40:16.613281 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 92: 192.168.2.101.51625 > 192.168.2.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:40:19.347260 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 92: 192.168.2.101.54508 > 192.168.2.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:40:19.617561 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 92: 192.168.2.101.54508 > 192.168.2.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
14:40:19.887840 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 92: 192.168.2.101.54508 > 192.168.2.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST

break

14:40:21.081885 xx:xx:xx:xx:xx:xx > yy:yy:yy:yy:yy:yy, ethertype EAPOL (0x888e), length 135: EAPOL key (3) v1, len 117
14:40:21.081902 yy:yy:yy:yy:yy:yy > xx:xx:xx:xx:xx:xx, ethertype EAPOL (0x888e), length 113: EAPOL key (3) v1, len 95
14:40:21.085829 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 0.0.0.0, length 28
14:40:21.086021 xx:xx:xx:xx:xx:xx > yy:yy:yy:yy:yy:yy, ethertype EAPOL (0x888e), length 113: EAPOL key (3) v1, len 95
14:40:21.086042 yy:yy:yy:yy:yy:yy > xx:xx:xx:xx:xx:xx, ethertype EAPOL (0x888e), length 193: EAPOL key (3) v1, len 175
14:40:21.485940 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 0.0.0.0, length 28
14:40:21.886049 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 0.0.0.0, length 28
14:40:22.286175 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 192.168.2.101, length 28
14:40:22.530218 xx:xx:xx:xx:xx:xx > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 46: 192.168.2.101 > 224.0.0.251: igmp v2 report 224.0.0.251
14:40:22.686436 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.101 tell 192.168.2.101, length 28
14:40:22.686817 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.2.254 tell 192.168.2.101, length 28
14:40:22.689952 yy:yy:yy:yy:yy:yy > xx:xx:xx:xx:xx:xx, ethertype ARP (0x0806), length 42: Reply 192.168.2.254 is-at yy:yy:yy:yy:yy:yy, length 28
14:40:23.086030 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
14:40:23.486122 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
14:40:23.886227 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
14:40:24.286350 xx:xx:xx:xx:xx:xx > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.255.255 tell 192.168.2.101, length 28
Nothing very special here too.
Reply With Quote