Inaccessible network from Verizon, accessible elsewhere.

Network IP Dog network.ipdog at gmail.com
Sun Dec 11 16:46:20 CST 2011


>From 90701 - Artesia, CA.   FIOS

No Go here too!!!



C:\WINDOWS\system32>tracert 106.187.34.1

Tracing route to gw-li377.linode.com [106.187.34.1]
over a maximum of 30 hops:

  1    22 ms    34 ms    <1 ms  Tomato [192.168.100.1]
  2    49 ms     1 ms     1 ms  Verizon [192.168.1.1]
  3    36 ms     6 ms     6 ms  L100.LSANCA-VFTTP-114.verizon-gni.net
[173.58.21
1.1]
  4    24 ms     9 ms     9 ms  G0-9-1-4.LSANCA-LCR-21.verizon-gni.net
[130.81.1
85.72]
  5    24 ms     9 ms     8 ms  so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net
[130.81
.151.246]
  6    24 ms     9 ms     8 ms  0.ae1.BR3.LAX15.ALTER.NET [152.63.2.129]
  7    38 ms     8 ms     8 ms  ae6.edge1.LosAngeles9.level3.net
[4.68.62.169]
  8    25 ms    10 ms    10 ms  63.146.26.70
  9    24 ms     9 ms     8 ms  lajbb001.kddnet.ad.jp [59.128.2.173]
 10    24 ms     9 ms     8 ms  lajbb001.kddnet.ad.jp [59.128.2.181]
 11   140 ms   110 ms   108 ms  otejbb203.kddnet.ad.jp [203.181.100.9]
 12   140 ms   124 ms   111 ms  cm-fcu203.kddnet.ad.jp [124.215.194.164]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *     ^C
C:\WINDOWS\system32>tracert 106.187.34.33

Tracing route to li377-33.members.linode.com [106.187.34.33]
over a maximum of 30 hops:

  1    22 ms     1 ms    <1 ms  Tomato [192.168.100.1]
  2    31 ms     1 ms     1 ms  Verizon [192.168.1.1]
  3    51 ms    10 ms    11 ms  L100.LSANCA-VFTTP-114.verizon-gni.net
[173.58.21
1.1]
  4    42 ms     9 ms    33 ms  G0-9-1-4.LSANCA-LCR-21.verizon-gni.net
[130.81.1
85.72]
  5    40 ms    15 ms     9 ms  so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net
[130.81
.151.246]
  6    31 ms     8 ms     8 ms  0.ae1.BR3.LAX15.ALTER.NET [152.63.2.129]
  7    61 ms    10 ms    16 ms  lap-brdr-03.inet.qwest.net [63.146.26.209]
  8    31 ms    10 ms    10 ms  63.146.26.70
  9    31 ms     9 ms     9 ms  lajbb001.kddnet.ad.jp [59.128.2.173]
 10    31 ms     9 ms     8 ms  lajbb001.kddnet.ad.jp [59.128.2.181]
 11   125 ms   118 ms   109 ms  otejbb203.kddnet.ad.jp [203.181.100.9]
 12   156 ms   111 ms   143 ms  124.215.199.122
 13   126 ms   112 ms   137 ms  124.215.199.122
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *     ^C
C:\WINDOWS\system32>


E = 4:32  &  Cheers!!!

-----Original Message-----
From: Lee [mailto:ler762 at gmail.com] 
Sent: Sunday, December 11, 2011 6:44 AM
To: NetSecGuy
Cc: nanog at nanog.org
Subject: Re: Inaccessible network from Verizon, accessible elsewhere.

On 12/10/11, NetSecGuy <netsecguy at gmail.com> wrote:
> I have a Linode VPS in Japan that I can't access from Verizon FIOS,
> but can access from other locations.  I'm not sure who to blame.

I can't get to 106.187.34.33 or 106.187.34.1 using Verizon FIOS

C:\>tracert 106.187.34.33

Tracing route to li377-33.members.linode.com [106.187.34.33]
over a maximum of 30 hops:
    [.. snip ..]
  5    23 ms     4 ms     4 ms
so-14-0-0-0.RES-BB-RTR2.verizon-gni.net [130.81.22.56]
  6    73 ms     6 ms     7 ms  0.ae2.BR2.IAD8.ALTER.NET [152.63.34.73]
  7     8 ms     6 ms     7 ms  dcp-brdr-03.inet.qwest.net [63.146.26.105]
  8     8 ms     9 ms     9 ms  sl-crs1-dc-0-1-0-0.sprintlink.net
