traceroute
 

Whenever I try to run traceroute, with any web/ip address it comes up as this:
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *

In the manual it says that this is an error thing, and it should be displaying the site/times that it goes to.
Why will it not work?

who is your ISP? what is your connection to the internet?

what does:

$ traceroute -vn yahoo.com

I have a cable through Roadrunner. When I do
$ traceroute -vn yahoo.com
then it says: $: command not found
When I did:
traceroute -vn yahoo.com
then it did the exact same thing as before.

One thing that I just thought of that might have something to do with it is that I am connected through a network with a linksys box hub dealy.

How 'bout ping -- is it working?
What output do you get from :
ping -c 5 www.yahoo.com

$ is just my shell prompt; [ almost ] all unix commands start with a command name, right?

the linksys is a router?

what do you get if you traceroute the ip of the linksys router?

$ traceroute 192.168.1.1 # that is the ip of my router, yours may be different
traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 0.974 ms 0.613 ms 1.491 ms

you should get one hop to your first gateway. are you running any routing services?

Ping works fine.
Oh ho! I traced my router and got this:
traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * 192.168.1.1 (192.168.1.1) 1.671 ms 1.491 ms

In all of the other times I had gotten to 30 tries with all *, but this time I got it at the second try of 11!
This is interesting: I tried the traceroute again (to the router) about 2 minutes after I had gotten it on the 11th try, and I got it on the first try! I then tried yahoo.com again to see if anything was different but it again got to 30 without any success. What if I try assigning a static ip to myself? Would that work?. The question is, how do I do that with my router there? When I go into network prefs and set to "manual" then type in my ip (keeping the same as the router assigned me) now when I try to traceroute to anything but the router and it says: traceroute:
unknown host yahoo.com
[1] + Terminated traceroute yahoo.com
Oh, and the web browser says it can't find anything either.
(dont worryi just set it back to auto and all is well)

there is a sickness somewhere. your router is probably dishing DHCP ip addresses and you can't change your host ip to static without re-configuring the router to stop DHCP, but don't mess around with those settings just yet.

it would behoove you to not change a lot of settings. in troubleshooting this, it's best to make small changes and test the results.

show us:

$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
en0: flags=8863<UP,BROADCAST,b6,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.50 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:30:65:83:a5:4c
media: autoselect (100baseTX <full-duplex>) status: active
supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 100baseTX <half-duplex> 100baseTX <full-duplex>

$ netstat -r
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 13 330 en0
localhost localhost UH 9 639300 lo0
192.168.1.0 ff:ff:ff:ff:ff:ff UHLWb 0 5 en0 =>
192.168.1 link#2 UC 0 0 en0
192.168.1.1 0:a0:4b:c:45:de UHLW 12 135 en0 108
192.168.1.50 localhost UHS 0 3 lo0

ok... here it is:


[localhost:~] kag% ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
en0: flags=8863<UP,BROADCAST,b6,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:50:e4:ae:a0:42
media: autoselect (100baseTX <full-duplex>) status: active
supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 100baseTX <half-duplex> 100baseTX <full-duplex>




[localhost:~] kag% netstat -r
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 40 0 en0
localhost localhost UH 7 646 lo0
192.168.1 link#2 UC 0 0 en0
192.168.1.1 0:4:5a:ec:3a:8f UHLW 41 1 en0 432
192.168.1.101 localhost UHS 0 0 lo0

hmm, that looks copacetic. what about:
and show us your ping times to yahoo.com

I am not familiiar w/ Road Runner services, but i've seen the same thing, from behind the on campus firewall. We can't even ping off campus so trying to traceroute gives a simliar return. Don't know if that's relevant in any way shape or form, but it's a thought that maybe is relevant... :shrug:

some routers can be set unpingable, that is, not to respond to ping requests. e.g., i don't believe anybody can ping cnn.com. and your campus firewall may contribute to dead traceroute hops?

but goad's setup should be simpler, unless roadrunner is stomping the packets. goad, if that's the case, the issue may be academic.

I'm experiencing this same problem behind my router,.. did anyone figure it out in 2 years?

MY traceroute doesn't work... in fact.. we have a thread starting a new mutliplayer gaming network.. people are ping testing and traceroute testing to the new server... half the people can't use trace route ... mostly because of the routers i believe.

If the routers aren't config'd to pass (tracroute) ICMP traffic back, then traceroute is useless.

And how exactly do i configure it to pass traceroute via UDP/ICMP

I have all ports open on the router and DMZ is on.... I even tried to open port 33434 UDP in multiple spots and nothing worked.

Also I read somewhere that traceroute can use ICMP also to trace.. but that -I switch doesn't work with the traceroute command from the terminal in OSX.

BTW I'm using a Linksys BEFSR41v3 with Firmware Version: 1.04.17.

How exactly would I set it up to work in the settings.

Sorry, let me rephrase..

From the traceroute man page:

Meaning, if a router (gateway) is configured to discard all packets begging for "TIME_EXCEEDED", or discard all "TIME_EXCEEDED" ICMP traffic, you'll never get traceroute to work. You may have to contact your ISP to find out if that is what they are doing. Your Linksys router should be passing the requests out and honoring them if they return, most likely it's the next router (gateway) that you're connecting to that is dropping the info.

It used to work before I ever got a router... So it shouldn't be the ISP (Comcast) that's blocking it. The router must be doing it somehow.

Guess you'll have to talk to Linksys then.

I've not used a linksys router in quite some time, so I don't remember it's particulars, but can't you turn off the packet filter, at least to test?

Anyone know how to do this?

Anyone with a Linksys router able to trace routes?... Does it have anything to do with the computer knowing only it's internal IP instead of external ip... I know a a linux user with a router and his computer knowss the outside ip via hostname.. but that doesn't work on OS X... Anyone know what might cause trace route to not work with the router.