Re: [nsp] Extended community-lists & filtering of customer communities

From: Alex Bligh (amb@gxn.net)
Date: Fri Aug 21 1998 - 19:06:08 EDT


Wayne,
>
> > Bearing in mind there may be more than one community attribute present,
> > I think the correct way to do this is (and testing *seems* to work)
> > as follows. Would someone who has used these things in anger care
> > to check my logic?
>
> It doesn't have to be that hard.
>
> ip community-list 109 permit 4444:1[0-9]*

Nope. My tests would indicate that would match (say)
a route with 4444:1234 and 4444:5678 on. I don't want it in if
it has 4444:anything unless it's 4444:1000 to 4444:1999

This is what makes the problem difficult, and why I think you
have to have a list which matches anything *bad* and then rejects
it.

> or if you want tem exactly 4 digits..
>
> ip community-list 109 permit 4444:1...

I think you need the underscores, or that would match
4444:1 4444:23456

-- 
Alex Bligh
GX Networks (formerly Xara Networks)



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:13 EDT