Traceroute issue in Mac OS X Leopard 10.5.5

Discussion in 'macOS' started by mohogany, Oct 19, 2008.

  1. mohogany macrumors newbie

    Joined:
    Sep 26, 2008
    #1
    Internet was running slow so I decided to run a traceroute from the network utilities. I made sure all applications were closed. To my surprise, I get *** on the first position which suggest that there might be something blocking in the operating system. Is this a common issue for Leopard users?

    Thanks in advance.
     
  2. jim.arrows macrumors regular

    Joined:
    Dec 11, 2006
    #2
    The "first position" as you put it is usually your home router (assuming you're using one) or your ISPs gateway for your local network if you're directly connected to your cable modem. Either way, it's definitely not your own operating system, it's the first network hop you cross on your way out to the internet.
     
  3. mohogany thread starter macrumors newbie

    Joined:
    Sep 26, 2008
    #3
    Thanks for the reply Jim.

    I'm directly connected to a cable modem. Does this mean that there's a timeout from my operating system to the modem or a problem from the modem to the local network? I was under the impression it was the first case.

    Thanks.
     
  4. jim.arrows macrumors regular

    Joined:
    Dec 11, 2006
    #4
    It doesn't necessarily indicate that there's any problem, your ISP may just not send a response when the TTL expires. Traceroute essentially works by incrementing the TTL ("Time To Live") value by 1 on each packet it sends out to the network, then it waits for a network device to respond saying that the TTL has expired and records the address of the network device that responded and the time it took to respond; that's the output you see when you run the command. A network device can be configured so that it doesn't send the TTL expired notification, and after a certain amount of time the traceroute program just gives up on that packet and records the "*" value, which simply means it didn't get a response to that packet. So, that could be because there's a problem between you and that particular hop, or it could simply mean that they're not responding. My ISP is Comcast and they don't respond from the first hop into their network, but they do respond for all subsequent hops within the network; I'm not sure why, it's just how they do it. When you traceroute out, do you get replies from hops beyond the first one, or do they all time out? Again, the traceroute results can be useful if you understand the implication of the results, but they don't necessarily mean there's a problem.

    Edit: Sorry, all that and I neglected to answer your most direct question -- your cable modem isn't a hop, so if the lack of a response was indicating a problem it would be between you and your ISPs first network device.
     

Share This Page