Hi, On Mon, Nov 22, 2021 at 10:02:56AM +0100, Sascha E. Pollok wrote: > I have actually tried to specify a custom community as a parameter and match > against that > in the route-policy's condition but that didn't work with match-any > ($community). The > parser wouldn't let me commit that. > > Do the RPL variables only work for numbers? Then I wouldnt also assume that > something like > match-any (12345:$var) would work?
Haven't tried, but that would be extremely annoying.
The use case I have in mind is using large communities to control
per-peer-AS exports, as in:
<myasn>:0:<yourasn> --> "do not announce to $yourasn"
<myasn>:1:<yourasn> --> "prepend to $yourasn"
and if that cannot be done by RPL parameters, this idea already looks
like "meh, nah, not worth the effort of having hundreds of nearly
identical policies"
route-policy export-to-9999
if match-any community in ( 5539:0:9999 )
then
drop
fi
apply decix-generic
end-policy
*scratch head*
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany [email protected]
signature.asc
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
