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
> 22.214.171.124/22 <- This belongs to us.
> 126.96.36.199/22 KNS Techno Integrators Pvt. Ltd.
> 188.8.131.52/24 hydrocontrol S.C.R.L.
> 184.108.40.206/24 TRAPIL - Societe des Transports Petroliers par Pipeline
> Where do we complain to get this fixed.
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...
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the NANOG