On Wed, May 05, 2010 at 04:24:04PM +0100, Alex wrote: > Hello there, > Below regex works too: > > community inbound-xxxx members "(11666:2000)|(11666:2002)"
The downside to this is you can't add communities using the same named definition, since regexp can only be used to match. If you have two seperate non-regexp names, you could do "community add blah" as well as "community from blah" using the same blah. Of course in a real/complex network where you're encoding more than a single piece of data (relationship type), you probably want to have two versions. For example you might have a tag_customer 11666:4123 where the initial 4 == customer and the other data == continent, region, or pop codes, and then have a match_customer "^11666:4...$" for matching all customer routes regardless of location tags. I highly recommend using distinct names like tag_ and match_ to keep the two seperate, it will make life much easier in the future. :) -- Richard A Steenbergen <r...@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp