[ILUG] Traceroute giving request timeout on Fedora Core3
Anil Kamath
kamath.anil at gmail.com
Wed Feb 15 13:25:19 GMT 2006
Hi
I am unable to use traceroute on fedora core3 I am using vmware ws 4 the
tracert works fine on winxp sp2 but on fedora it just goes thru the first
hop and later gives a request timeout. I ran tcpdump, the output is as
follws :
tcpdump: listening on eth0
18:24:11.890986 192.168.1.10.32795 > 203.239.110.20.33446: udp 10
18:24:11.907221 218.248.255.5 > 192.168.1.10: icmp: time exceeded in-transit
18:24:16.892033 192.168.1.10.32795 > 203.239.110.20.33447: udp 10
18:24:16.907141 218.248.255.6 > 192.168.1.10: icmp: time exceeded in-transit
18:24:21.891717 192.168.1.10.32795 > 203.239.110.20.33448: udp 10
18:24:21.907117 218.248.255.6 > 192.168.1.10: icmp: time exceeded in-transit
18:24:26.891605 192.168.1.10.32795 > 203.239.110.20.33449: udp 10
18:24:26.906803 218.248.255.6 > 192.168.1.10: icmp: time exceeded in-transit
18:24:31.891667 192.168.1.10.32795 > 203.239.110.20.33450: udp 10
18:24:31.920362 203.200.145.202 > 192.168.1.10: icmp: time exceeded
in-transit
18:24:35.763224 192.168.1.10 > 202.54.6.50: icmp: echo request (DF)
18:24:35.808256 202.54.6.50 > 192.168.1.10: icmp: echo reply (DF)
18:24:36.781303 192.168.1.10 > 202.54.6.50: icmp: echo request (DF)
18:24:36.825328 202.54.6.50 > 192.168.1.10: icmp: echo reply (DF)
18:24:36.900398 192.168.1.10.32795 > 203.239.110.20.33451: udp 10
18:24:36.928123 203.200.145.202 > 192.168.1.10: icmp: time exceeded
in-transit
18:24:37.800372 192.168.1.10 > 202.54.6.50: icmp: echo request (DF)
18:24:37.844025 202.54.6.50 > 192.168.1.10: icmp: echo reply (DF)
18:24:38.811240 192.168.1.10 > 202.54.6.50: icmp: echo request (DF)
18:24:38.854162 202.54.6.50 > 192.168.1.10: icmp: echo reply (DF)
18:24:39.821784 192.168.1.10 > 202.54.6.50: icmp: echo request (DF)
18:24:39.866082 202.54.6.50 > 192.168.1.10: icmp: echo reply (DF)
18:24:41.900106 192.168.1.10.32795 > 203.239.110.20.33452: udp 10
18:24:41.927096 203.200.145.202 > 192.168.1.10: icmp: time exceeded
in-transit
18:24:46.901324 192.168.1.10.32795 > 203.239.110.20.33453: udp 10
18:24:46.998292 134.159.129.61 > 192.168.1.10: icmp: time exceeded
in-transit
18:24:51.903664 192.168.1.10.32795 > 203.239.110.20.33454: udp 10
18:24:51.982835 134.159.129.61 > 192.168.1.10: icmp: time exceeded
in-transit
18:24:56.115013 192.168.1.10 > 203.197.12.30: icmp: echo request (DF)
18:24:56.155396 203.197.12.30 > 192.168.1.10: icmp: echo reply (DF)
18:24:56.901869 192.168.1.10.32795 > 203.239.110.20.33455: udp 10
18:24:56.998198 134.159.129.61 > 192.168.1.10: icmp: time exceeded
in-transit
18:24:57.130845 192.168.1.10 > 203.197.12.30: icmp: echo request (DF)
18:24:57.172567 203.197.12.30 > 192.168.1.10: icmp: echo reply (DF)
18:24:57.550036 192.168.1.10.32796 > 202.54.6.50.53: 34902+ A?
www.yahoo.com. (31) (DF)
18:24:57.593453 202.54.6.50.53 > 192.168.1.10.32796: 34902 Refused 0/0/0
(31) (DF)
18:24:57.625557 192.168.1.10.32769 > 66.163.169.170.53: 29125 [1au] A?
www.yahoo.com. (42) (DF)
18:24:57.923711 66.163.169.170.53 > 192.168.1.10.32769: 29125*-% 1/13/1
CNAME[|domain]
18:24:57.947844 192.168.1.10.32769 > 220.73.220.4.53: 48516 A?
www.yahoo.akadns.net. (38) (DF)
18:24:58.152784 192.168.1.10 > 203.197.12.30: icmp: echo request (DF)
18:24:58.193230 203.197.12.30 > 192.168.1.10: icmp: echo reply (DF)
18:24:58.212025 220.73.220.4.53 > 192.168.1.10.32769: 48516*- 8/0/0 A
66.94.230.36[|domain] (DF)
18:24:59.162143 192.168.1.10 > 203.197.12.30: icmp: echo request (DF)
18:24:59.204525 203.197.12.30 > 192.168.1.10: icmp: echo reply (DF)
18:25:00.171951 192.168.1.10 > 203.197.12.30: icmp: echo request (DF)
18:25:00.211736 203.197.12.30 > 192.168.1.10: icmp: echo reply (DF)
18:25:01.902006 192.168.1.10.32795 > 203.239.110.20.33456: udp 10
18:25:02.015566 202.84.154.102 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:04.474190 192.168.1.10 > 202.54.6.50: icmp: echo request (DF)
18:25:04.518151 202.54.6.50 > 192.168.1.10: icmp: echo reply (DF)
18:25:06.901662 192.168.1.10.32795 > 203.239.110.20.33457: udp 10
18:25:06.996327 202.84.154.102 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:11.412144 192.168.1.100.1031 > 192.168.1.10.53: 53429+ A?
mail.google.com. (33)
18:25:11.419217 192.168.1.10.32769 > 216.239.36.10.53: 57026 [1au] A?
mail.google.com. (44) (DF)
18:25:11.720329 216.239.36.10.53 > 192.168.1.10.32769: 57026*-% 1/6/7
CNAME[|domain]
18:25:11.725600 192.168.1.10.53 > 192.168.1.100.1031: 53429 3/6/0
CNAME[|domain] (DF)
18:25:11.901530 192.168.1.10.32795 > 203.239.110.20.33458: udp 10
18:25:12.023341 202.84.154.102 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:14.713759 192.168.1.10 > 203.197.12.30: icmp: echo request (DF)
18:25:14.755973 203.197.12.30 > 192.168.1.10: icmp: echo reply (DF)
18:25:14.848027 192.168.1.10 > 202.54.6.50: icmp: echo request (DF)
18:25:14.891744 202.54.6.50 > 192.168.1.10: icmp: echo reply (DF)
18:25:16.901586 192.168.1.10.32795 > 203.239.110.20.33459: udp 10
18:25:16.997176 202.84.154.197 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:19.135349 192.168.1.1 > 224.0.0.1: igmp query v2 [ttl 1]
18:25:21.901321 192.168.1.10.32795 > 203.239.110.20.33460: udp 10
18:25:21.997856 202.84.154.197 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:22.928314 192.168.1.100 > 239.255.255.250: igmp v2 report
239.255.255.250 [ttl 1]
18:25:26.901162 192.168.1.10.32795 > 203.239.110.20.33461: udp 10
18:25:26.997096 202.84.154.197 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:31.901226 192.168.1.10.32795 > 203.239.110.20.33462: udp 10
18:25:32.163068 202.84.143.245 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:35.220170 192.168.1.10.32797 > 203.197.12.30.53: 52645+ A?
www.yahoo.com. (31) (DF)
18:25:35.267088 203.197.12.30.53 > 192.168.1.10.32797: 52645 Refused 0/0/0
(31) (DF)
18:25:36.901936 192.168.1.10.32795 > 203.239.110.20.33463: udp 10
18:25:37.158124 202.84.143.245 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:41.901842 192.168.1.10.32795 > 203.239.110.20.33464: udp 10
18:25:42.158061 202.84.143.245 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:44.282754 192.168.1.10 > 203.197.12.30: icmp: echo request (DF)
18:25:44.323819 203.197.12.30 > 192.168.1.10: icmp: echo reply (DF)
18:25:46.901952 192.168.1.10.32795 > 203.239.110.20.33465: udp 10
18:25:47.169560 208.214.143.177 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:51.911563 192.168.1.10.32795 > 203.239.110.20.33466: udp 10
18:25:52.178050 208.214.143.177 > 192.168.1.10: icmp: time exceeded
in-transit
18:25:56.912469 192.168.1.10.32795 > 203.239.110.20.33467: udp 10
18:25:57.180328 208.214.143.177 > 192.168.1.10: icmp: time exceeded
in-transit
18:26:01.910877 arp who-has 192.168.1.1 tell 192.168.1.10
18:26:01.911637 arp reply 192.168.1.1 is-at 0:f:a3:51:dc:27
18:26:01.921431 192.168.1.10.32795 > 203.239.110.20.33468: udp 10
18:26:02.189185 152.63.51.54 > 192.168.1.10: icmp: time exceeded in-transit
18:26:06.931512 192.168.1.10.32795 > 203.239.110.20.33469: udp 10
18:26:07.199035 152.63.51.54 > 192.168.1.10: icmp: time exceeded in-transit
please let me know if there is any issue with the ports
It works well on Windows XP SP2
--
Thanks & Regards,
Anil M Kamath
mobile:9880037400
More information about the ILUG
mailing list