<div dir="ltr"> Solved adapting the configuration help found at the following link:<div><a href="https://gitlab.labs.nic.cz/labs/bird/wikis/BGP_filtering">https://gitlab.labs.nic.cz/labs/bird/wikis/BGP_filtering</a></div><div><br></div><div>This is an excellent configuration explanation, but without figures of the network it's a little bit tricky to read, if possible I may suggest to update the guide with a figure of the network and a figure of the message exchange propagation (clients to everyone and peers to clients ecc)<br></div><div><br></div><div>The first time I tried to implement the code of the guide I got an error in a function because it seems that the name "asn" is reserved, when I tried to start a node with "asn" like parameter of the function I got a syntax error.</div><div>Solved swapping "asn" with another name.</div><div><br></div><div>Thanks,</div><div>Mattia<br></div><div><br><code></code></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno ven 28 giu 2019 alle ore 18:42 Mattia Milani <<a href="mailto:mattia.milani@studenti.unitn.it">mattia.milani@studenti.unitn.it</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello bird community, I have a little problem with some configuration files in Bird 2.0<br><br>The protocol I use is BGP<br><br>I have a star network with 5 nodes, one in the center with the 4 edges.<br>It's something like this (I'm not sure you will see it correctly):<br><br> H1<br> |<br>H2--H0--H3<br> |<br> H4<br><br>Now H1,H2,H3, and H4 will share a network, a basic /24 network, and H0 should share them with these rules:<br>If the network comes from H2 I share it with H1 and the opposite<br>If the network comes from H3 I share it with H4 and the opposite<br><br>For this reason, I created this configuration for the H1-H0 link:<br><br>protocol bgp h_0_h_1 {<br> local 10.0.0.1 as 1;<br> neighbor 10.0.0.2 as 2;<br> ipv4{<br> import filter bgp_in;<br> export where proto = "h_0_h_2";<br> };<br> direct;<br>}<br><br>Obviously, the protocol "h_0_h_2" is the protocol between H0 and H2 that is the same with little differences in addresses and in the export, where proto = "h_0_h_1".<br><br>I don't think this is the correct way to handle this situation, could you please suggest any other configurations?<br><br>Thanks a lot for the help,<br>Mattia<br clear="all"><br>-- <br><div dir="ltr" class="gmail-m_-7802450563125108438gmail_signature"><div dir="ltr">Mattia Milani<br></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Mattia Milani<br></div></div>