Maria,
On Tue, 28 Jan 2020 at 02:03, Robert Blayzor wrote:
> 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: attribut
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
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
On January 27, 2020 8:52:38 PM GMT+01:00, Robert Blayzor
wrote:
>After som
After some digging through the BIRD 2.0 manual, I may have found my own
answer, but first time working with BIRD 2.0 so not sure if this is
valid
Maybe something like:
if (net.type = NET_IP4) && (net.len = 32) then {
...
} else if (net.type = NET_IP6) && (net.len >
On Mon, 27 Jan 2020 at 20:27, Robert Blayzor wrote:
> Migrating from BIRD 1.6 to 2.0 and I would like to consolidate some BGP
> filters and use them for IPv4 or IPv6 sessions
>
> What is the best way to enumerate if a net is IPv4 or IPv6 if you wanted
> to make a if/then/else on.. ie:
>
> filt
Migrating from BIRD 1.6 to 2.0 and I would like to consolidate some BGP
filters and use them for IPv4 or IPv6 sessions
What is the best way to enumerate if a net is IPv4 or IPv6 if you wanted
to make a if/then/else on.. ie:
filter MY_FILTER {
if ((MYAS, 888) ~ bgp_community) then {
