[174203] 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:45:25 2014

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

Am 29.08.2014 11:39, 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?
>> No, as the the more specific route is signed and is preferred (longest
>> match routing) against the less specific hijacked route
> clearly i am missing something.  got a write-up?
>
> randy
sorry my mistake, you're right

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