[56755] in North American Network Operators' Group
Re: route filtering in large networks
daemon@ATHENA.MIT.EDU (E.B. Dreger)
Thu Mar 13 11:14:12 2003
Date: Thu, 13 Mar 2003 16:13:39 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: nanog@merit.edu
In-Reply-To: <20030313034721.GY8839@overlord.e-gerbil.net>
Errors-To: owner-nanog-outgoing@merit.edu
RAS> Date: Wed, 12 Mar 2003 22:47:21 -0500
RAS> From: Richard A Steenbergen
RAS> That said, I'm sure we would all LOVE a protocol which can
RAS> dynamically supply routes for various route and packet
RAS> filter operations throughout a large network.
If it weren't so dangerous, I'd suggest a "hyperweight" that
overrides prefix length. Hear bogons from route server, set
hyperweight high enough to override longer prefixes, and set the
next hop to null interface.
Things like this return us to separation of routing and
forwarding: Should BGP munching and fancy route-fu be performed
on a flexible, customizable *ix box, then fed to the actual
forwarding machines?
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@brics.com>, or you are likely to
be blocked.
