to
load, and some just don't load at all.
Date: Mon, 12 Dec 2011 09:55:40 +0900
From: ra...@psg.com
To: nanog@nanog.org
Subject: Re: Inaccessible network from Verizon, accessible
elsewhere.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377
...@ox.com
To: maill...@webjogger.net; nanog@nanog.org
Date: Mon, 12 Dec 2011 08:44:56 -0500
Subject: RE: Inaccessible network from Verizon, accessible elsewhere.
DSLReports Verizon forum reports routing issues in Westchester, Rockland and
Nassau. I tried a few traceroutes this morning. Some went
:02 AM
To: nanog group
Subject: RE: Inaccessible network from Verizon, accessible elsewhere.
Yes I am in Rockland. I failed to mentioned that I was having issues with
consumer FIOS.
Is anyone with Verizon on this list? This morning www.cisco.com and
www.nfl.com works now.
They didn't last night
On 12/10/11, NetSecGuy netsec...@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
I should have included reverse traces to begin with. No firewall on VPS.
Trace from the VPS to a router close to me.
traceroute to 130.81.199.4 (130.81.199.4), 64 hops max, 40 byte packets
1 106.187.33.2 (106.187.33.2) 1 ms 0 ms 0 ms
2 124.215.199.121 (124.215.199.121) 6 ms 1 ms 13 ms
I believe 130.81 is blocked. Traceroute to your gateway address.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
NetSecGuy netsec...@gmail.com wrote:
I should have included reverse traces to begin with. No firewall on VPS.
Trace from the VPS to a router close to me.
On Sat, Dec 10, 2011 at 11:49 AM, NetSecGuy netsec...@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.
The host, 106.187.34.33, is behind the gateway 106.187.34.1:
From FIOS to 106.187.34.1
network from Verizon, accessible elsewhere.
On 12/10/11, NetSecGuy netsec...@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
* * ^C
C:\WINDOWS\system32
E = 4:32 Cheers!!!
-Original Message-
From: Lee [mailto:ler...@gmail.com]
Sent: Sunday, December 11, 2011 6:44 AM
To: NetSecGuy
Cc: nanog@nanog.org
Subject: Re: Inaccessible network from Verizon, accessible elsewhere.
On 12/10/11, NetSecGuy netsec...@gmail.com
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.471 ms 0.725 ms 0.555 ms
2 tokyo10-f03.flets.2iij.net (210.149.34.72) 7.241 ms 6.651 ms 6.939 ms
3
: Inaccessible network from Verizon, accessible elsewhere.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.471 ms 0.725 ms 0.555 ms
2 tokyo10-f03.flets.2iij.net (210.149.34.72) 7.241
network from Verizon, accessible elsewhere.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte
packets
1 192.168.0.1 (192.168.0.1) 1.471 ms 0.725 ms 0.555 ms
2 tokyo10-f03.flets.2iij.net (210.149.34.72) 7.241 ms 6.651
On Sun, Dec 11, 2011 at 3:11 PM, Joseph Snyder joseph.sny...@gmail.com wrote:
I believe 130.81 is blocked. Traceroute to your gateway address.
portions (at least) of that are 19262's loopback/ptp space, they
block/rate-limit toward that at their edge.
.
Date: Mon, 12 Dec 2011 09:55:40 +0900
From: ra...@psg.com
To: nanog@nanog.org
Subject: Re: Inaccessible network from Verizon, accessible elsewhere.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte
packets
1
To: nanog@nanog.org
Subject: Re: Inaccessible network from Verizon, accessible elsewhere.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte
packets
1 192.168.0.1 (192.168.0.1) 1.471 ms 0.725 ms 0.555 ms
2 tokyo10-f03
To: nanog@nanog.org
Subject: Re: Inaccessible network from Verizon, accessible elsewhere.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte
packets
1 192.168.0.1 (192.168.0.1) 1.471 ms 0.725 ms 0.555 ms
2 tokyo10-f03
...@psg.com
To: nanog@nanog.org
Subject: Re: Inaccessible network from Verizon, accessible elsewhere.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.471 ms 0.725 ms 0.555 ms
2 tokyo10
On Mon, Dec 12, 2011 at 1:26 AM, Adam Greene maill...@webjogger.net wrote:
130.81.107.228
hrm... LCR == lata-core-router... something fairly close to you, like
2 router-hops from your first L3 hop... sounds like someone ought to
call the vz customer service line and ask for a fix :)
Yep, tried that. Connected with a lower level tech who would not escalate.
Anyone know a Verizon NOC direct contact #?
On 12/12/2011 2:17 AM, Christopher Morrow wrote:
On Mon, Dec 12, 2011 at 1:26 AM, Adam Greenemaill...@webjogger.net wrote:
130.81.107.228
hrm... LCR == lata-core-router...
Do you have a firewall running on the Linode VPS? Any chance something
like fail2ban blocked your IP for too many invalid logins? Are you able
to ping your FIOS IP from the VPS? Try doing a traceroute on the VPS to
your FIOS IP. Perhaps there is some issue getting back to you. Based on
the
Am 10.12.2011 um 20:49 schrieb NetSecGuy:
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
Disable your firewall and run TCPDump on your host when you try to ping
it.
Does the ICMP packet get to your host?
On Sat, Dec 10, 2011 at 4:11 PM, Stefan Bethke s...@lassitu.de wrote:
Am 10.12.2011 um 20:49 schrieb NetSecGuy:
This does not work from FIOS:
traceroute to 106.187.34.33
22 matches
Mail list logo
