<html><head></head><body><div dir="auto">Hello!<br><br>Yes, it's hardcoded, typically as a macro / constant definition. I don't see any good reason to have it outside BIRD.<br><br>Maria</div><br><br><div class="gmail_quote"><div dir="auto">On 12 May 2023 14:23:37 CEST, Douglas Fischer <fischerdouglas@gmail.com> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">This conversation piqued my curiosity...<br><br>P.S.: It's almost a fork on the topic, but maybe it could be a productive conversation. I apologize in advance if I mess up.<br><br>Just for context:<br>I'm not a programmer!<br>I have some references of the concepts, but almost no practice in it.<br><br>How does Bird load these possible attribute variations?<br>In the specific case, where is it defined that 0 -> Provider, 1-> RS, 2 -> RS-Client, 3 -> Customer, 4 -> Peer, and etc...?<br>Is this hardcoded in the source code?<br>Is there any lib apart from where this is described that is loaded at binary initialization?<br><br>The same question applies to other questions like BGP Message types, address families...<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em sex., 12 de mai. de 2023 às 06:04, Mikhail Grishin <<a href="mailto:magr@ripn.net">magr@ripn.net</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
Thanks.<br>
<br>
I'll also remind you the idea to show in Bird CLI<br>
not<br>
Last error: BGP Error: Role mismatch<br>
but<br>
Last error: BGP Error: Role mismatch (provider)<br>
<br>
In some of previous conversations you accepted it.<br>
<br>
Ondrej Zajicek пишет 11.05.2023 18:27:<br>
><br>
> In the logs printed Error: Role mismatch (provider)<br>
> Hi<br>
><br>
> Yes, it is a bug in BIRD. When BGP capability option is parsed, the<br>
> capability structure is initialized with the proper default value, but<br>
> when there is no BGP capability option altogether (like in these case),<br>
> the capability structure is just zeroed. Unfortunately, RFC 9234 is the<br>
> only supported capability that has non-zero default value (0xff), zero<br>
> is 'provider'. Will fix that.<br>
><br>
> I am surprised that in 2023 there are still BGP routers not supporting /<br>
> sending capabilities :-) .<br>
><br>
<br>
</blockquote></div><br clear="all"><div><br></div></blockquote></div></body></html>