Re: Defines for mixed IPv6/IPv4

2024-01-23 Thread Jeroen Massar via Bird-users
> On 23 Jan 2024, at 14:13, Nico Schottelius via Bird-users > wrote: > > > Hello bird users, > > I am wondering how you handle matching both IPv6 and IPv4 prefixes > efficiently. > > We have tons of blocks in our config like these: Generate the configs. Especially when doing IRR filterin

Re: Defines for mixed IPv6/IPv4

2024-01-23 Thread Douglas Fischer
That is almost the same methodology I used in other engines(RPL and XPL). But, after having some issues on performance of control plane, I needed to change a bit... Splitting the IFs of v4 and v6, and then inside that IF testing for the Prefix-list. Doing that recursion on IFs, reduced a bit the im

Re: Defines for mixed IPv6/IPv4

2024-01-23 Thread Luiz Amaral
Hello Nico, I make separate defines per family (like you did) and then in my filters I just use:     if (net.type = NET_IP4 && ! (net ~ ASxxx_IPV4)) then reject;     if (net.type = NET_IP6 && ! (net ~ ASxxx_IPV6)) then reject; Best, Luiz On 23/01/2024 14:13, Nico Schottelius via Bird-users wr

Defines for mixed IPv6/IPv4

2024-01-23 Thread Nico Schottelius via Bird-users
Hello bird users, I am wondering how you handle matching both IPv6 and IPv4 prefixes efficiently. We have tons of blocks in our config like these: define net_genauso_v6 = [ 2a0a:5480::/29+ ]; define net_genauso_v4 = [ 185.203.113.0/24, 185.116.114.0/24 ]; And then later