[nsp] Typical Prefix filters - greater than /24's dropped?

[Vincent De Keyzer]

Not sure this test is really relevant, but here is what I see on my bi-homed
BGP network:

alfonso>sh ip bgp | i /2[5-9]
*>i62.72.119.192/26 a.b.c.d                100      0 8220 i
*>i62.72.120.192/26 a.b.c.d                100      0 8220 i
*>i194.45.237.0/27  a.b.c.d                100      0 8220 i
*>i194.45.237.192/27
*>i194.153.215.0/25 a.b.c.d                100      0 8220 i
*>i195.77.113.0/25  a.b.c.d                100      0 8220 20566 i
*>i212.0.113.128/26 a.b.c.d                100      0 8220 ?
alfonso>

alfonso>sh ip bgp | i /3[0-2]
alfonso>

So only one of my two transit providers seems to pass me on routes with a
longer prefix than /24, and all but one of the routes are originated in his
own AS (the last one being probably originated by one of its customers).

So I imagine that yes, many transit providers do filter those.

Vincent

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Sam Stickland
> Sent: jeudi 20 novembre 2003 11:59
> To: Cisco Nsp
> Subject: [nsp] Typical Prefix filters - greater than /24's dropped?
> 
> 
> Hi,
> 
> I'm trying to get a feel for the sort of prefix filters that 
> are typically in use on the backbones and transit providers. 
> Are prefixes longer than /24's typically filtered out?
> 
> Sam
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco> -nsp
> archive at 
> http://puck.nether.net/pipermail/cisco-nsp/
>