- Bird-users - Mailing Lists

Authentication in OSPFv3
by Derek Pan 19 Mar '18

19 Mar '18

Hi developer, my BIRD version: 2.0.0 when I create a ospfv3 instance with authentication info, and I get the output: "Authentication not supported in OSPFv3" do you have a plan to support it or not ? Thanks. Best regards, Derek Pan ADVA Shenzhen

5 6

[BGP] add atribute explanation
by Mattia Milani 16 Mar '18

16 Mar '18

Hello all, i want to add an atribute to bgp protocol in the update message. i already added it to the file attrs.c in bgp_attr_table[]. now i want to add this atribute to update message before send it, i read the documentation and i follow the code from the function bgp_encode_attr where it use the function encode of the attribute, but i didn't seen where to configure the data to encode in the attribute. someone could help me understand where i can set this attribute with a default value? i don't need to specify it in the conf file for my project. Thanks everyone who could help me. Mattia

2 1

Routing via device, not via next hop?
by Michael Schwartzkopff 11 Mar '18

11 Mar '18

Hi, I want to set up a gre tunnel between two routers that speak BGP. bird exports the learned route to the kernel with "via": 10.0.1.0/24 via 192.168.88.101 dev eth0 proto bird But with a gre tunnel I'd need something like ip route add 10.0.1.0/24 dev gre0. Is it possible to configure bird that it exports the route to the kernel with "dev <gre>", not with "via <nexthop>"? Thanks for any help or hints in the right direction. Mit freundlichen Grüßen, -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

3 3

BGP Listen Port
by Joshua McQuistan 10 Mar '18

10 Mar '18

Hello, From BIRD 2.0.0 I can see that the "listen bgp" command has been replaced with "strict bind". However this means that BIRD can no longer listen on a specific port. This is something I am using with 1.6.3 to operate separate BGP instances. For example on a server with a main instance I can test on a different port or on a switch where I don't want to replace the vendor's instance. Is this something that will return? Or have I missed something painfully obvious? Regards, Joshua

2 2

Re: Bird2: BGP password & setkey
by Leo Vandewoestijne 09 Mar '18

09 Mar '18

On Fri, 09 Mar 2018, Ondrej Zajicek wrote: > And if you try BIRD 1.6.3, it works without /etc/setkey.conf? > That's correct; Early 1.x I used setkey.conf without password, and in final releases the opposite seemed the only possible way: so in deed password without setkey.conf Without changes to the OS'es I went to 2.0.1 and now need both. -- Met vriendelijke groet, With kind regards, Leo Vandewoestijne <%2A%2A%2A(a)dns.company> <www.dns.company>

1 0

OSPF in VRF
by Ticlea Alexandru 09 Mar '18

09 Mar '18

