[j-nsp] Community matching policy

[Krasimir Avramski]

A match 100:100
B match 101:101
Your TEST1 term match on !A OR !B <=> !(A AND B), so it effectively rejects
every route that has NO communities 100:100 AND 101:101 (at the same time)
Your target is to accept A OR B, so you can first match and accept on these
communities (TEST1 OR TEST2 defined without invert-match) and then reject
everything else.

Best Regards,
Krasi


On 31 March 2014 12:10, Andrew Khan <good1uzi at outlook.com> wrote:

> Hi -
>
> Let's say I want to reject everything except the following communities:
>
> Either 100:100
> OR 101:101
> OR both 100:100 101:100
>
> Tried to setup something:
>
> [edit policy-options]
> policy-statement TEST {
>       term TEST1 {
>           from community [ TEST1 TEST2 ]; ///////Is not it logical OR, and
> matching everything except what I want because of invert-match//////
>            then reject;
>        }
>       term TEST2 {
>      then accept;   //// And then this should accept what I wanted /////
>    }
> }
>
> [edit policy-options]
>    community TEST1 {
>       invert-match;
>        members 100:100;
>    }
>    community TEST2 {
>        invert-match;
>        members 101:101;
>    }
>
> However it is rejecting everything. Any thoughts what I'm missing here or
> perhaps the approach is not correct.
>
> Thanks in advance.
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>