[c-nsp] RPL question

[Adam Vitkovsky]

Hi,
My assumption was that if there's a single community attached than it has to
start and end with 1234:1234 
So I thought it's something easy as:

community-set cs-test
  ios-regex '^1234\:1234$'
end-set

route-policy rp-test_in
  if community matches-every test then
    pass
  else
    drop
  endif
end-policy
!

However it appears that the communities attached to a route are not part of
a community-list of some sort (like it is with AS numbers), thus are
evaluated separately. 
And since I cannot use "[]" with community-set to match on a range of chars
in order to exclude anything else except "1234:1234" I am clueless. 



adam

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of MKS
Sent: Wednesday, April 24, 2013 11:56 AM
To: cisco-nsp
Subject: [c-nsp] RPL question

Hi list,  I'm new to RPL and I have a simple question;)

I would like to match on a one and only one community, so if a route has
additional communities to 1234:1234 then it shouldn't match.

    1.1.1.0 (metric 10) from 2.2.2.2
      Origin IGP, metric 0, localpref 100, valid, internal, best, group-best
      Received Path ID 0, Local Path ID 1, version 32
      Community: 1234:1234


    1.1.2.0 (metric 10) from 2.2.2.2
      Origin IGP, metric 0, localpref 100, valid, internal, best, group-best
      Received Path ID 0, Local Path ID 1, version 32
      Community: 1234:1234 2345:2345

so the RPL code should match on 1.1.1.0 and not 1.1.2.0 (or any other route
which has additional communities to 1234:1234).

I reckon that this should be fairly simple, but I can't find a way to do
this... silly me

Regards
MKS
_______________________________________________
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/