PDA

View Full Version : traceroute just doesn't work


evad
2nd August 2005, 02:30 AM
i have this strange problem - my traceroute just doesn't work, while i.e. ping works perfect. here's example:

[evad@evad ~]$ traceroute onet.pl
traceroute to onet.pl (213.180.130.200), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *
[and so on...]

[evad@evad ~]$ ping onet.pl
PING onet.pl (213.180.130.200) 56(84) bytes of data.
64 bytes from f1virt.onet.pl (213.180.130.200): icmp_seq=0 ttl=48 time=76.2 ms
64 bytes from f1virt.onet.pl (213.180.130.200): icmp_seq=1 ttl=48 time=75.9 ms
64 bytes from f1virt.onet.pl (213.180.130.200): icmp_seq=2 ttl=48 time=85.4 ms
64 bytes from f1virt.onet.pl (213.180.130.200): icmp_seq=3 ttl=48 time=75.1 ms
64 bytes from f1virt.onet.pl (213.180.130.200): icmp_seq=4 ttl=48 time=101 ms
64 bytes from f1virt.onet.pl (213.180.130.200): icmp_seq=5 ttl=48 time=74.5 ms

--- onet.pl ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 74.538/81.395/101.103/9.547 ms, pipe 2

it doesn't matter which host i'm trying to traceroute - effect is the same. initially i thought it's a problem with firewall on my adsl modem/router which i use to split my home broadband connection, but it works ok on other machines in network (with winxp & win mobile, however). so looks like local firewall/network problem, but i don't have a clue where to start (i've tried to tweak options in firestarter but i'm not sure about it). thanks for any suggestions.

jim
2nd August 2005, 02:59 AM
are you using the su - with a dash ???


[root@fedorajim_mobile ~]# traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 64.233.161.147traceroute to www.l.google.com (64.233.161.147), 30 hops max, 38 byte packets
1 10.108.96.1 (10.108.96.1) 9.440 ms 9.655 ms 9.453 ms
2 fas0-1.rochnymth-rtr04.nyroc.rr.com (24.93.2.5) 8.331 ms 9.775 ms 9.411 ms
3 srp3-0.rochnymth-rtr02.nyroc.rr.com (24.93.3.178) 10.170 ms 10.707 ms 11.154 ms
4 son0-0-3.albynywav-rtr03.nyroc.rr.com (24.92.224.178) 16.325 ms 16.925 ms 15.599 ms
5 pop1-alb-P6-0.atdn.net (66.185.133.225) 18.091 ms 17.773 ms 19.338 ms
6 bb2-alb-P1-0.atdn.net (66.185.133.238) 21.659 ms 18.599 ms 19.142 ms
MPLS Label=150 CoS=0 TTL=1 S=1
7 bb1-new-P5-0.atdn.net (66.185.152.194) 27.463 ms 26.472 ms 26.022 ms
MPLS Label=155 CoS=0 TTL=1 S=1
8 bb1-ash-P13-0.atdn.net (66.185.152.48) 33.773 ms 30.948 ms 31.946 ms
MPLS Label=37 CoS=0 TTL=1 S=1
9 pop2-ash-P0-0.atdn.net (66.185.139.209) 31.271 ms 31.645 ms 30.635 ms
10 216.239.48.17 (216.239.48.17) 31.256 ms 31.010 ms 30.279 ms
11 216.239.49.248 (216.239.49.248) 30.290 ms 216.239.47.120 (216.239.47.120) 32.614 ms 30.187 ms
12 216.239.49.214 (216.239.49.214) 34.921 ms 35.664 ms 216.239.48.198 (216.239.48.198) 33.684 ms

[root@fedorajim_mobile ~]#


[root@fedorajim_mobile ~]# traceroute onet.pl
traceroute to onet.pl (213.180.130.200), 30 hops max, 38 byte packets
1 10.108.96.1 (10.108.96.1) 30.216 ms 8.444 ms 11.390 ms
2 fas1-4.rochnymth-rtr04.nyroc.rr.com (24.93.0.97) 16.097 ms 10.025 ms 8.32 2 ms
3 srp3-0.rochnymth-rtr02.nyroc.rr.com (24.93.3.178) 15.377 ms 9.749 ms 9.89 9 ms
4 son0-0-3.albynywav-rtr03.nyroc.rr.com (24.92.224.178) 20.310 ms 18.315 ms 16.753 ms
5 pop1-alb-P7-0.atdn.net (66.185.133.229) 18.395 ms 19.333 ms 18.340 ms
6 bb1-alb-P0-0.atdn.net (66.185.148.96) 23.627 ms 17.533 ms 17.860 ms
MPLS Label=340 CoS=0 TTL=1 S=1
7 bb2-nye-P3-0.atdn.net (66.185.152.71) 21.396 ms 22.673 ms 21.019 ms
MPLS Label=350 CoS=0 TTL=1 S=1
8 pop1-nye-P1-0.atdn.net (66.185.151.51) 26.281 ms 21.225 ms 21.451 ms
9 DTAG.atdn.net (66.185.137.206) 21.506 ms 21.152 ms 19.911 ms
10 217.239.37.98 (217.239.37.98) 126.720 ms 127.075 ms 127.214 ms
11 212.184.27.94 (212.184.27.94) 132.788 ms 133.394 ms 133.898 ms
12 * * do-atman-f.onet.pl (193.111.37.58) 145.444 ms !X

