[174835] in North American Network Operators' Group
Re: cogent update suppression, and routing loops
daemon@ATHENA.MIT.EDU (Brandon Ewing)
Fri Oct 3 13:56:30 2014
X-Original-To: nanog@nanog.org
Date: Fri, 3 Oct 2014 12:56:22 -0500
From: Brandon Ewing <nicotine@warningg.com>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <CAK_-TSZuQ5Sng5J1rot_=pDLfajGUyNJVDRjzJo9AzaMPhxH4w@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
--f2QGlHpHGjS2mn6Y
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Oct 02, 2014 at 09:03:15AM -0700, ryanL wrote:
> (who peers with cogent), and then pull the /24 some time later, that coge=
nt
> holds onto the /24 and then bounces packets around in their network a bun=
ch
> of times for upwards of 8-10 minutes until they finally yank it. this
> effectively blackholes traffic to my /24 for anyone that is using a path
> thru cogent.
Maybe running into some non-standard BGP Advertisement intervals inside
Cogent's network? Might be running a lot of sub-ASes inside the
confederation, and having to wait multiple advertisement intervals for full
propagation.
https://routingfreak.wordpress.com/tag/minimum-route-advertisement-interval/
--=20
Brandon Ewing (nicotine@warningg.com)
--f2QGlHpHGjS2mn6Y
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFULuNG7UrjtO3ToYoRAiB/AJ96rVG5f8tNWJC4m19T79DNkflflACcDW4l
3VxTQghTNdTysEuvduy4W4Y=
=KD1L
-----END PGP SIGNATURE-----
--f2QGlHpHGjS2mn6Y--
