Probably the real question is what you wish to accomplish with communities - do you want to use them just for marking "interesting info" or do you want to use them for filtering? You can also take them to the point of allowing your downstream BGP customers to influence their traffic through your network...
Communities are very cool in my opinion - but you need a good "plan of attack" for utilizing them to save yourself headaches..;) Paul -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Eric Van Tol Sent: September-04-09 7:53 AM To: [email protected] Subject: [j-nsp] Community RegEx Hi all, I'm having some trouble identifying the proper way to define some communities. I've read this: http://www.juniper.net/techpubs/software/junos/junos94/swconfig-policy/confi guring-the-community-attribute-using-unix-regular-expressions.html but still have questions. Let's say I have three communities 1234:100, 1234:250, and 1234:375. According to the docs, it appears they should be defined as such: ^1234:((100)|(250)|(375))$ However, I have several community definitions that seem to work in the following format: ^1234:(100)|(250)|(375)$ I would think that the first one is the way to go, but it appears that both work. Is one a "more righter" way of defining these communities? -evt _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