[144.232.19.229]
  9    28 ms    26 ms    44 ms  sl-crs1-dc-0-5-3-0.sprintlink.net
[144.232.24.37]
 10   177 ms   176 ms   177 ms  lajbb001.kddnet.ad.jp [59.128.2.173]
 11    43 ms    41 ms    42 ms  sl-crs1-oma-0-9-2-0.sprintlink.net
[144.232.2.177]
 12   291 ms     *      301 ms  cm-fcu203.kddnet.ad.jp [124.215.194.164]
 13   286 ms   279 ms   282 ms  124.215.199.122
 14    81 ms    81 ms    82 ms  sl-crs1-sj-0-5-3-0.sprintlink.net
[144.232.20.99]
 15    88 ms    86 ms    87 ms  sl-st20-pa-9-0-0.sprintlink.net
[144.232.8.108]
 16   405 ms   406 ms   399 ms  144.223.243.126
 17   364 ms   386 ms   406 ms  pajbb001.kddnet.ad.jp [111.87.3.41]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *     ^C

C:\>tracert 106.187.34.1

Tracing route to gw-li377.linode.com [106.187.34.1]
over a maximum of 30 hops:
    [.. snip ..]
  5     5 ms    24 ms    24 ms  so-3-1-0-0.RES-BB-RTR2.verizon-gni.net
[130.81.151.232]
  6     7 ms     7 ms     7 ms  0.ae2.BR2.IAD8.ALTER.NET [152.63.34.73]
  7     8 ms     7 ms     7 ms  dcp-brdr-03.inet.qwest.net [63.146.26.105]
  8    84 ms    84 ms    84 ms  lap-brdr-03.inet.qwest.net [67.14.22.78]
  9   171 ms   174 ms   176 ms  63.146.26.70
 10   178 ms   177 ms   177 ms  lajbb001.kddnet.ad.jp [59.128.2.173]
 11   283 ms   284 ms   284 ms  otejbb203.kddnet.ad.jp [203.181.100.9]
 12   289 ms   287 ms   287 ms  cm-fcu203.kddnet.ad.jp [124.215.194.164]
 13     *        *        *     Request timed out.
 14    83 ms    81 ms    82 ms  sl-crs1-sj-0-12-0-1.sprintlink.net
[144.232.9.224]
 15     *        *        *     Request timed out.
 16   403 ms   407 ms   404 ms  144.223.243.126
 17     *        *        *     Request timed out.
 18   501 ms   499 ms   501 ms
otejbb203.kddnet.ad.jp.100.181.203.in-addr.arpa [203.181.100.137]
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *     ^C

Lee

