On Thursday, March 08, 2012 12:30:16 PM Reuben Farrelly wrote: > If I have a route-map that parses IPv6 routes, but does > not match any IPv6 routes (no match ipv6 ... defined > anywhere in any of the route-map sequence entries) then > it matches on the first _IPv4_ route map entry and sets > the community of that IPv6 route to the IPv4 match > instead. That's the bug :)
Ah, now I understand. I believe this would be expected behaviour, given that you're applying the policy on an IPv6 session as well. I can't confirm this as we run a different setup, but it would theoretically make sense to be expected. Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
