handling of the onlink next hop

[Maria Matejka]

Hello Radu,

yes, there are plans to fix it, unfortunately we didn't have time yet to do it. The actual problem is semantics of the nexthop attribute wrt. the configured VRFs, but thinking about that again, I'm almost tempted to say that all the original reasons are gone. So we'll check and let you know very soon.

Thank you for the heads-up, and sorry for breaking this.

Maria

On May 27, 2025 3:28:36 AM GMT+02:00, Radu CARPA <carpa.radu at gmail.com> wrote:
>Hi team,
>
>We've just got the update of bird (bird-2.16.2-1.el9.x86_64->bird-3.1.1-1.el9.x86_64) delivered via rpm updates and it broke our configuration with the following error message:
>
>`/etc/bird.conf:7:5 syntax error, unexpected ONLINK`
>
>By reading the migration guide, i see that it was a deliberate choice to stop supporting this attribute: "The|onlink|route attribute has been temporarily disabled until we find out how to implement it properly."
>
>We used the functionality implemented in 7144c9ca46f092da33a4e051bbce8f973a3bd8c4 . In particular, with the following configuration:
>
>```
>
>    ifname = "tunl0";
>    onlink = true;
>    gw = from;
>
>```
>
>Is there a plan to bring back support for it in the nearby future?
>
>If not, I will try to get in touch with the maintainer of the package in EPEL to see if it's possible to submit and keep maintaining a "bird2" branch of this package in EPEL.
>
>Regards,
>
>Radu

-- 
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20250527/3615bec7/attachment.htm>