[28897] in North American Network Operators' Group
Re: That pesky AS path corruption bug...
daemon@ATHENA.MIT.EDU (Jeff Haas)
Tue May 23 13:21:02 2000
Date: Tue, 23 May 2000 13:18:48 -0400
From: Jeff Haas <jeffhaas@merit.edu>
To: Blaine Christian <blaine@inbound.blaines.net>
Cc: nanog@merit.edu
Message-ID: <20000523131847.B24730@vorlon.merit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.4.10.10005231234410.19459-100000@inbound.blaines.net>; from Blaine Christian on Tue, May 23, 2000 at 12:40:00PM -0400
Errors-To: owner-nanog-outgoing@merit.edu
On Tue, May 23, 2000 at 12:40:00PM -0400, Blaine Christian wrote:
> Since the corrupted AS-path does not include the AS that the route is
> coming from (at least in the corruption that I saw) it seems to me that a
> simple solution for all is to filter on AS i.e. only allow routes that
> have the AS of your EBGP neighbor prepended to them.
Just a note that this breaks route servers. Caveat programmer.
And how do you mean "corrupted"? If the packet is syntacically
invalid, its perfectly legal to send a NOTIFY and drop the
session. GateD did this to Proteon for years. :-)
> Blaine
--
Jeffrey Haas - Merit RSng project - jeffhaas@merit.edu
