[8860] in North American Network Operators' Group

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

Re: seeing the trees in the forest of confusion

daemon@ATHENA.MIT.EDU (Avi Freedman)
Sat Apr 26 14:53:27 1997

From: Avi Freedman <freedman@netaxs.com>
To: junkins@nwnet.net (Doug Junkins)
Date: Sat, 26 Apr 1997 14:44:57 -0400 (EDT)
Cc: amb@xara.net, nanog@merit.edu
In-Reply-To: <Pine.GSO.3.96.970426105444.25693O-100000@cypress.nwnet.net> from "Doug Junkins" at Apr 26, 97 11:23:19 am

> I agree that there appears to be some underlying problem with the BGP code
> on the backbone that is delaying route withdrawals beyond a reasonable
> time.  We ran into a similar problem Wednesday night where one of our
> customers started advertising more specifics for our network blocks to
> another transit provider (who does not filter customer routes). After
> shutting down the customer's BGP peering, the bogus routes were still in
> the table an hour later at which time we started advertising our own more
> specifics to restore service to our other customers -- this lead to our
> unfortunate position in Thursday's CIDR report.

Were they in as dampened; history; or just in as if they were in and had
not flapped?

Dampening of more specific bogus announcements is a problem I'd like to
see addressed, since the more general (and correct) routes won't be used
if more specifics are dampened.

> - Doug

Avi


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