Prefix hijacking, how to prevent and fix currently

Fred Baker (fred) fred at cisco.com
Fri Aug 29 03:24:28 UTC 2014


On Aug 28, 2014, at 9:55 AM, Tarun Dua <lists at tarundua.net> wrote:

> AS Number 43239
> AS Name SPETSENERGO-AS SpetsEnergo Ltd.
> 
> 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.
> 
> http://bgp.he.net/AS43239#_prefixes
> 
> 103.20.212.0/22 <- This belongs to us.
> 
> 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
> 
> Where do we complain to get this fixed.
> 
> -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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20140829/0b3b1d0f/attachment.pgp>


More information about the NANOG mailing list