[wellylug] Re: Can't access linux conf site

Mark Foster blakjak at blakjak.net
Sun Nov 13 20:14:22 NZDT 2005


Jethro Carr wrote:


> 
> here's what I'm getting:
> 
> could you give me your traceroute output? I'd like to see what route
> yours is taking.
> 
> -------------
> traceroute to lca2006.linux.org.au (202.91.207.101), 30 hops max, 40 byte packets
>  1  192.168.0.1 (192.168.0.1)  15.174 ms  14.609 ms  8.159 ms
>  2  203-109-156-250.ihug.net (203.109.156.250)  93.483 ms  92.472 ms  81.680 ms
>  3  Vl117-tig-nz-core-1.ihug.net (203.109.156.209)  91.387 ms  92.103 ms  94.348 ms
>  4  203-109-156-138.ihug.net (203.109.156.138)  104.402 ms  97.034 ms  92.700 ms
>  5  ba3-atm9-0-0-71-acld.auckland.clix.net.nz (203.97.2.61)  104.087 ms  90.357 ms  91.170 ms
>  6  ge-0-2-0-1.xcore1.acld.telstraclear.net (203.98.50.251)  82.182 ms  87.373 ms  93.075 ms
>  7  ge0-0-0.nzsx-core1.akl.telstraclear.net (203.98.4.3)  91.381 ms  94.558 ms  99.586 ms
>  8  i-4-3.syd-core03.net.reach.com (202.84.219.97)  117.981 ms  158.538 ms  131.052 ms
>  9  i-6-0.syd-core01.net.reach.com (202.84.249.13)  111.612 ms  136.465 ms  125.887 ms
> 10  unknown.net.reach.com (134.159.125.74)  135.800 ms  148.428 ms  131.237 ms
> 11  10GigabitEthernet3-0.ken-core4.Sydney.telstra.net (203.50.6.85)  108.725 ms  125.516 ms  107.699 ms
> 12  TenGigabitEthernet8-1.ken17.Sydney.telstra.net (203.50.20.27)  105.948 ms  136.700 ms  128.230 ms
> 13  ge-2-1-0-25.bdr5.hay.connect.com.au (203.63.130.250)  124.190 ms  138.990 ms  135.057 ms
> 14  so-3-1-0.cre1.hay.connect.com.au (202.10.4.99)  120.515 ms  151.429 ms  146.342 ms
> 15  so-5-0-0.cre1.bur.connect.com.au (202.10.0.251)  132.223 ms  201.533 ms  148.585 ms
> 16  so-0-0-1.dst2.mel.connect.com.au (202.10.0.134)  132.104 ms  130.144 ms  132.438 ms
> 17  gigabitethernet0-2.cor6.mel.connect.com.au (203.63.11.228)  142.835 ms  156.246 ms  150.885 ms
> 18  DDES142069-1.gw.connect.com.au (210.8.12.249)  147.185 ms  162.120 ms  130.505 ms
> 19  ge0-2.cr1.mel2.techex.net.au (203.222.128.117)  159.033 ms  152.442 ms  146.273 ms
> 20  218-128-222-203.rev.techex.net.au (203.222.128.218)  146.534 ms  157.031 ms  141.627 ms
> 21  202-91-196-13.gpm.net.au (202.91.196.13)  157.484 ms  166.795 ms  181.004 ms
> 22  * * *
> 23  uml1.linux.org.au (202.91.207.101)  234.579 ms  255.667 ms  199.135 ms
> 24  uml1.linux.org.au (202.91.207.101)  195.926 ms  225.132 ms  335.114 ms
> 

traceroute to lca2006.linux.org.au (202.91.207.101), 30 hops max, 38 
byte packets
  1  dsl500 (192.168.2.254)  1.411 ms  0.982 ms  0.903 ms
  2  222-152-192-1.jetstream.xtra.co.nz (222.152.192.1)  45.029 ms
  3  222.152.127.131 (222.152.127.131)  195.449 ms  139.272 ms  263.576
  4  ge0-3-0-1006.akbr3.global-gateway.net.nz (203.96.120.93)  48.900 ms
  5  p1-7.sybr2.global-gateway.net.nz (202.37.245.58)  70.256 ms  70.609
  6  p6-0.sybr3.global-gateway.net.nz (203.96.120.86)  70.466 ms  72.109
  7  connect1.sybr3.global-gateway.net.nz (203.96.120.122)  71.048 ms
  8  so-4-1-0.cre1.hay.connect.com.au (202.10.4.93)  68.408 ms  73.746 ms
  9  so-5-0-0.cre1.bur.connect.com.au (202.10.0.251)  87.591 ms  84.178
