My Packets Take a Detour

I am trying to telnet (remote access) to a machine about a block and a half away. But my residential DSL provider is Bell South. The machine is on the campus at UM. And tonight my packets can't quite seem to get there….could it be because my packets have to take quite a long detour — through a bad neighborhood — to get across the street?


Host % Sent Recv Best Avrg Wrst Last
65.3.10.1 40 10 6 15 36 109 31
adsl-152-108-1.mia.bellsouth.net 30 10 7 0 15 31 16
205.152.145.161 30 10 7 15 20 32 16
axr00mia-1-3-1.bellsouth.net 50 10 5 15 15 16 16
pxr00mia-2-0-0.bellsouth.net 50 10 5 15 22 47 16
65.57.174.1 30 10 7 15 17 31 16
so-7-0-0.mp2.Miami1.Level3.net 50 10 5 15 28 78 15
as-2-0.bbr1.Washington1.Level3.net 20 10 8 31 60 94 79
so-6-0-0.edge1.Washington1.Level3.net 40 10 6 31 221 1094 62
qwest-level3-oc48.Washington1.Level3.net 50 10 5 47 62 78 63
205.171.251.33 30 10 7 31 60 79 62
dca-core-02.inet.qwest.net 30 10 7 31 154 734 63
tpa-core-01.inet.qwest.net 50 10 5 62 71 78 63
tpa-edge-11.inet.qwest.net 60 10 4 78 78 78 78
No response from host 100 10 0 0 0 0 0

[Table moved off front because it messed up the page at lower resolution]

This entry was posted in Internet. Bookmark the permalink.

5 Responses to My Packets Take a Detour

  1. Andrew says:

    - You seem to be losing more packets than you should, all along the way.
    - Can you ever do a traceroute into UM? (In my experience they’ve always been blocked. tcptraceroute has worked for me, if you can find that for Windows.)
    - Why are you using telnet rather than ssh?

  2. Michael says:

    I am using ssh, actually. I was just being sloppy. UM won’t allow telent any more, which is just as well.

  3. Michael says:

    I tried to run tcptraceroute (via lft, which uses Cygwin. But all I got was this…

    AMF@AMF-Sonata /bin
    $ lft-2.2-win32.exe osaka.law.miami.edu

    WSAIoctl: No error
    Tracing ___________________

    LFT can’t seem to round-trip. Local packet filter in the way?

    TTL LFT trace to 129.171.187.81:80/tcp
    ** [80/tcp failed] Try alternate options or use -V to see packets.

    AMF@AMF-Sonata /bin
    $ lft-2.2-win32.exe -V osaka.law.miami.edu
    Setting my ISN = 829050412
    Using device eth0, AMF-Sonata (192.168.1.101):53
    WSAIoctl: No error
    SEND TTL=0 TSEQ=829050412 FLAGS=2
    SEND TTL=1 TSEQ=829050413 FLAGS=2
    sendto: No error

    AMF@AMF-Sonata /bin

  4. Pinski says:

    Thats not too bad you go through two major cities, to go to University of Cincinnati from my house (about 5 miles) we go from Cincinnati to Chicago to New York to Ashburn, VA to Columbus to Cincinnati, now that is probably worse. I just wish my packets got frequent flier miles.

  5. Andrew says:

    Here’s what I get with tcptraceroute from a computer in Coral Gables connected to the net via an AT&T Broadband cable modem. It goes through Atlanta, which is typical for connections from there to UM, I’ve found.

    It looks like the program you tried can’t send the packets it wants to. Make sure you are running it under a user account which can send via raw sockets (root or Administrator), because it certainly needs them to generate packets with different TTLs. And, as the error message mentions, make sure the local firewall isn’t getting in the way.

    [andrew@nc.ath.cx] ~> tcptraceroute osaka.law.miami.edu
    Selected device sis0, address 65.34.156.59, port 1039 for outgoing packets
    Tracing the path to osaka.law.miami.edu (129.171.187.81) on TCP port 80, 30 hops max
    1 10.246.0.1 (10.246.0.1) 9.946 ms 14.120 ms 11.792 ms
    2 btr01-p4-0.pmbhhe1.fl.attbb.net (66.176.1.49) 13.399 ms 14.306 ms 13.750 ms
    3 rtr-jaxc-pos22.pompano.net (66.176.1.117) 13.929 ms 12.964 ms 13.865 ms
    4 12.119.94.9 (12.119.94.9) 16.127 ms 18.954 ms 14.187 ms
    5 gbr4-p100.ormfl.ip.att.net (12.123.218.66) 17.729 ms 18.053 ms 17.754 ms
    6 tbr1-p012401.attga.ip.att.net (12.122.12.121) 31.773 ms 27.229 ms 29.760 ms
    7 ggr1-p360.attga.ip.att.net (12.123.20.249) 27.387 ms 27.177 ms 25.806 ms
    8 atl-brdr-03.inet.qwest.net (205.171.1.25) 25.986 ms 29.275 ms 25.730 ms
    9 atl-core-02.inet.qwest.net (205.171.21.101) 26.036 ms 26.768 ms 27.971 ms
    10 atl-core-01.inet.qwest.net (205.171.21.149) 28.540 ms 28.344 ms 26.981 ms
    11 tpa-core-01.inet.qwest.net (205.171.5.66) 38.151 ms 37.151 ms 38.012 ms
    12 tpa-edge-11.inet.qwest.net (205.171.27.110) 37.861 ms 38.896 ms 38.561 ms
    13 * * *
    14 nat034.tel.miami.edu (65.115.176.34) 43.250 ms 41.908 ms 44.020 ms
    15 65.115.176.97 (65.115.176.97) 42.142 ms 43.516 ms 46.270 ms
    16 129.171.200.33 (129.171.200.33) 44.161 ms 41.915 ms 49.758 ms
    17 buddhi2.ir.miami.edu (129.171.32.26) 42.444 ms 42.766 ms 43.154 ms
    18 lawns500.law.miami.edu (129.171.187.129) 42.528 ms 42.815 ms 42.004 ms
    19 osaka.law.miami.edu (129.171.187.81) [closed] 42.085 ms 43.587 ms 43.836 ms

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Notify me of followup comments via e-mail. You can also subscribe without commenting.