Re: determining ipv4 or ipv6 net in filter

Excellent. I like the custom attributes for route tagging. However in the docs I cannot find what "types" are supported for custom attributes. For example: attribute string foo; Results in an unsupported type, yet: attribute int foo; works... On 1/27/20 5:37 PM, Maria Matějka wrote:

Yes. This version should work.

BTW, I suggest using custom attributes instead of communities for all the route tagging. They work the same way as other attributes and all protocols (except for Pipe) ignore them.

Maria