On Wed, Mar 27, 2019 at 09:36:20PM +, Graham Johnston wrote:
> This afternoon at around 12:17 central time today we began learning
> the subnet for the Equinix IX in Chicago via a transit provider; we
> are on the IX as well. The subnet in question is 208.115.136.0/23.
> Using stat.ripe.net I
On Thu, Mar 28, 2019 at 02:59:43PM +0100, Niels Bakker wrote:
> * christopher.morrell.na...@gmail.com (Christopher Morrell) [Thu 28 Mar 2019,
> 14:35 CET]:
> > I've been bit by this in the past at two different exchanges. I too
> > have a policy applied to deny IXP LANs from upstreams and peers.
* christopher.morrell.na...@gmail.com (Christopher Morrell) [Thu 28 Mar 2019,
14:35 CET]:
I've been bit by this in the past at two different exchanges. I too
have a policy applied to deny IXP LANs from upstreams and peers. It
would be nice if there was a list of all IXP LANs somewhere that
I've been bit by this in the past at two different exchanges. I too have a
policy applied to deny IXP LANs from upstreams and peers. It would be nice
if there was a list of all IXP LANs somewhere that we could generically add
to all upstream and peers.
On Thu, Mar 28, 2019 at 9:11 AM Eric
I have a policy applied to my upstreams and peers to deny the IXP's LANs
were connected to. I don't think of any reason to learn these routes from
someone else's network.
On Wed, Mar 27, 2019 at 7:44 PM Cummings, Chris wrote:
> Not too sure about your topology, but I’ve had something similar
Not too sure about your topology, but I’ve had something similar bite me, so we
typically put a prefix list inbound to deny receiving our internal prefixes
from our peers. This probably doesn’t work as well if your network is less
“eyeballish” than ours, however.
/chris
On Wed, Mar 27, 2019
@nanog.org
Subject: Re: Advertisement of Equinix Chicago IX Subnet
CAUTION: This email is from an external source. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
Graham Johnston wrote on 27/03/2019 21:36:
> What am I doing that isn't b
Graham Johnston wrote on 27/03/2019 21:36:
What am I doing that isn’t best practices that would have prevented this?
you're setting the next-hop of the prefixes learned at the IXP to be
your own IP address from the IXP subnet (i.e. 208.115.136.0/23).
When your routers learn this address
This afternoon at around 12:17 central time today we began learning the subnet
for the Equinix IX in Chicago via a transit provider; we are on the IX as well.
The subnet in question is 208.115.136.0/23. Using stat.ripe.net I can see that
this subnet is also being learned by others, see the snip
9 matches
Mail list logo
