I will do it as soon as possible in the next few days. Thanks, Mattia
> Il giorno 1 lug 2019, alle ore 08:50, Maria Jan Matejka <jan.mate...@nic.cz> > ha scritto: > > Hello! > > Thank you for checking this. Please send your proposed changes as a patch > for the appropripate git repository, > https://gitlab.labs.nic.cz/labs/bird.wiki.git > … or if you are going to draw the figures, also a pull request is OK in this > case. > > Thanks! > Maria > >> On 6/29/19 4:48 PM, Mattia Milani wrote: >> Solved adapting the configuration help found at the following link: >> https://gitlab.labs.nic.cz/labs/bird/wikis/BGP_filtering >> >> 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) >> >> 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. >> Solved swapping "asn" with another name. >> >> Thanks, >> Mattia >> >> || >> >> Il giorno ven 28 giu 2019 alle ore 18:42 Mattia Milani >> <mattia.mil...@studenti.unitn.it <mailto:mattia.mil...@studenti.unitn.it>> >> ha scritto: >> >> Hello bird community, I have a little problem with some configuration >> files in Bird 2.0 >> >> The protocol I use is BGP >> >> I have a star network with 5 nodes, one in the center with the 4 edges. >> It's something like this (I'm not sure you will see it correctly): >> >> H1 >> | >> H2--H0--H3 >> | >> H4 >> >> Now H1,H2,H3, and H4 will share a network, a basic /24 network, and H0 >> should share them with these rules: >> If the network comes from H2 I share it with H1 and the opposite >> If the network comes from H3 I share it with H4 and the opposite >> >> For this reason, I created this configuration for the H1-H0 link: >> >> protocol bgp h_0_h_1 { >> local 10.0.0.1 as 1; >> neighbor 10.0.0.2 as 2; >> ipv4{ >> import filter bgp_in; >> export where proto = "h_0_h_2"; >> }; >> direct; >> } >> >> 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". >> >> I don't think this is the correct way to handle this situation, could you >> please suggest any other configurations? >> >> Thanks a lot for the help, >> Mattia >> >> -- >> Mattia Milani >> >> >> >> -- >> Mattia Milani > >
