[174201] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Prefix hijacking, how to prevent and fix currently

daemon@ATHENA.MIT.EDU (Karsten Thomann)
Fri Aug 29 05:36:41 2014

X-Original-To: nanog@nanog.org
Date: Fri, 29 Aug 2014 11:34:20 +0200
From: Karsten Thomann <karsten_thomann@linfre.de>
To: Randy Bush <randy@psg.com>
In-Reply-To: <m2egvz8x6r.wl%randy@psg.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org

Am 29.08.2014 11:25, schrieb Randy Bush:
>> Loose mode would drop failing routes, iff there is covering (i.e. less
>> specific is ok) route already in RIB.
> isn't that exactly the hole punching attack?
>
> randy
No, as the the more specific route is signed and is preferred (longest 
match routing) against the less specific hijacked route

home help back first fref pref prev next nref lref last post