Frustrated that I don't UNDERSTAND why my network times out

Discussion in 'Linux Networking' started by billy, Oct 8, 2013.

  1. billy

    billy Guest

    Below (sorry for the top post) is the old traceroute from yesterday on
    Microknoppix.

    Here is the new traceroute from a few seconds ago.
    The route is entirely different!
    Since *UNDERSTANDING* is what we're after, can you give me
    insight into *how* all of a sudden, the route is so very different
    (and why it works now)?

    Who decides what route my packets will take?

    knoppix@Microknoppix:~$ traceroute www.centos.org
    traceroute to www.centos.org (85.12.30.227), 30 hops max, 60 byte packets
    1 192.168.1.1 (192.168.1.1) 2.940 ms 2.915 ms 5.895 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 23.983 ms 23.970 ms 23.953 ms
    3 10.50.0.1 (10.50.0.1) 23.935 ms 23.920 ms 23.905 ms
    4 10.25.0.1 (10.25.0.1) 33.716 ms 33.701 ms 33.687 ms
    5 10.20.0.1 (10.20.0.1) 113.640 ms 127.266 ms 127.251 ms
    6 10.0.0.1 (10.0.0.1) 155.135 ms 198.034 ms 198.014 ms
    7 69.36.226.193 (69.36.226.193) 77.534 ms 88.951 ms 88.940 ms
    8 vl2.core2.scl.layer42.net (69.36.225.130) 101.711 ms 101.700 ms 107.203 ms
    9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net (140.174.21.101) 111.422 ms 111.419 ms 111.404 ms
    10 te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 111.376 ms te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49)
    111.352 ms te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 111.341 ms
    11 be2047.ccr22.sjc01.atlas.cogentco.com (154.54.5.113) 111.324 ms 111.311 ms be2000.ccr21.sjc01.atlas.cogentco.com
    (154.54.6.105) 111.251 ms
    12 be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 111.238 ms be2166.mpd21.sfo01.atlas.cogentco.com (154.54.28.69) 58.660 ms
    be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 66.012 ms
    13 be2132.ccr21.mci01.atlas.cogentco.com (154.54.30.54) 168.366 ms be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 168.350 ms
    be2133.ccr22.mci01.atlas.cogentco.com (154.54.30.66) 165.709 ms
    14 be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82) 168.316 ms 168.300 ms be2158.mpd21.ord01.atlas.cogentco.com
    (154.54.7.130) 168.285 ms
    15 be2079.ccr21.yyz02.atlas.cogentco.com (154.54.27.182) 139.555 ms 133.671 ms be2138.ccr22.bos01.atlas.cogentco.com
    (154.54.43.202) 155.781 ms
    16 be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 139.505 ms te0-3-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.230)
    208.018 ms te0-4-0-3.ccr22.lpl01.atlas.cogentco.com (154.54.44.190) 208.007 ms
    17 te0-5-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.87.65) 211.696 ms be2182.ccr21.ams03.atlas.cogentco.com (154.54.77.245)
    226.780 ms te0-4-0-6.ccr22.lpl01.atlas.cogentco.com (154.54.44.214) 211.705 ms
    18 be2185.mpd22.ams03.atlas.cogentco.com (154.54.37.105) 229.203 ms te0-0-0-4.mag21.ams03.atlas.cogentco.com (154.54.76.190)
    310.294 ms be2185.mpd22.ams03.atlas.cogentco.com (154.54.37.105) 310.272 ms
    19 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.393 ms te0-0-0-12.mag21.ams03.atlas.cogentco.com (154.54.76.134) 310.218 ms
    10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.367 ms
    20 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.344 ms 305.321 ms 310.147 ms
    21 85.12.30.227 (85.12.30.227) 305.263 ms !X 305.254 ms !X 205.255 ms !X
    knoppix@Microknoppix:~$
     
    billy, Oct 11, 2013
    #81
    1. Advertisements

  2. You're now talking to another IP, i.e. probably another system. Someone
    in this thread noted that the other IP was with Akamai. Probably some
    remains of a torn down accelleration setup? Who knows.

    Best regards
    Thomas
     
    Thomas Keusch, Oct 11, 2013
    #82
    1. Advertisements

  3. billy

    nemesis Guest

    The guy at 67.218.118.85. He probably lives nearby. Kick his a¨%&¨¨.
     
    nemesis, Oct 11, 2013
    #83
  4. billy

    billy Guest

    If I understand you correctly, what you're saying is that
    yesterday, Centos.org was hosted on 72.232.194.162 while,
    today, it's hosted on 85.12.30.227.

    For some reason, I couldn't get to 72.232.194.162 yesterday,
    while my neighbors could get to it; but, today, I only need
    to get to 85.12.30.227, which works fine for me.

    I just tried pinging 72.232.194.162, and it fails to return.

    A traceroute to that same IP address still fails today.

    # traceroute -M icmp 72.232.194.162
    traceroute to 72.232.194.162 (72.232.194.162), 30 hops max, 60 byte packets
    1 192.168.1.1 (192.168.1.1) 2.849 ms 2.839 ms 2.839 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 8.476 ms 8.477 ms 8.474 ms
    3 10.50.0.1 (10.50.0.1) 8.468 ms 15.442 ms 15.442 ms
    4 10.25.0.1 (10.25.0.1) 62.623 ms 62.631 ms 62.629 ms
    5 10.20.0.1 (10.20.0.1) 68.657 ms 68.654 ms 68.652 ms
    6 10.0.0.1 (10.0.0.1) 99.906 ms 36.198 ms 45.997 ms
    7 69.36.226.193 (69.36.226.193) 45.960 ms 22.838 ms 39.756 ms
    8 vl2.core1.scl.layer42.net (69.36.225.129) 39.747 ms 21.573 ms 25.054 ms
    9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 25.035 ms 43.099 ms 43.074 ms
    10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 101.938 ms 74.301 ms 76.448 ms
    11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 76.430 ms 108.260 ms 108.219 ms
    12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 108.186 ms 60.969 ms 65.956 ms
    13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 70.441 ms 124.382 ms 126.699 ms
    14 border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 126.680 ms border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81)
    69.193 ms border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 69.171 ms
    15 layered-11.border1.dal004.pnap.net (63.251.44.74) 69.140 ms 97.227 ms 102.727 ms
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    So, I guess all that changed is that Centos.org moved servers, and, well,
    the original server (of yesterday) was unreachable by me, but most of you
    (and my neighbors) could reach it.

    At least this moving of servers can explain why my ability to reach
    the server comes and goes - but - what I still don't get is why I couldn't
    (and can't) reach the old server and all of you guys could.
     
    billy, Oct 11, 2013
    #84
  5. billy

    unruh Guest

    Each router looks for a next hop to send the packet on to, each has a
    default route to send it on if it does not know where it is. Thus, the
    route is dynamic and determined on the fly-- it was purposely designed
    that way so that if a nuclear war takes out Dallas, the packets go via
    Minneapolis instead, automatically.
     
    unruh, Oct 11, 2013
    #85
  6. billy

    billy Guest

    I do not disagree, since, in theory, that's how the Internet
    was designed (redundancy).

    However, in my experience here, all the traceroutes were
    the same path, time after time after time after time.

    It is only when centos.org changed servers (between yesterday
    and today) that the path taken was drastically different.

    Even so, the *new* path is the same time after time.

    So, it's not as dynamic as one might presume.
    In fact, it's pretty static.

    Of course, if one of the routers were to be taken out,
    then I'm sure it would route around them - but barring
    that, the route sure *appears* to be static to me.

    PS: Do you think the NSA is stealing my packets? :)
     
    billy, Oct 11, 2013
    #86
  7. billy

    billy Guest

    This gives me an idea...

    It seems that, when I try to traceroute to the old
    Centos.org site of yesterday (72.232.194.162), there
    is this last router, from whence my packets never
    go any further:
    layered-11.border1.dal004.pnap.net (63.251.44.74)

    Now, if I ping that router, everything seems fine:
    $ ping 63.251.44.74
    PING 63.251.44.74 (63.251.44.74) 56(84) bytes of data.
    64 bytes from 63.251.44.74: icmp_req=1 ttl=238 time=62.0 ms
    64 bytes from 63.251.44.74: icmp_req=2 ttl=238 time=63.1 ms
    64 bytes from 63.251.44.74: icmp_req=3 ttl=238 time=72.0 ms
    ^C
    --- 63.251.44.74 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2014ms
    rtt min/avg/max/mdev = 62.017/65.710/72.006/4.478 ms

    A traceroute works fine also:
    # traceroute -M icmp 63.251.44.74
    traceroute to 63.251.44.74 (63.251.44.74), 30 hops max, 60 byte packets
    1 192.168.1.1 (192.168.1.1) 2.850 ms 2.835 ms 2.834 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 2.882 ms 2.881 ms 5.680 ms
    3 10.50.0.1 (10.50.0.1) 12.477 ms 14.800 ms 14.797 ms
    4 10.25.0.1 (10.25.0.1) 20.777 ms 23.605 ms 23.601 ms
    5 10.20.0.1 (10.20.0.1) 41.385 ms 144.151 ms 146.952 ms
    6 10.0.0.1 (10.0.0.1) 619.953 ms 306.464 ms 306.448 ms
    7 69.36.226.193 (69.36.226.193) 306.421 ms 364.905 ms 364.883 ms
    8 vl2.core2.scl.layer42.net (69.36.225.130) 364.865 ms 266.085 ms 266.063 ms
    9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 266.044 ms 345.147 ms 346.288 ms
    10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 366.961 ms 634.262 ms 667.273 ms
    11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 667.264 ms 457.518 ms 461.442 ms
    12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 529.257 ms 520.364 ms 520.332 ms
    13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 520.314 ms 444.251 ms 485.246 ms
    14 border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 615.351 ms border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81)
    444.807 ms border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 462.102 ms
    15 layered-11.border1.dal004.pnap.net (63.251.44.74) 73.068 ms 65.315 ms *

    My key confusion is below:
    Q: How can I tell if the problem getting to the old Centos server
    is due to this router? Or to the next router in line?
     
    billy, Oct 11, 2013
    #87
  8. billy

    unruh Guest

    Yes, and then because something changes, suddenly it is different.
    Probably. They are missing so many packets that they need to collect all
    the ones they can.
     
    unruh, Oct 11, 2013
    #88
  9. billy

    ein Guest

    unruh wrote:

    Have you tired https://www.centos.org/ ?



    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.14 (GNU/Linux)
    Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

    iQIcBAEBAgAGBQJSV5VSAAoJEHr/aeHyxuoQ4KkQALl/3e8NxcoxMdIi8cvP4/54
    ne9ck7YOgsKqXI1xCTP9amh8u4UR9NdHE/7qyRADP9AZXP7zs1SLZc9S5IzDBpiE
    1Dk3a8bRHMWWhrGrH3st5Y+JI/g0CIPQ0N4OCfyjgJYZusnAeN9Ihvvfm9jtAoH8
    y0+chICiKJSfuyQ6w3zcoNTXn+VHGl7ogrN7QbU6c+iz/ZcRZQYabMDrqsUU2h/t
    jyr2JeHFUFNrPL/VfA2+F5JGKoeoumvUZNa5jZLSzKgbpKQczHK6NTYOVQ9jr0Id
    yX7Yr100AaaD7UV/fP12oFSjtGeyZVIxE/drGKweoPOBYUYOvc1SmYzFESLleU+Z
    ij7p7+tycT4JCiO7969inV0ZzmnveFRYw6sn51k7mjmeiw5nnLgZocoDI2UVcCEs
    RITeQcfaQVnfTJHDZlBOzYqWu9EYzy2ANJ5lIpnN2brTreQlNnGmBS49WJSKmwZd
    20ffo0DZ8+bjeP5031qGd6jUAY2sUD9z0iZ8KGG8UQUi1r2JrU0MZlwnI0w5xMKQ
    HES77dMu3JZGfIVQD/E2vUAjSkSxRIWb/e4r0Qjjlwx82LvWXN+qVECF2Uudy5FF
    tduZfiawZCQbm+eA9oju4RKBEp0KK0+vp+odlymQwy0o//bpSjz22yN7Xjp25jd9
    +ooCR/RYvC8jHbHLEwF7
    =AGlY
    -----END PGP SIGNATURE-----
     
    ein, Oct 11, 2013
    #89
  10. !X is mentioned in the documentation...
     
    Richard Kettlewell, Oct 11, 2013
    #90
  11. Dynamic does not mean “changes every timeâ€. At a given moment the
    chances are that the best route to a given destination is the same as
    the previous time a packet traversed it.
     
    Richard Kettlewell, Oct 11, 2013
    #91
  12. billy

    dyrmak Guest

    En 62 lignes billy a écrit
    dans le vendredi, 11 octobre 2013 à 05:24:53 :
    Could it be DNS problem you are having on your own ?
    When the problem occurs http://@IP might give confirmation.
    If your router is mtu-modifiable lower it to 150 thereabouts
    along with your network card and see what happens.

    dyrmak
     
    dyrmak, Oct 11, 2013
    #92
  13. Well if you emailed that guy I expect he either sorted it out or
    forwarded it to the person who could. If not God intervened.

    Routes are decided by static entries and entries made by dynamic routing
    protocols on each router.

    http://en.wikipedia.org/wiki/Routing
    The owner of the router, sorta in consultation with their neighbours.

    --
    p-0.0-h the cat

    Internet Terrorist, Mass sock puppeteer, Agent provocateur, Gutter rat,
    Devil incarnate, Linux user#666, BaStarD hacker, Resident evil, Monkey Boy,
    Certifiable criminal, Spineless cowardly scum, textbook Psychopath,
    the SCOURGE, l33t p00h d3 tr0ll, p00h == lam3r, p00h == tr0ll, troll infâme,
    the OVERCAT [The BEARPAIR are dead, and we are its murderers], lowlife troll,
    shyster [pending approval by STATE_TERROR], cripple, sociopath, kook,
    smug prick, smartarse, arsehole, moron, idiot, imbecile, snittish scumbag,
    liar, and shill.

    Honorary SHYSTER and FRAUD awarded for services to Haberdashery.
    By Appointment to God Frank-Lin.
     
    p-0''0-h the cat (ES), Oct 11, 2013
    #93
  14. billy

    billy Guest

    Unfortunately, the short respit is over. This morning, I again, can
    no longer connect to the (new) centos.org. Sigh ...
    I just wish I understood this better ...

    $ traceroute centos.org
    traceroute to centos.org (85.12.30.227), 30 hops max, 60 byte packets
    1 192.168.1.1 (192.168.1.1) 7.301 ms 7.275 ms 7.258 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 20.126 ms 20.113
    ms 20.096 ms
    3 10.50.0.1 (10.50.0.1) 25.566 ms 25.551 ms 28.360 ms
    4 10.25.0.1 (10.25.0.1) 33.868 ms 36.207 ms 36.192 ms
    5 10.20.0.1 (10.20.0.1) 38.464 ms 38.448 ms 38.431 ms
    6 10.0.0.1 (10.0.0.1) 38.416 ms 118.426 ms 118.412 ms
    7 69.36.226.193 (69.36.226.193) 118.388 ms 33.867 ms 62.402 ms
    8 vl2.core2.scl.layer42.net (69.36.225.130) 62.387 ms 65.348 ms
    65.333 ms
    9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net (140.174.21.101) 65.319
    ms 65.304 ms 70.705 ms
    10 te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49) 70.708 ms
    70.685 ms te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85)
    70.653 ms
    11 be2047.ccr22.sjc01.atlas.cogentco.com (154.54.5.113) 70.638 ms
    70.623 ms be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 33.395
    ms
    12 be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 33.378 ms
    be2166.mpd21.sfo01.atlas.cogentco.com (154.54.28.69) 33.363 ms
    be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 51.255 ms
    13 be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 119.248 ms
    be2134.mpd21.mci01.atlas.cogentco.com (154.54.6.38) 119.241 ms
    be2132.ccr21.mci01.atlas.cogentco.com (154.54.30.54) 119.227 ms
    14 be2158.mpd21.ord01.atlas.cogentco.com (154.54.7.130) 119.220 ms
    be2157.ccr22.ord01.atlas.cogentco.com (154.54.6.118) 119.191 ms
    be2156.ccr21.ord01.atlas.cogentco.com (154.54.6.86) 119.177 ms
    15 be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6) 136.953 ms
    be2139.ccr21.bos01.atlas.cogentco.com (154.54.43.178) 136.938 ms
    be2079.ccr21.yyz02.atlas.cogentco.com (154.54.27.182) 136.908 ms
    16 te0-2-0-3.ccr21.lpl01.atlas.cogentco.com (154.54.85.214) 192.925
    ms be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 136.885 ms
    be2091.ccr22.ymq02.atlas.cogentco.com (154.54.44.98) 136.870 ms
    17 be2185.mpd22.ams03.atlas.cogentco.com (154.54.37.105) 194.858 ms
    be2182.ccr21.ams03.atlas.cogentco.com (154.54.77.245) 194.846 ms
    be2184.mpd21.ams03.atlas.cogentco.com (154.54.37.69) 194.831 ms
    18 be2183.ccr22.ams03.atlas.cogentco.com (154.54.58.70) 196.838 ms
    196.794 ms te0-3-0-3.mag21.ams03.atlas.cogentco.com (154.54.78.210)
    196.791 ms
    19 te0-3-0-0.mag21.ams03.atlas.cogentco.com (154.54.78.206) 199.738
    ms te0-7-0-10.mag21.ams03.atlas.cogentco.com (154.54.76.209) 212.950
    ms te0-7-0-6.mag21.ams03.atlas.cogentco.com (154.54.76.198) 221.482 ms
    20 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 212.901 ms 212.874
    ms 212.868 ms
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
     
    billy, Oct 11, 2013
    #94
  15. billy

    billy Guest

    DNS? Hmmm... would switching DNS servers affect the route taken?
    I'll try that, but, putting the IP address in the URL does not help.

    For example, http://85.12.30.227/ does the same thing as does
    http://www.centos.org as does http://centos.org
     
    billy, Oct 11, 2013
    #95
  16. billy

    billy Guest

    I can't disagree with you at all.

    From *my* experience, the route is pretty much static, and,
    when it fails, it pretty much fails at the same point for
    hours, days, or months at a time.

    For example, my traceroute two days ago to the old centos.org
    at 72.232.194.162 failed around hop 15, while last night a
    traceroute (and all other tests) worked fine to the new Centos.org
    at 85.12.30.227, yet, inexplicably, today, that same test failed!

    Here's a traceroute yesterday that worked and one that failed
    today, all to the same IP address!

    WORKED YESTERDAY:
    knoppix@Microknoppix:~$ traceroute www.centos.org
    traceroute to www.centos.org (85.12.30.227), 30 hops max, 60 byte
    packets
    1 192.168.1.1 (192.168.1.1) 2.940 ms 2.915 ms 5.895 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 23.983 ms 23.970
    ms 23.953 ms
    3 10.50.0.1 (10.50.0.1) 23.935 ms 23.920 ms 23.905 ms
    4 10.25.0.1 (10.25.0.1) 33.716 ms 33.701 ms 33.687 ms
    5 10.20.0.1 (10.20.0.1) 113.640 ms 127.266 ms 127.251 ms
    6 10.0.0.1 (10.0.0.1) 155.135 ms 198.034 ms 198.014 ms
    7 69.36.226.193 (69.36.226.193) 77.534 ms 88.951 ms 88.940 ms
    8 vl2.core2.scl.layer42.net (69.36.225.130) 101.711 ms 101.700
    ms 107.203 ms
    9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net
    (140.174.21.101) 111.422 ms 111.419 ms 111.404 ms
    10 te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 111.376
    ms te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49)
    111.352 ms te0-7-0-32.ccr21.sjc03.atlas.cogentco.com
    (154.54.11.85) 111.341 ms
    11 be2047.ccr22.sjc01.atlas.cogentco.com (154.54.5.113) 111.324
    ms 111.311 ms be2000.ccr21.sjc01.atlas.cogentco.com
    (154.54.6.105) 111.251 ms
    12 be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 111.238 ms
    be2166.mpd21.sfo01.atlas.cogentco.com (154.54.28.69) 58.660 ms
    be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 66.012 ms
    13 be2132.ccr21.mci01.atlas.cogentco.com (154.54.30.54) 168.366 ms
    be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 168.350 ms
    be2133.ccr22.mci01.atlas.cogentco.com (154.54.30.66) 165.709 ms
    14 be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82) 168.316
    ms 168.300 ms be2158.mpd21.ord01.atlas.cogentco.com
    (154.54.7.130) 168.285 ms
    15 be2079.ccr21.yyz02.atlas.cogentco.com (154.54.27.182) 139.555
    ms 133.671 ms be2138.ccr22.bos01.atlas.cogentco.com
    (154.54.43.202) 155.781 ms
    16 be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 139.505 ms
    te0-3-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.230)
    208.018 ms te0-4-0-3.ccr22.lpl01.atlas.cogentco.com
    (154.54.44.190) 208.007 ms
    17 te0-5-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.87.65) 211.696 ms
    be2182.ccr21.ams03.atlas.cogentco.com (154.54.77.245)
    226.780 ms te0-4-0-6.ccr22.lpl01.atlas.cogentco.com
    (154.54.44.214) 211.705 ms
    18 be2185.mpd22.ams03.atlas.cogentco.com (154.54.37.105) 229.203 ms
    te0-0-0-4.mag21.ams03.atlas.cogentco.com (154.54.76.190)
    310.294 ms be2185.mpd22.ams03.atlas.cogentco.com
    (154.54.37.105) 310.272 ms
    19 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.393 ms
    te0-0-0-12.mag21.ams03.atlas.cogentco.com (154.54.76.134) 310.218 ms
    10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.367 ms
    20 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.344 ms 305.321
    ms 310.147 ms
    21 85.12.30.227 (85.12.30.227) 305.263 ms !X 305.254 ms !X 205.255
    ms !X
    knoppix@Microknoppix:~$

    FAILED TODAY:
    knoppix@Microknoppix:~$ traceroute centos.org
    traceroute to centos.org (85.12.30.227), 30 hops max, 60 byte packets
    1 192.168.1.1 (192.168.1.1) 6.125 ms 6.094 ms 6.077 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 33.527 ms 33.515
    ms 33.499 ms
    3 10.50.0.1 (10.50.0.1) 33.485 ms 39.686 ms 47.348 ms
    4 10.25.0.1 (10.25.0.1) 82.142 ms 82.128 ms 82.113 ms
    5 10.20.0.1 (10.20.0.1) 101.802 ms 101.787 ms 101.771 ms
    6 10.0.0.1 (10.0.0.1) 111.627 ms 52.710 ms 52.672 ms
    7 69.36.226.193 (69.36.226.193) 52.637 ms 25.633 ms 25.613 ms
    8 vl2.core2.scl.layer42.net (69.36.225.130) 25.599 ms 25.584 ms
    32.306 ms
    9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net (140.174.21.101) 36.545
    ms 36.530 ms 36.515 ms
    10 te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 36.477 ms
    te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49) 36.463 ms
    te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 36.433 ms
    11 be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 36.442 ms
    36.427 ms 17.909 ms
    12 be2164.ccr21.sfo01.atlas.cogentco.com (154.54.28.33) 26.295 ms
    be2166.mpd21.sfo01.atlas.cogentco.com (154.54.28.69) 26.279 ms
    be2167.mpd22.sfo01.atlas.cogentco.com (154.54.28.77) 31.666 ms
    13 be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 81.979 ms
    be2134.mpd21.mci01.atlas.cogentco.com (154.54.6.38) 81.949 ms
    be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 81.943 ms
    14 be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82) 91.739 ms
    110.049 ms be2156.ccr21.ord01.atlas.cogentco.com (154.54.6.86) 110.039
    ms
    15 be2140.ccr22.bos01.atlas.cogentco.com (154.54.43.186) 118.042 ms
    be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6) 112.212 ms
    be2137.ccr21.bos01.atlas.cogentco.com (154.54.43.194) 118.011 ms
    16 te0-2-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.190) 185.107
    ms te0-0-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.170) 185.082 ms
    185.048 ms
    17 te0-3-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.6.142) 191.782 ms
    be2184.mpd21.ams03.atlas.cogentco.com (154.54.37.69) 204.548 ms
    te0-5-0-4.ccr22.lpl01.atlas.cogentco.com (154.54.87.53) 191.749 ms
    18 te0-7-0-0.mag21.ams03.atlas.cogentco.com (154.54.76.170) 191.771
    ms 199.379 ms be2184.mpd21.ams03.atlas.cogentco.com (154.54.37.69)
    199.369 ms
    19 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 199.355 ms 199.325
    ms te0-0-0-4.mag21.ams03.atlas.cogentco.com (154.54.76.190) 207.195 ms
    20 * * 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 188.627 ms
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    knoppix@Microknoppix:~$
     
    billy, Oct 11, 2013
    #96
  17. billy

    billy Guest

    Yes. I had mentioned it earlier, but, I have an old thread there
    on the same topic, and I also contacted the gmane centos group
    and I contacted the web sysadmins.

    They're all saying that it works for them ...
     
    billy, Oct 11, 2013
    #97
  18. billy

    billy Guest

    BTW, I have resigned myself to the conclusion that, in a cynical
    way, "the Internet doesn't really work", since it arbitrarily
    works for 99% of the sites I want to connect to, but, I know of
    two that it just is flaky on.
    centos.org <== which I do care about
    linuxreference.com <== which I don't care about

    The sheer capriciousness of the results is what's killing me because
    it makes no sense for the Internet to not work.

    The entire thing was designed to work - and this indicates that
    (for me, for a few sites), it's just not working.

    Makes no sense - and that's what is killing me inside, eating me
    up.
     
    billy, Oct 11, 2013
    #98
  19. billy

    billy Guest

    That's me! :)

    Anyway, the problem is back, and shown below.

    If I had a better DIAGNOSTIC TOOL, I'd feel better with the data.
    It's not the MTU, the TTL, the DNS server, the operating system,
    etc.

    I just wish I had a better diagnostic tool than traceroute...

    knoppix@Microknoppix:~$ traceroute !$
    traceroute centos.org
    traceroute to centos.org (85.12.30.227), 30 hops max, 60 byte packets
    1 192.168.1.1 (192.168.1.1) 6.125 ms 6.094 ms 6.077 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 33.527 ms 33.515
    ms 33.499 ms
    3 10.50.0.1 (10.50.0.1) 33.485 ms 39.686 ms 47.348 ms
    4 10.25.0.1 (10.25.0.1) 82.142 ms 82.128 ms 82.113 ms
    5 10.20.0.1 (10.20.0.1) 101.802 ms 101.787 ms 101.771 ms
    6 10.0.0.1 (10.0.0.1) 111.627 ms 52.710 ms 52.672 ms
    7 69.36.226.193 (69.36.226.193) 52.637 ms 25.633 ms 25.613 ms
    8 vl2.core2.scl.layer42.net (69.36.225.130) 25.599 ms 25.584 ms
    32.306 ms
    9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net (140.174.21.101) 36.545
    ms 36.530 ms 36.515 ms
    10 te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 36.477 ms
    te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49) 36.463 ms
    te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 36.433 ms
    11 be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 36.442 ms
    36.427 ms 17.909 ms
    12 be2164.ccr21.sfo01.atlas.cogentco.com (154.54.28.33) 26.295 ms
    be2166.mpd21.sfo01.atlas.cogentco.com (154.54.28.69) 26.279 ms
    be2167.mpd22.sfo01.atlas.cogentco.com (154.54.28.77) 31.666 ms
    13 be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 81.979 ms
    be2134.mpd21.mci01.atlas.cogentco.com (154.54.6.38) 81.949 ms
    be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 81.943 ms
    14 be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82) 91.739 ms
    110.049 ms be2156.ccr21.ord01.atlas.cogentco.com (154.54.6.86) 110.039
    ms
    15 be2140.ccr22.bos01.atlas.cogentco.com (154.54.43.186) 118.042 ms
    be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6) 112.212 ms
    be2137.ccr21.bos01.atlas.cogentco.com (154.54.43.194) 118.011 ms
    16 te0-2-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.190) 185.107
    ms te0-0-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.170) 185.082 ms
    185.048 ms
    17 te0-3-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.6.142) 191.782 ms
    be2184.mpd21.ams03.atlas.cogentco.com (154.54.37.69) 204.548 ms
    te0-5-0-4.ccr22.lpl01.atlas.cogentco.com (154.54.87.53) 191.749 ms
    18 te0-7-0-0.mag21.ams03.atlas.cogentco.com (154.54.76.170) 191.771
    ms 199.379 ms be2184.mpd21.ams03.atlas.cogentco.com (154.54.37.69)
    199.369 ms
    19 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 199.355 ms 199.325
    ms te0-0-0-4.mag21.ams03.atlas.cogentco.com (154.54.76.190) 207.195 ms
    20 * * 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 188.627 ms
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    knoppix@Microknoppix:~$
    knoppix@Microknoppix:~$ traceroute linuxreference.com
    traceroute to linuxreference.com (72.232.194.162), 30 hops max, 60 byte
    packets
    1 192.168.1.1 (192.168.1.1) 2.834 ms 2.810 ms 9.836 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 19.635 ms 19.625
    ms 19.610 ms
    3 10.50.0.1 (10.50.0.1) 46.754 ms 46.748 ms 46.730 ms
    4 10.25.0.1 (10.25.0.1) 51.077 ms 51.065 ms 51.051 ms
    5 10.20.0.1 (10.20.0.1) 53.594 ms 53.583 ms 53.574 ms
    6 10.0.0.1 (10.0.0.1) 53.548 ms 37.843 ms 37.816 ms
    7 69.36.226.193 (69.36.226.193) 35.370 ms 35.323 ms 37.883 ms
    8 vl2.core1.scl.layer42.net (69.36.225.129) 37.878 ms 37.863 ms
    37.847 ms
    9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 37.832 ms 59.609 ms
    59.597 ms
    10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 112.224 ms 112.214 ms
    104.915 ms
    11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 104.885 ms 104.859
    ms 104.813 ms
    12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 101.385 ms 133.165 ms
    133.144 ms
    13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 111.137 ms 111.135 ms
    111.097 ms
    14 border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 111.084 ms
    border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 111.070 ms
    border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 114.155 ms
    15 layered-11.border1.dal004.pnap.net (63.251.44.74) 114.144 ms
    114.133 ms 114.110 ms
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    knoppix@Microknoppix:~$
     
    billy, Oct 11, 2013
    #99
  20. billy

    billy Guest

    You just gave me a diagnostic idea!
    You guys have modems, but I have a transceiver instead of a modem.
    I can log into the radio on the roof and let it run the traceroute!
    That way, my entire house is eliminated as a variable!

    Here's the traceroute just now from the radio:
    RADIO: traceroute centos.org
    # Host IP Responses
    1 10.50.0.1 9.148 ms · 6.287 ms · 1.944 ms
    2 10.25.0.1 12.735 ms · 9.051 ms · 10.880 ms
    3 10.20.0.1 16.225 ms · 56.871 ms · 14.400 ms
    4 10.0.0.1 53.791 ms · 40.530 ms · 12.047 ms
    5 69.36.226.193 19.931 ms · 72.111 ms ·
    30.576 ms
    6 69.36.225.129 21.656 ms · 32.959 ms ·
    20.087 ms
    7 140.174.21.101 15.294 ms · 20.615 ms ·
    18.735 ms
    8 154.54.11.85 18.116 ms · 8.769 ms ·
    16.054 ms
    9 154.54.5.113 13.920 ms · 14.242 ms ·
    15.359 ms
    10 154.54.28.33 18.270 ms · 14.705 ms ·
    20.000 ms
    11 154.54.30.66 76.472 ms · 81.262 ms ·
    66.369 ms
    12 154.54.6.86 82.061 ms · 86.454 ms · 102.949 ms
    13 154.54.42.10 92.515 ms · 94.962 ms ·
    99.695 ms
    14 154.54.44.106 94.444 ms · 169.748 ms ·
    110.654 ms
    15 154.54.6.142 178.136 ms · 166.632 ms ·
    200.960 ms
    16 154.54.37.234 178.396 ms · 227.571 ms ·
    182.961 ms
    17 154.54.76.198 253.605 ms · 197.191 ms ·
    214.669 ms
    18 85.12.30.227 170.040 ms !C · 193.573
    ms · 192.897 ms

    Huh? It made it through? Let me run a quick traceroute on the laptop!
    $ traceroute centos.org
    traceroute to centos.org (85.12.30.227), 30 hops max, 60 byte packets
    1 192.168.1.1 (192.168.1.1) 7.298 ms 7.264 ms 7.247 ms
    2 67-218-118-85.ridgewireless.net (67.218.118.85) 20.239 ms 20.227
    ms 20.210 ms
    3 10.50.0.1 (10.50.0.1) 23.845 ms 23.830 ms 23.814 ms
    4 10.25.0.1 (10.25.0.1) 37.873 ms 37.860 ms 37.844 ms
    5 10.20.0.1 (10.20.0.1) 37.829 ms 40.619 ms 40.597 ms
    6 10.0.0.1 (10.0.0.1) 56.534 ms 134.350 ms 134.330 ms
    7 69.36.226.193 (69.36.226.193) 134.315 ms 97.897 ms 97.878 ms
    8 vl2.core2.scl.layer42.net (69.36.225.130) 97.869 ms 97.845 ms
    97.834 ms
    9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net (140.174.21.101)
    102.205 ms 97.803 ms 102.171 ms
    10 te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 97.761 ms
    102.118 ms te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49)
    102.104 ms
    11 be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 102.098 ms
    be2047.ccr22.sjc01.atlas.cogentco.com (154.54.5.113) 102.081 ms
    be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 68.723 ms
    12 be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 68.708 ms
    be2167.mpd22.sfo01.atlas.cogentco.com (154.54.28.77) 68.693 ms
    be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 128.983 ms
    13 be2134.mpd21.mci01.atlas.cogentco.com (154.54.6.38) 138.168 ms
    138.156 ms be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 144.404
    ms
    14 be2158.mpd21.ord01.atlas.cogentco.com (154.54.7.130) 160.871 ms
    be2157.ccr22.ord01.atlas.cogentco.com (154.54.6.118) 160.858 ms
    be2156.ccr21.ord01.atlas.cogentco.com (154.54.6.86) 160.827 ms
    15 be2139.ccr21.bos01.atlas.cogentco.com (154.54.43.178) 167.524 ms
    be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6) 160.809 ms
    be2081.ccr21.yyz02.atlas.cogentco.com (154.54.42.10) 160.785 ms
    16 be2091.ccr22.ymq02.atlas.cogentco.com (154.54.44.98) 167.479 ms
    be2092.ccr21.ymq02.atlas.cogentco.com (154.54.25.26) 167.456 ms
    be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 167.431 ms
    17 te0-5-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.87.65) 235.370 ms
    te0-5-0-6.ccr22.lpl01.atlas.cogentco.com (154.54.87.57) 235.330 ms
    be2183.ccr22.ams03.atlas.cogentco.com (154.54.58.70) 235.329 ms
    18 te0-0-0-10.mag21.ams03.atlas.cogentco.com (154.54.37.234) 225.581
    ms be2185.mpd22.ams03.atlas.cogentco.com (154.54.37.105) 225.554 ms
    be2183.ccr22.ams03.atlas.cogentco.com (154.54.58.70) 215.695 ms
    19 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 215.661 ms
    te0-3-0-15.mag21.ams03.atlas.cogentco.com (154.54.78.217) 225.499 ms
    10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 215.632 ms
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    Hmmm... so maybe it "is" my home broadband router (netgear standard
    stuff).

    Let me try with the linuxreference site...
     
    billy, Oct 11, 2013
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.