[117774] in North American Network Operators' Group
Re: Cogent leaking /32s?
daemon@ATHENA.MIT.EDU (Michael Hallgren)
Fri Oct 2 16:38:05 2009
From: Michael Hallgren <m.hallgren@free.fr>
To: "Alex H. Ryu" <r.hyunseog@ieee.org>
In-Reply-To: <4AC623C3.7090408@ieee.org>
Date: Fri, 02 Oct 2009 22:37:32 +0200
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--=-RHAVw1A7Cspa4NoesiYu
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Le vendredi 02 octobre 2009 =C3=A0 11:01 -0500, Alex H. Ryu a =C3=A9crit :
> If there is DDoS attack going on from/to specific /32, sometimes they do
> that to avoid too much overload for the network.
> Cogent should give the answer for what's going on.
Generally, such is kept in-AS (null-routing or routing to some other
sink of choice).
mh
>=20
> Alex
>=20
> Zak Thompson wrote:
> > We had a problem with cogent about a year ago. Somehow.. cymru was
> > announcing a /32 of ours and black holing it for whatever reason. It
> > was removed but wasn't happy that cogent was allowing cymru to do this
> > sort of action. To this date we do not have a valid reason from cogent
> > on why they allowed this to happen.
> >
> > Cheers,
> > Zak Thompson
> >
> >
> >
> > -----Original Message-----
> > From: ML [mailto:ml@kenweb.org]=20
> > Sent: Friday, October 02, 2009 7:23 AM
> > To: nanog@nanog.org
> > Subject: Cogent leaking /32s?
> >
> > I received an alert from Cyclops telling me a probe in AS513 had seen a=
=20
> > /32 that I announce to Cogent for one of our BGP sessions.
> >
> > Did anyone else see this?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > =20
>=20
>=20
--=20
michael hallgren, mh2198-ripe
--=-RHAVw1A7Cspa4NoesiYu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Ceci est une partie de message
=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkrGZIYACgkQZNZ/rrgsqadedQCdFyLNXCOkiXDIHUM4cMleKsPw
JnMAni0sPTKm5GWrxhPUHnyf2UKpFiiF
=mY/l
-----END PGP SIGNATURE-----
--=-RHAVw1A7Cspa4NoesiYu--