[174193] in North American Network Operators' Group
Re: Prefix hijacking, how to prevent and fix currently
daemon@ATHENA.MIT.EDU (Fred Baker (fred))
Thu Aug 28 23:27:36 2014
X-Original-To: nanog@nanog.org
From: "Fred Baker (fred)" <fred@cisco.com>
To: Tarun Dua <lists@tarundua.net>
Date: Fri, 29 Aug 2014 03:24:28 +0000
In-Reply-To: <CAAjbWEr_o+yQY1T72JMvJ_Nw2Eu2L7=TzZ0dc33mhodo5JB=yw@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--Apple-Mail=_6D9B4A59-F22A-44C2-BC69-BD93EE94BA9E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On Aug 28, 2014, at 9:55 AM, Tarun Dua <lists@tarundua.net> wrote:
> AS Number 43239
> AS Name SPETSENERGO-AS SpetsEnergo Ltd.
>=20
> Has started hijacking our IPv4 prefix, while this prefix was NOT in
> production, it worries us that it was this easy for someone to hijack
> it.
>=20
> http://bgp.he.net/AS43239#_prefixes
>=20
> 103.20.212.0/22 <- This belongs to us.
>=20
> 103.238.232.0/22 KNS Techno Integrators Pvt. Ltd.
> 193.43.33.0/24 hydrocontrol S.C.R.L.
> 193.56.146.0/24 TRAPIL - Societe des Transports Petroliers par =
Pipeline
>=20
> Where do we complain to get this fixed.
>=20
> -Tarun
> AS132420
Do you implement RPKI? Are providers that neighbor with them =
implementing RPKI?
If not, complain to the folks not indicating RPKI and therefore =
accepting a hijacked prefix. Including yourself.
--Apple-Mail=_6D9B4A59-F22A-44C2-BC69-BD93EE94BA9E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iD8DBQFT//JlbjEdbHIsm0MRAur6AJ9Ce3drpeqPc4jWR4iIwCb89WGYIACfbuYi
DHA0jRepMkoYOYEMylIob1Y=
=PXYO
-----END PGP SIGNATURE-----
--Apple-Mail=_6D9B4A59-F22A-44C2-BC69-BD93EE94BA9E--
