The below information is taken from an internal router directly connected
to 701
==
CORE-R1#show ip bgp 200.10.150.169
BGP routing table entry for 200.10.150.0/24, version 46722748
Paths: (1 available, best #1, table default)
Not
I can see the Google IP space (64.71.240.0/20) from Verizon/AS701, but not
from Rogers/AS812 in Toronto. I've done a few other test traceroutes
through Rogers to verify that they didn't filter UDP/ICMP. At this point
nothing would surprise me from Rogers.
AS701
=
TOR2-CORE-R1#traceroute
812
205.205.23.121 from 205.205.23.121 (137.39.8.42)
Origin IGP, localpref 100, valid, external, best
TOR2-CORE-R1#
Thanks,
- Mike
On Wed, Jul 10, 2013 at 11:28 AM, Mike Jackson m...@routed.ca wrote:
I can see the Google IP space (64.71.240.0/20) from Verizon/AS701, but
not from
to www3.l.google.com (66.185.84.30)
Cheers,
- Mike
On Wed, Jul 10, 2013 at 2:18 PM, Christopher Morrow morrowc.li...@gmail.com
wrote:
On Wed, Jul 10, 2013 at 12:20 PM, Mike Jackson m...@routed.ca wrote:
I just realized that it's not Google IP space (74.125.0.0/16), Rogers is
hijacking
:
On Wed, Jul 10, 2013 at 12:20 PM, Mike Jackson m...@routed.ca wrote:
I just realized that it's not Google IP space (74.125.0.0/16), Rogers
is
hijacking the DNS and resolving www.google.com to space within
64.71.240.0/20 which is Rogers IP space! (note the name server set as
8.8.8.8)
so
5 matches
Mail list logo