10  so-0-0-1.dst2.mel.connect.com.au (202.10.0.134)  87.709 ms  87.266
11  gigabitethernet0-1.cor6.mel.connect.com.au (203.63.11.68)  86.124 ms
12  DDES142069-1.gw.connect.com.au (210.8.12.249)  85.942 ms  89.735 ms
13  ge0-2.cr1.mel2.techex.net.au (203.222.128.117)  90.520 ms  88.388 ms
14  218-128-222-203.rev.techex.net.au (203.222.128.218)  90.433 ms
15  202-91-196-13.gpm.net.au (202.91.196.13)  134.035 ms  159.902 ms
16  * * *
17  uml1.linux.org.au (202.91.207.101)  536.048 ms  365.878 ms  485.937
18  uml1.linux.org.au (202.91.207.101)  217.257 ms  226.341 ms  364.304


I've trimmed the lines for brevity as my client is trying to wrap them.

so-3-1-0.cre1.hay.connect.com.au (202.10.4.99) is the first common hop 
between my route via Global Gateway and yours via Telstra Clear.

Anyone else on the list using TCL and experiencing similar to Jethro?

Heres another option, via Quicksilver:

blakjak at maverick:~$ traceroute  lca2006.linux.org.au
traceroute to lca2006.linux.org.au (202.91.207.101), 30 hops max, 38 
byte packets
  1  akl-colo1.helix.net.nz (202.50.176.78)  0.365 ms  0.179 ms  0.174 ms
  2  202-49-59-254.level48.net (202.49.59.254)  0.378 ms  0.370 ms  0.342
  3  qsi2.ape.net.nz (192.203.154.29)  0.710 ms  0.837 ms  0.781 ms
  4  gateway3-acc-skyt.qsi.net.nz (202.89.128.91)  1.349 ms  1.562 ms
  5  Mercury-Quicksilver-FE-1-0-0-402-ar1.akl1.gblx.net (203.192.179.9)
  6  po2-2.gw2.syd1.asianetcom.net (202.147.55.89)  27.685 ms  25.847 ms
  7  61.88.133.205 (61.88.133.205)  46.282 ms  42.210 ms  42.618 ms
  8  GE-WAN3-4.un2.optus.net.au (203.202.36.137)  40.999 ms  40.394 ms
  9  ConnectCom.un2.optus.net.au (61.88.171.206)  28.104 ms  29.250 ms
10  ge-0-1-0.dst2.syd.connect.com.au (203.63.11.205)  29.976 ms  30.636
11  so-3-0-0.cre1.syd.connect.com.au (202.10.0.117)  27.724 ms  28.718
12  as0.cre1.hay.connect.com.au (202.10.0.59)  28.718 ms  28.794 ms
13  so-5-0-0.cre1.bur.connect.com.au (202.10.0.251)  42.407 ms  46.314
14  so-0-0-1.dst2.mel.connect.com.au (202.10.0.134)  51.745 ms  42.164
15  gigabitethernet0-1.cor6.mel.connect.com.au (203.63.11.68)  44.437 ms
16  DDES142069-1.gw.connect.com.au (210.8.12.249)  95.006 ms  96.411 ms
17  ge0-2.cr1.mel2.techex.net.au (203.222.128.117)  43.018 ms  44.061 ms
18  218-128-222-203.rev.techex.net.au (203.222.128.218)  44.523 ms
19  202-91-196-13.gpm.net.au (202.91.196.13)  74.362 ms  72.364 ms
20  * * *
21  uml1.linux.org.au (202.91.207.101)  49.651 ms  48.874 ms  49.767 ms
22  uml1.linux.org.au (202.91.207.101)  49.000 ms  50.710 ms  47.613 ms



Also, with a standard MTU, you can do testing with ping, like so:

     -s packetsize
               Specifies  the number of data bytes to be sent.  The 
default is 56, which translates into 64 ICMP data bytes
               when combined with the 8 bytes of ICMP header data.


So you can send ping packets of custom sizes and see where MTU actually 
comes in to play.

Mark.

(And apologies for those getting sick of this thread, some of this info 
is very likely useful to have in the archives, however...)





More information about the wellylug mailing list