|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Bogon list
I agree with Joe on this. At one time we were filtering 198.32/16 from our peers but ran into things like ep.net (198.32.6.31) breaking. We now only filter on IXP blocks for which we participate. While on the subject of IXP blocks, we also ended up redistributing the IXP blocks and sending them to our BGP customers (who do not receive a default) so that traceroutes and such from Looking Glasses do not break. They can then choose to filter them as they wish. -Dave Joe Abley wrote: > > On Tuesday, June 4, 2002, at 12:48 , Barry Raveendran Greene wrote: > > >> Then we come to the extra bogons like exchange point allocations. Can't > >> forget them. :) > > > > I've never heard anyone refer to the IXP allocations as "bogons." Plus, > > I've > > not heard of anyone filtering the IXP prefixes on their ingress peering > > filters. Egress peering filters - yes. > > Depending on your internal routing policy, it may well be important not > to learn routes to exchange points to which you connect. > > A straightforward example is when people accidentally propagate the > prefixes 195.66.224.0/24 and 195.66.225.0/24. Interfaces on the LINX > exchange fabric are currently numbered within 195.66.224.0/23, so if my > LINX router learns the longer prefix routes from somewhere else, my EBGP > sessions across the exchange get hijacked. Without the prefix length > aspect the effect is less obviously serious, but it can still cause > issues. > > Subnets numbering interfaces on exchange point subnets, for exchange > points at which I participate, can hence generally be considered > bogonish by me. For exchange points at which I do not participate this > need not be the case. The list of EP-derived bogons is, following this > logic, operator-specific. > > Joe
|