>
> The host, 106.187.34.33, is behind the gateway 106.187.34.1:
>
> From FIOS to 106.187.34.1  (this works).
>
> traceroute to 106.187.34.1 (106.187.34.1), 64 hops max, 52 byte packets
>
>  4  so-6-1-0-0.phil-bb-rtr2.verizon-gni.net (130.81.199.4)  9.960 ms
> 9.957 ms  6.666 ms
>  5  so-8-0-0-0.lcc1-res-bb-rtr1-re1.verizon-gni.net (130.81.17.3)
> 12.298 ms  13.463 ms  13.706 ms
>  6  0.ae2.br1.iad8.alter.net (152.63.32.158)  14.571 ms  14.372 ms  14.003
> ms
>  7  204.255.169.218 (204.255.169.218)  14.692 ms  14.759 ms  13.670 ms
>  8  sl-crs1-dc-0-1-0-0.sprintlink.net (144.232.19.229)  13.077 ms
> 12.577 ms  14.954 ms
>  9  sl-crs1-nsh-0-5-5-0.sprintlink.net (144.232.18.200)  31.443 ms
>     sl-crs1-dc-0-5-3-0.sprintlink.net (144.232.24.37)  33.005 ms
>     sl-crs1-nsh-0-5-5-0.sprintlink.net (144.232.18.200)  31.507 ms
> 10  sl-crs1-kc-0-0-0-2.sprintlink.net (144.232.18.112)  57.610 ms
> 58.322 ms  59.098 ms
> 11  otejbb204.kddnet.ad.jp (203.181.100.45)  196.063 ms
>     otejbb203.kddnet.ad.jp (203.181.100.13)  188.846 ms
>     otejbb204.kddnet.ad.jp (203.181.100.21)  195.277 ms
> 12  cm-fcu203.kddnet.ad.jp (124.215.194.180)  214.760 ms
>     cm-fcu203.kddnet.ad.jp (124.215.194.164)  198.925 ms
>     cm-fcu203.kddnet.ad.jp (124.215.194.180)  200.583 ms
> 13  124.215.199.122 (124.215.199.122)  193.086 ms *  194.967 ms
>
> This does not work from FIOS:
>
> traceroute to 106.187.34.33 (106.187.34.33), 64 hops max, 52 byte packets
>
>  4  so-6-1-0-0.phil-bb-rtr2.verizon-gni.net (130.81.199.4)  34.229 ms
> 8.743 ms  8.878 ms
>  5  so-8-0-0-0.lcc1-res-bb-rtr1-re1.verizon-gni.net (130.81.17.3)
> 15.402 ms  13.008 ms  14.932 ms
>  6  0.ae2.br1.iad8.alter.net (152.63.32.158)  13.325 ms  13.245 ms  13.802
> ms
>  7  204.255.169.218 (204.255.169.218)  14.820 ms  14.232 ms  13.491 ms
>  8  lap-brdr-03.inet.qwest.net (67.14.22.78)  90.170 ms  92.273 ms
145.887
> ms
>  9  63.146.26.70 (63.146.26.70)  92.482 ms  92.287 ms  94.000 ms
> 10  sl-crs1-kc-0-0-0-2.sprintlink.net (144.232.18.112)  58.135 ms
> 58.520 ms  58.055 ms
> 11  otejbb203.kddnet.ad.jp (203.181.100.17)  205.844 ms
>     otejbb204.kddnet.ad.jp (203.181.100.25)  189.929 ms
>     otejbb203.kddnet.ad.jp (203.181.100.17)  204.846 ms
> 12  sl-crs1-oro-0-1-5-0.sprintlink.net (144.232.25.77)  87.229 ms
>     sl-crs1-oro-0-3-3-0.sprintlink.net (144.232.25.207)  88.796 ms  88.717
> ms
> 13  124.215.199.122 (124.215.199.122)  193.584 ms  202.208 ms  192.989 ms
> 14  * * *
>
> Same IP from different network:
>
> traceroute to 106.187.34.33 (106.187.34.33), 30 hops max, 60 byte packets
>
>  6  ae-8-8.ebr2.Washington1.Level3.net (4.69.134.105)  2.230 ms  1.847
> ms  1.938 ms
>  7  ae-92-92.csw4.Washington1.Level3.net (4.69.134.158)  2.010 ms
> 1.985 ms ae-62-62.csw1.Washington1.Level3.net (4.69.134.146)  1.942 ms
>  8  ae-94-94.ebr4.Washington1.Level3.net (4.69.134.189)  12.515 ms
> ae-74-74.ebr4.Washington1.Level3.net (4.69.134.181)  12.519 ms  12.507
> ms
>  9  ae-4-4.ebr3.LosAngeles1.Level3.net (4.69.132.81)  65.957 ms
> 65.958 ms  66.056 ms
> 10  ae-83-83.csw3.LosAngeles1.Level3.net (4.69.137.42)  66.063 ms
> ae-93-93.csw4.LosAngeles1.Level3.net (4.69.137.46)  65.985 ms
> ae-63-63.csw1.LosAngeles1.Level3.net (4.69.137.34)  66.026 ms
> 11  ae-3-80.edge2.LosAngeles9.Level3.net (4.69.144.143)  66.162 ms
> 66.160 ms  66.238 ms
> 12  KDDI-AMERIC.edge2.LosAngeles9.Level3.net (4.53.228.14)  193.317 ms
>  193.447 ms  193.305 ms
> 13  lajbb001.kddnet.ad.jp (59.128.2.101)  101.544 ms  101.543 ms
> lajbb002.kddnet.ad.jp (59.128.2.185)  66.563 ms
> 14  otejbb203.kddnet.ad.jp (203.181.100.13)  164.217 ms  164.221 ms
164.330
> ms
> 15  cm-fcu203.kddnet.ad.jp (124.215.194.164)  180.350 ms
> cm-fcu203.kddnet.ad.jp (124.215.194.180)  172.779 ms
> cm-fcu203.kddnet.ad.jp (124.215.194.164)  185.824 ms
> 16  124.215.199.122 (124.215.199.122)  175.703 ms  175.700 ms  168.268 ms
> 17  li377-33.members.linode.com (106.187.34.33)  174.381 ms  174.383
> ms  174.368 ms
>
> The last hop is KDDI, but things work from via Level3 and not sprint.
> Linode blames Verizon, but I'm not seeing how it's them.
>
> Any ideas?
>
>




More information about the NANOG mailing list