[root@fedorajim_mobile ~]#

evad
2nd August 2005, 03:05 AM

are you using the su - with a dash ???

what exactly do you mean by 'su - with a dash'?

btw, traceroute ran as root user doesn't work either.

jim
2nd August 2005, 03:16 AM
http://www.fedorajim.homelinux.com/pages/rookieguide.html#root

So how does one padiwan become root in time of need?

~ to run any system specific application you'll need root password
~ in the terminal you can type
su ( to become root in Root's PATH)
su - ( to become root in Your PATH & /sbin ) notice the space and dash

kg4cbk
2nd August 2005, 03:19 AM
Normally an * from traceroute indicates a time out.

Have you tried mtr?

You will need to be root to run mtr.

From my site traceroute provided information almost to the onet.pl site. I started getting some timeouts around hop 15 or so. mtr seemed to provide better results all the way to onet.pl.

It could be that the intervening routers from your location may not respond to ICMP echo requests, or there is lots of congestion. ICMP packets will be dropped first on routers if there is any congestion.

evad
2nd August 2005, 04:21 PM
kg4cbk: yes, mtr works. however, i'm rather sure that's not problem related to network congestion/packet dropping. when i run traceroute on my FC4 and tracert to the same host on other microsoft os enabled machine, the latter one works fine, while FC4 gives me nothing but '* * *'. btw, i also tried ltr, but it doesn't work either.

fedorajim: yes, i tried to switch user by 'su -' (as i always do to switch to root), but as a root traceroute still doesn't work :(

kg4cbk
2nd August 2005, 06:18 PM
Sounds like you need to file a bug report. mtr should be using the same basic method of getting that info, it just does a real time update of it.

traceroute must be broken in FC4.

evad
2nd August 2005, 07:24 PM
my friend is right now at my home, he also has FC4 and i asked him to test traceroute... effect the same as mine. so it looks like some kind of bug, indeed. however, i don't know where to post the bug, if you can direct me into proper website, i'd be grateful :)

kg4cbk
2nd August 2005, 07:28 PM
Try this:

https://bugzilla.redhat.com/bugzilla/index.cgi

mobsta
24th January 2006, 01:59 AM
If you disable ICMP filtering in your firewall everything should wark expected.
Here is the proof. It's in the Edit>Preferences menu item. Hope it works for you


traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 66.102.7.99
traceroute to www.l.google.com (66.102.7.99), 30 hops max, 38 byte packets
1 10.25.0.1 (10.25.0.1) 15.152 ms 20.120 ms 7.180 ms
2 bla4-ge2.gw.optusnet.com.au (211.28.192.2) 7.632 ms 7.729 ms 8.583 ms
3 * mas2-ge10.gw.optusnet.com.au (211.29.129.201) 11.598 ms 7.398 ms
4 mas3-ge2-1.gw.optusnet.com.au (211.29.129.33) 11.537 ms 7.061 ms 8.486 ms 5 203.208.148.5 (203.208.148.5) 170.948 ms 173.268 ms 182.725 ms
6 203.208.168.217 (203.208.168.217) 179.065 ms laxeq-cr1.ge-3-0-0.ix.singtel.com (203.208.182.45) 226.773 ms 203.208.168.217 (203.208.168.217) 169.607 ms
MPLS Label=159440 CoS=0 TTL=1 S=1
7 so-1-1-0.plapx-cr2.ix.singtel.com (203.208.168.229) 191.021 ms 203.208.168.141 (203.208.168.141) 169.615 ms 183.905 ms
MPLS Label=100896 CoS=0 TTL=1 S=1
8 ge-4-0-0.plapx-ar3.ix.singtel.com (203.208.168.110) 169.745 ms 169.541 ms 203.208.173.66 (203.208.173.66) 173.439 ms
9 203.208.168.250 (203.208.168.250) 167.665 ms 169.233 ms 169.565 ms
10 66.249.94.8 (66.249.94.8) 175.197 ms 170.650 ms 171.706 ms
11 66.249.94.31 (66.249.94.31) 170.689 ms 168.772 ms 169.562 ms
12 216.239.49.150 (216.239.49.150) 180.869 ms 179.777 ms 169.476 ms
13 66.102.7.99 (66.102.7.99) 167.681 ms 169.971 ms 171.100 ms

gavinw6662
24th January 2006, 06:48 AM
I am thinking it is an ICMP problem too.