Hello!
If that option is by default off and doesn't make the code inadequately
complex, then basically yes, and in this specific case also yes.
Interoperability is important.
Maria
On 5/12/23 21:36, Arnaud Houdelette-Langlois via Bird-users wrote:
Hi.
I have an issue with the BGP implementation of a well-known hardware
manufacturer.
Said implementation send multiple Add-Path capabilities, one for each
address family, instead of sending only one capability with both address
families. Moreover, it expects it's BGP peer to behave identically.
If bird manages to understand the badly formatted open message, the said
BGP implementation fails and reject bird (well-formed) message.
The manufacturer is informed, but has still to provide a working patch.
In the meantime, I think it would be easy to implement a workaround as a
bgp protocol option in bird. I'm ready to dive into the code to do it.
But ...
Is it bird policy to accept such workaround pull requests ?
--
Arnaud Houdelette-Langlois
Administrateur des infrastructures systèmes et réseaux
Normandie Université
+33 2 31 56 69 54
