Prefix hijacking, how to prevent and fix currently
marka at isc.org
Fri Aug 29 03:28:38 UTC 2014
See "whois -r AS43239".
The long term solution is to deploy RPKI and only use
transits which use RPKI. No RPKI support => no business.
Additionally make RPKI a peering requirement.
In message <CAAjbWEr_o+yQY1T72JMvJ_Nw2Eu2L7=TzZ0dc33mhodo5JB=yw at mail.gmail.com>
, Tarun Dua writes:
> 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
> 188.8.131.52/22 <- This belongs to us.
> 184.108.40.206/22 KNS Techno Integrators Pvt. Ltd.
> 220.127.116.11/24 hydrocontrol S.C.R.L.
> 18.104.22.168/24 TRAPIL - Societe des Transports Petroliers par Pipeline
> Where do we complain to get this fixed.
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka at isc.org
More information about the NANOG