Hello Is possible to run ospf instance over an interface which is part of an VRF?I make a config but I see I see no package from local instance on VRF interfaceThe log shows the Hello package are sent out using physical interface Config is like ipv4 table vrf_private; protocol kernel kernel_vrf_private { scan time 1; vrf "vrf-private"; #kernel table 200; ipv4 { table vrf_private; import all; export all; }; } protocol direct direct_vrf_private { vrf "vrf-private"; ipv4 { table vrf_private; }; } protocol ospf ospf_local_core { vrf "vrf-private"; ipv4 { table vrf_private; import all; export all; }; disabled off; instance id 0; debug { states, routes, filters, interfaces, events, packets }; area 0.0.0.0 { interface 1.2.3.0/24, "ens256", "vrf-private" , 172.31.254.0/24 { type broadcast; check link on; tx dscp 0x1a; bfd off; }; }; In log I see 2018-03-08 23:52:31.962 <TRACE> ospf_local_core: HELLO packet sent via ens256 tcpdump shows the packets from the neighbor coming into ens256

2 3

Bgp 4 peer problems, 2 peer stay in connect
by Mattia Milani 09 Mar '18

09 Mar '18

Hello everyone, I'm writing you because i have a problem with the implementation of BGP on 4 peer in 4 different AS in line. I use bird 2.0.1, and the four peer is virtualized on my pc The 4 peer is in this form AS2 AS4 AS3 AS1 H0 ------------------------------- H1 -------------------------------- H2 ------------------------------ H3 eth1 eth1 eth2 eth2 eth1 eth1 The same configuration without H3 work perfectly, but with H3, H1 and H2 can't comunicate, they stay in the connect state, it's like they never bee reachable for the connection, but if i ping the 2 interface i get a replay. the address of my peer is: H0.eth1: 10.0.0.1/8 H1.eth1: 10.0.1.1/8 H1.eth2: 10.0.1.2/8 H2.eth1: 10.0.2.1/8 H2.eth2: 10.0.2.2/8 H3.eth1: 10.0.3.1/8 the 4 configuration of bird is: H0 log "fileLogh0_0.log" all; debug protocols all; router id 200.0.0.2; protocol kernel { metric 0; learn; ipv4 { import all; export all; }; } protocol direct { } protocol device { scan time 2; } function avoid_crappy_prefixes() { if net.len < 8 then return false; if net.len > 24 then return false; return true; } filter bgp_in { if avoid_crappy_prefixes() then accept; else reject; } protocol bgp h0_0_h1_1 { local as 2; neighbor 10.0.1.1 as 4; ipv4{ import filter bgp_in; export all; }; connect retry time 3; source address 10.0.0.1; } H1 log "fileLogh1_1.log" all; debug protocols all; router id 200.0.0.4; protocol kernel { metric 0; learn; ipv4 { import all; export all; }; } protocol direct { } protocol device { scan time 2; } function avoid_crappy_prefixes() { if net.len < 8 then return false; if net.len > 24 then return false; return true; } filter bgp_in { if avoid_crappy_prefixes() then accept; else reject; } protocol bgp h1_1_h0_0 { local as 4; neighbor 10.0.0.1 as 2; ipv4{ import filter bgp_in; export all; }; connect retry time 3; source address 10.0.1.1; } protocol bgp h1_1_h2_2 { local as 4; neighbor 10.0.2.2 as 3; ipv4{ import filter bgp_in; export all; }; connect retry time 3; source address 10.0.1.2; } H2: log "fileLogh2_2.log" all; debug protocols all; router id 200.0.0.3; protocol kernel { metric 0; learn; ipv4 { import all; export all; }; } protocol direct { } protocol device { scan time 2; } function avoid_crappy_prefixes() { if net.len < 8 then return false; if net.len > 24 then return false; return true; } filter bgp_in { if avoid_crappy_prefixes() then accept; else reject; } protocol bgp h2_2_h3_3 { local as 3; neighbor 10.0.3.1 as 1; ipv4{ import filter bgp_in; export all; }; connect retry time 3; source address 10.0.2.1; } protocol bgp h2_2_h1_1 { local as 3; neighbor 10.0.1.2 as 4; ipv4{ import filter bgp_in; export all; }; connect retry time 3; source address 10.0.2.2; } H3 log "fileLogh3_3.log" all; debug protocols all; router id 200.0.0.1; protocol kernel { metric 0; learn; ipv4 { import all; export all; }; } protocol direct { } protocol device { scan time 2; } function avoid_crappy_prefixes() { if net.len < 8 then return false; if net.len > 24 then return false; return true; } filter bgp_in { if avoid_crappy_prefixes() then accept; else reject; } protocol bgp h3_3_h2_2 { local as 1; neighbor 10.0.2.1 as 3; ipv4{ import filter bgp_in; export all; }; connect retry time 3; source address 10.0.3.1; } This are the file .conf, using the command "show protocols" for every peer i get this results: H0 BIRD 2.0.1 ready. Name Proto Table State Since Info kernel1 Kernel master4 up 17:18:55.370 direct1 Direct --- up 17:18:55.370 device1 Device --- up 17:18:55.370 h0_0_h1_1 BGP --- up 17:19:00.115 Established H1 BIRD 2.0.1 ready. Name Proto Table State Since Info kernel1 Kernel master4 up 17:18:55.370 direct1 Direct --- up 17:18:55.370 device1 Device --- up 17:18:55.370 h1_1_h0_0 BGP --- up 17:19:00.115 Established h1_1_h2_2 BGP --- start 17:18:55.370 Connect H2 BIRD 2.0.1 ready. Name Proto Table State Since Info kernel1 Kernel master4 up 17:18:55.370 direct1 Direct --- up 17:18:55.370 device1 Device --- up 17:18:55.370 h2_2_h3_3 BGP --- up 17:19:00.114 Established h2_2_h1_1 BGP --- start 17:18:55.370 Connect H3 BIRD 2.0.1 ready. Name Proto Table State Since Info kernel1 Kernel master4 up 17:18:55.353 direct1 Direct --- up 17:18:55.353 device1 Device --- up 17:18:55.353 h3_3_h2_2 BGP --- up 17:19:00.114 Established Using a ping from H1.eth2 to 10.0.2.2 i get the replay from peer 2 but in the log of H1 i founded that: 2018-03-06 17:11:57.854 <TRACE> h1_1_h2_2: Connecting to 10.0.2.2 from local address 10.0.1.2 2018-03-06 17:11:59.462 <TRACE> device1: Scanning interfaces 2018-03-06 17:12:00.128 <TRACE> h1_1_h2_2: Connecting to 10.0.2.2 from local address 10.0.1.2 2018-03-06 17:12:01.462 <TRACE> device1: Scanning interfaces 2018-03-06 17:12:02.960 <TRACE> h1_1_h2_2: Connecting to 10.0.2.2 from local address 10.0.1.2 2018-03-06 17:12:03.462 <TRACE> device1: Scanning interfaces peer H1 try to estabilish a connection with H2 without success the same for peer H2 using tcp dump i found that it consider 10.0.2.2 unreachable after some arpe request that didn't get answered. without H3 it works perfectly but i want to work with it, sorry if i'm annoying. Thanks if you will answer me with some idea/explanation Mattia

4 9

Bird2: BGP password & setkey
by Leo Vandewoestijne 08 Mar '18

08 Mar '18

Hello, The setkey option caught my attention when reading the 2.x manual... I'm using FreeBSD 11.1 and was trying to have Bird manage the IPSEC (MD5 checksum), which I've succesfully done already in OpenBGPd before NIC.CZ picked up the Bird project. So I have a number of upstream pears that have it enabled. When the password option arrived in Bird I still used setkey, but in the later 1.x releases I needed to use only the 'password' option in bird.conf, and had to drop my IPSEC settings at the OS level. When I now -using bird 2.0.1- put in a BGP protocol block: password "bla"; setkey enabled; I get returned: bird: /usr/local/etc/bird.conf, line 42: Number expected So therefor (after `enabled/disabled`) I tried `1/0`, and then `yes/no`, even `true/false`. But nothing seems make the behaviour different. What was allowed was: password "bla"; setkey; But... having `setkey` in bird.conf -or not- doesn't seem to make any difference. Meaning I still need to define the password both my regular IPSEC settings AND those in Bird. So yes, I got it working, but -reading the manual- I highly doubt double config was intented. What is the correct/simple/efficient method to do this? FYI in /etc/rc.conf I still have: ipsec_enable="YES" ipsec_program="/sbin/setkey" ipsec_file="/etc/setkey.conf" The double config also makes me wonder if I might be confusing things; I find both "IPSEC" or "MD5 TCP checksum" sounds like improving authenticity of a transport, where "BGP password" -to me- sounds like authentication. But reading both the Bird manual as well as the setkey manual it looks like that's the same thing. Anyway, I also discovered you can set a password in a template (which I use in a cascading way), and further on can overwrite/reset it for particular sessions using `password "";`. As the manual doesn't mention it, I'm unsure if that's a bug or a feature, but that's very nice! Another nice new behaviour I discovered is that now you can have mixed (enabled/disabled) sessions on the same interface (which -in my case- is having multiple IP's). In 1.6 I never got that working. -- Met vriendelijke groet, With kind regards, Leo Vandewoestijne <%2A%2A%2A(a)dns.company> <www.dns.company>

2 1

BGP bird implement some exterior split horizon process?
by Mattia Milani 08 Mar '18

08 Mar '18

Hello everyone. I wnant to make a question reguarding BGP in particular EBGP, and how message update send is applied on bird. My bird version is 2.0.1. My Configuration have 3 peer virtualized on my pc with bird running three configuration for BGP The configuration is the following: H0.eth1 is connected to H1.eth1 and they can spooke each other without problem, protocols goes on esatbilished state H1.eth1 like i saide before is connected to H0.eth1 H1.eth2 is connected to H2.eth2 and they can spooke each other without problem, protocols goes on esatbilished state The address of the interface are the following: H0.eth1: 10.0.0.1/30 H1.eth1: 10.0.0.2/30 H1.eth2: 10.0.0.5/30 H2.eth1: 10.0.0.6/30 H0 AS id is 0 H1 AS id is 1 H2 AS id is 2 There is two different subnet between the host, like you can see with the address and the netmask assigned. My question is on the logic of the H1 update sending system. The only peer that export a route is H0, it sends the route to H1 that share it The route shared is 100.0.1.0/24 but this is not important for the question. With tcpdump and the option -vvv i had seen that H0 and H1 open the connection H1 and H0 open the connection H1 and H2 open the connection H0 sends to H1 the route 100.0.1.0/24 with an update message H1 recive the route from H0 it elaborates it and with the filter found that it's valid and put it on his routing table H1 now send an update message with the route learned from H0 only to H2 with the AS PATH setted correctly. But why H1 didn't send back the same update message to H0? H0 after it will discard the route because it found his AS id in the AS path On the RFC they talk about the split horizon but it's only for the interior BGP section 9.2 "UPDATE message from an internal peer, the receiving bgp speaker shall not re-distribute the routing information contained in that update message to other internal peer" obiusly anless it acts like a route reflector But for exterior bgp they didn't spoke about limit like that Now why H1 didn't send the route to H0? it's a bird choice? i can disable that setting somthing on the config file (I searched on the web page but i didn't see anything for that)? If there isn't an atribute to change where i need to change the code of bird to make this working? Thanks for the attention, waiting you answer, Mattia

1 0

BIRD 1.6.3 on Centos7
by Georg Kahest 08 Mar '18

08 Mar '18

Hello, I tried installing bird 1.6.3 from bird repos, but the install seems to fail with dependency error: Resolving Dependencies --> Running transaction check ---> Package bird.x86_64 0:1.6.3-1 will be installed --> Processing Dependency: libtinfo.so.6()(64bit) for package: bird-1.6.3-1.x86_64 --> Processing Dependency: libncurses.so.6()(64bit) for package: bird-1.6.3-1.x86_64 --> Finished Dependency Resolution Error: Package: bird-1.6.3-1.x86_64 (bird) Requires: libtinfo.so.6()(64bit) Error: Package: bird-1.6.3-1.x86_64 (bird) Requires: libncurses.so.6()(64bit) Are the packages in BIRD repo broken ? Georg

1 0