osx - Mac OS X traceroute not even reaching router gateway

05
2014-04
  • angelamia

    I'm having an issue on a Macbook Pro running Mac OS X 10.5, I'm unable to visit certain websites such as: "themarchesa.com"

    On other computers in the same LAN network connected over wifi I'm able to see those sites fine and run a traceroute succesfully.

    When I run a traceroute from the terminal it doesn't even appear to go out to the wireless router gateway:

    angela-dions-macbook-pro:~ Angie$ traceroute themarchesa.com
traceroute to themarchesa.com (64.202.189.170), 64 hops max, 40 byte packets
traceroute: sendto: No route to host
 1 traceroute: wrote themarchesa.com 40 chars, ret=-1
 *traceroute: sendto: No route to host
traceroute: wrote themarchesa.com 40 chars, ret=-1

    When I run the same command on google.com it looks different:

    angela-dions-macbook-pro:~ Angie$ traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.227.18
traceroute to google.com (74.125.227.18), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  3.768 ms  6.499 ms  6.716 ms
 2  * * *
 3  gig3-11.austtxk-rtr2.austin.rr.com (66.68.1.253)  15.161 ms  24.131 ms  16.291 ms
 4  Gi0-2-1-1.austtxrdcsc-rtr2.austin.rr.com (24.27.12.174)  18.678 ms  26.495 ms  16.064 ms
 5  gig6-3-0.dllatxl3-rtr1.texas.rr.com (72.179.205.76)  15.589 ms  18.537 ms  18.427 ms
 6  ae-4-0.cr0.dfw10.tbone.rr.com (66.109.6.88)  16.404 ms  24.141 ms  27.108 ms
 7  ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179)  25.488 ms  19.721 ms  20.257 ms
 8  74.125.48.65 (74.125.48.65)  20.165 ms  22.483 ms  21.444 ms
 9  72.14.233.65 (72.14.233.65)  20.186 ms  25.394 ms  20.003 ms
10  216.239.47.54 (216.239.47.54)  24.236 ms  37.011 ms  38.239 ms
11  74.125.227.18 (74.125.227.18)  27.468 ms  27.292 ms  20.032 ms

    EDIT: Here's the output of route get on the IP address:

    angela-dions-macbook-pro:~ Angie$ route get 64.202.189.170
   route to: pwfwd-v01.prod.mesa1.secureserver.net
destination: default
       mask: default
    gateway: 192.168.1.1
  interface: en1
      flags: <UP,GATEWAY,DONE,STATIC,PRCLONING>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0

    Also here's my routing table information if that helps out (what else could cause this to happen). I'm able to run traceroute and visit the website on other machines on the same LAN (connected to the same router over wifi).

    angela-dions-macbook-pro:~ Angie$ netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            192.168.1.1        UGSc       30        0    en1
127                127.0.0.1          UCS         0        0    lo0
127.0.0.1          127.0.0.1          UH          1    19326    lo0
169.254            link#5             UCS         0        0    en1
192.168.1          link#5             UCS         4        0    en1
192.168.1.1        0:18:f8:b7:45:7c   UHLW       26      112    en1    955
192.168.1.107      7c:6d:62:d2:43:99  UHLW        0        0    en1   1198
192.168.1.111      127.0.0.1          UHS         0        0    lo0
192.168.1.255      link#5             UHLWb       3       18    en1

Internet6:
Destination                             Gateway                         Flags      Netif Expire
::1                                     link#1                          UHL         lo0
fe80::%lo0/64                           fe80::1%lo0                     Uc          lo0
fe80::1%lo0                             link#1                          UHL         lo0
fe80::%en1/64                           link#5                          UC          en1
fe80::21f:5bff:fec7:aed7%en1            0:1f:5b:c7:ae:d7                UHLW        en1
fe80::223:6cff:fe88:f0bd%en1            0:23:6c:88:f0:bd                UHL         lo0
ff01::/32                               ::1                             U           lo0
ff02::/32                               fe80::1%lo0                     UC          lo0
ff02::/32                               link#5                          UC          en1

    I'm not sure what else I can do to debug this issue, what should I use to help debug and fix this issue?

    There were some people that ran into a similiar issue and used some cache cleaning tools (but it seemed like the problem kept popping up, feels almost like a virus?):

    • Answers
  • angelamia

    The issue turned out to be Peer Guardian, I had to disable the filters and then I was able to hit those websites.

  • Ingmar Hupp

    Transmission has built-in block list support, which means you don't need to use Peer Guardian, avoiding such issues.


    • Related Question

    osx - Why can't I route to some sites from my MacBook Pro that I can see from my iPad?
  • Robert Atkins

    Possible Duplicate:
    Mac OS X traceroute not even reaching router gateway

    I am on M1 Cable (residential) broadband in Singapore.

    I have an intermittent problem routing to some sites from my MacBook Pro—often Google-related sites (arduino.googlecode.com and ajax.googleapis.com right now, but sometimes even gmail.com.) This prevents StackExchange chat from working, for instance. Funny thing is, my iPad can route to those sites and they're on the same wireless network! I can ping the sites, but not traceroute to them which I find odd.

    That I can get through via the iPad implies the problem is with the MBP. In any case, calling M1 support is... not helpful.

    I get the same behaviour when I bypass the Airport Express entirely and plug the MBP directly into the cable modem. Can anybody explain a) how this is even possible and b) how to fix it?

    mella:~ ratkins$ ping ajax.googleapis.com
PING googleapis.l.google.com (209.85.132.95): 56 data bytes
64 bytes from 209.85.132.95: icmp_seq=0 ttl=50 time=11.488 ms
64 bytes from 209.85.132.95: icmp_seq=1 ttl=53 time=13.012 ms
64 bytes from 209.85.132.95: icmp_seq=2 ttl=53 time=13.048 ms
^C
--- googleapis.l.google.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.488/12.516/13.048/0.727 ms
mella:~ ratkins$ traceroute ajax.googleapis.com
traceroute to googleapis.l.google.com (209.85.132.95), 64 hops max, 52 byte packets
traceroute: sendto: No route to host
 1 traceroute: wrote googleapis.l.google.com 52 chars, ret=-1
 *traceroute: sendto: No route to host
traceroute: wrote googleapis.l.google.com 52 chars, ret=-1
^C
mella:~ ratkins$

    The traceroute from the iPad goes (and I'm copying this by hand):

    10.0.1.1
119.56.34.1
172.20.8.222
172.31.253.11
202.65.245.1
202.65.245.142
209.85.243.156
72.14.233.145
209.85.132.82

    From the MBP, I can't traceroute to any of the IPs from 172.20.8.222 onwards.


    • Related Answers
  • RedGrittyBrick

    Firstly, the traceroute: sendto: No route to host message is your primary clue. Your MacBook Pro's network configuration isn't fully functional. Perhaps the MacBook is configured with some static settings that overide the settings that are obtainable by DHCP from your cable broadband modem or router?

    Secondly MacBooks and iPads run different operating systems. It is possible that this has some bearing on the problem. Either in the way these devices pick up wireless settings or in the way tracert/traceroute work (normally they use ICMP protocol but some variants use TCP - it is possible that ICMP is blocked at some router/firewall)

    On the Macbook Pro, can you get it to display it's network settings - chiefly default gateway and DNS servers? E.g. ifconfig -a

    If you can see the equivalent informatio on the iPad - look for differences.

  • Robert Atkins

    Turns out this was the answer (tl;dr, nuke Peerguardian from orbit.)