[38245] in North American Network Operators' Group

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

Re: engineering --> ddos and flooding

daemon@ATHENA.MIT.EDU (Geoff Zinderdine)
Fri Jun 1 14:56:37 2001

Message-ID: <001901c0eacc$94995a80$0c64a8c0@aegis>
Reply-To: "Geoff Zinderdine" <geoff.zinderdine@mts.mb.ca>
From: "Geoff Zinderdine" <geoffz@mts.net>
To: <lucifer@lightbearer.com>
Cc: <nanog@merit.edu>
Date: Fri, 1 Jun 2001 13:56:24 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu


> Including the BGP session, I would think, thus causing it to reset and
> drop the route, sending all the traffic back to the primary, which
unfloods
> the smaller link, which re-advertises, which...
>
> Flappage, anyone?

Why not just advertise the host route with an unreachable next hop from your
main peering session?

Best regards,

====================
Geoff Zinderdine
CCNP CCA MCP
MTS Communications Inc.
====================
"I'd rather route than switch."





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