- Bird-users - Mailing Lists

Bird and RIP
by Anton Kiryushkin 05 Jan '16

05 Jan '16

Hello. Could you tell me status RIP in bird. Is it still broken in Bird? Or it should works fine? I have a problem with rip_metric. -- Best regards, Anton Kiryushkin

3 7

deterministic order for include by wildcard
by Warren Turkal 28 Dec '15

28 Dec '15

Hey folks, Do wildcards in includes resolve in a deterministic order? I'd like to just put something like the following in my bird.conf: include "/etc/bird.d/*.conf" If I do that, can I rely on 10-common.conf to be included before 20-bgp_to_other_place.conf so that I can define templates in a common place and use those templated in the later included files? If there is a deterministic order, it might make sense to identify that order in the docs. I only found [1], which does not say anything about the order of the files included. Also, if the ordering does exist, does anything affect the ordering? As a side note, it would also be nice to add an anchor to each option in the different sections where there are options so that one could link directly to the option within the section. If that had existed, I could have linked to the "include" option directly. Is there a bug tracker somewhere for bird for this type of request? Thanks, wt [1]http://bird.network.cz/?get_doc&f=bird-3.html#ss3.2 at the "include" option

3 4

generic extended communities support
by Warren Turkal 28 Dec '15

28 Dec '15

Bird folks, Is there any chance that the transitive part of the following RFC draft will be implemented in BIRD? https://tools.ietf.org/html/draft-ietf-idr-as4octet-extcomm-generic-subtype… I only ask as the implementation seems like it might be trivial since one can already do something like (4, 4200000000, 60000) already works for ext communities in Bird. This would definitely be useful to me, as I am currently abusing route origin subtype ext communities since they have no special meaning in bird. I would love to see the following syntax available: (generic, 4200000000, 60000) Thanks, wt

2 1

Trouble with inter and intra area filtering between two areas.
by LU 28 Dec '15

28 Dec '15

Hello. Here's my setup with 4 routers: area 0 / \ R1 ---- R2 | | | | R3 ------ R4 \ area1 / What I am trying is to prevent routes that fall in 10.0.0.0/8 range from being announced from Area 1 routers (R3, R4) to Area 0 routers (R1, R2). At the same time I want Area 1 routers (R3, R4) to exchange these routes between themselves. I thought that I could achieve it by using "networks { 10.0.0.0/8 hidden; };" in Area 1 routers configs. Documentation says: "Hidden networks are not propagated into other areas." It does indeed prevent annoucement to Area 0 routers from Area 1, but at the same time it also filters these routes out between Area 1 routers (R3, R4) which is not what I want, I expected it not getting filtered from Area 1 routers. (Since they are the same area). Is there any way I can filter 10.0.0.0/8 from reaching Area 0 from Area 1, but at the same time keep such routes announced between Area 1 routers? Thank you. My configs are as follows: Config for R1: router id 1.1.1.1; protocol kernel { export all; } protocol device { scan time 10; } protocol static { } protocol ospf { tick 2; area 0.0.0.0 { interface "eth0" { # interface from R1 to R2 dead count 4; type broadcast; }; interface "eth1" { # interface from R1 to R3 dead count 4; type broadcast; }; }; } Config for R2: router id 2.2.2.2; protocol kernel { export all; } protocol device { scan time 10; } protocol static { } protocol ospf { tick 2; area 0.0.0.0 { interface "eth0" { # interface from R2 to R1 dead count 4; type broadcast; }; interface "eth1" { # interface from R2 to R4 dead count 4; type broadcast; }; }; } Config for R3: router id 3.3.3.3; protocol kernel { export all; } protocol device { scan time 10; } protocol static { } protocol ospf { tick 2; area 0.0.0.0 { interface "eth0" { # interface from R3 to R1 dead count 4; type broadcast; }; }; area 0.0.0.1 { stub yes; summary no; networks { 10.0.0.0/8 hidden; }; interface "eth1" { # interface from R3 to R4 cost 1000; dead count 4; type broadcast; }; interface "ppp*" { stub yes; }; }; } Config for R4: router id 4.4.4.4; protocol kernel { export all; } protocol device { scan time 10; } protocol static { } protocol ospf { tick 2; area 0.0.0.0 { interface "eth0" { # interface from R4 to R2 dead count 4; type broadcast; }; }; area 0.0.0.1 { stub yes; summary no; networks { 10.0.0.0/8 hidden; }; interface "eth1" { # interface from R4 to R4 cost 1000; dead count 4; type broadcast; }; interface "ppp*" { stub yes; }; }; }

2 1

route withdraws on BGP route-refresh
by Christos Trochalakis 28 Dec '15

28 Dec '15

Hello all, While debugging a route-refresh issue we discovered that when a route-refresh is received, bird, instead of just sending an update containing the exported routes, also withdraws **all known routes** from its peer. In our case, it withdraws the whole FIRT sending multiple BGP updates. Is this the expected behaviour? We are using bird 1.4.5. We believe that the opposite router has trouble processing all those withdrawed routes which leads to other connectivity issues.

3 3

[bird-ospf] LSA forward-address is incorrect
by danilov 28 Dec '15

28 Dec '15

Hello. I have a small network with several bird routers as bgp and ospf routers. EBGP-session has been established between one of our bgp-routers and customer router with multihop feature through OSPF-domain and iBGP-domain. Then bgp-router advertises the customer announce to other bgp-router, that also works as OSPF ASBR (ospf-domain on the one side and ibgp-domain on the other side). On this ASBR-router I see the valid next-hop value (customer router IP-address in OSPF-domain) in the corresponded routes of customer. This routes are installed to OSPF-domain, but in the outgoing LSA-updates I see only 0.0.0.0 forward-address values instead the customer router IP-address (I have checked it with wireshark). Brief flowchart: (CUSTOMER-ROUTER)--(PE)--<ospf-domain>--(ASBR)--<ibgp-domain>--(BGP-ROUTER) \ / \-------------------EBGP session---------------------/ Some info from ASBR: >From bird command line. bird> show route all XX.XX.102.0/23 export ospf_tst XX.XX.102.0/23 via YY.YY.0.210 on eth1 [bgp_tst_r1 12:41:09] * (100) [AS____i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 48938 BGP.next_hop: ZZ.ZZ.21.94 <-- this address of the customer router in the ospf network (correct) BGP.med: 0 BGP.local_pref: 800 OSPF.metric1: 16777215 OSPF.metric2: 10000 OSPF.tag: 0x00000000 OSPF.router_id: 0.0.0.0 bird> show route all for ZZ.ZZ.21.94 protocol ospf_tst ZZ.ZZ.21.92/30 via WW.WW.6.32 on eth0.4 [ospf_tst 13:47:14] * I (150/16) [WW.WW.6.32] Type: OSPF unicast univ OSPF.metric1: 16 OSPF.metric2: 16777215 OSPF.tag: 0x00000000 OSPF.router_id: WW.WW.6.32 <-- pe-router ------------------------- Dump of LSA-packet: Open Shortest Path First OSPF Header Version: 2 Message Type: LS Update (4) Packet Length: 64 Source OSPF Router: YY.YY.0.10 (YY.YY.0.10) Area ID: 0.0.0.0 (0.0.0.0) (Backbone) Checksum: 0x0000 (None) Auth Type: Cryptographic (2) Auth Crypt Key id: 1 Auth Crypt Data Length: 16 Auth Crypt Sequence Number: 6541704 Auth Crypt Data: 973debe532daa553f846053cd44d481f LS Update Packet Number of LSAs: 1 AS-External-LSA (ASBR) .000 0000 0000 0001 = LS Age (seconds): 1 0... .... .... .... = Do Not Age Flag: 0 Options: 0x02 (E) 0... .... = DN: Not set .0.. .... = O: Not set ..0. .... = DC: Demand Circuits are NOT supported ...0 .... = L: The packet does NOT contain LLS data block .... 0... = NP: NSSA is NOT supported .... .0.. = MC: NOT Multicast Capable .... ..1. = E: External Routing Capability .... ...0 = MT: NO Multi-Topology Routing LS Type: AS-External-LSA (ASBR) (5) Link State ID: XX.XX.102.0 (XX.XX.102.0) Advertising Router: YY.YY.0.10 (YY.YY.0.10) Sequence Number: 0x80000001 Checksum: 0xb1b5 Length: 36 Netmask: 255.255.254.0 (255.255.254.0) External Type: Type 1 (metric is specified in the same units as interface cost) Metric: 20 Forwarding Address: 0.0.0.0 (0.0.0.0) <-- should be ZZ.ZZ.21.94 External Route Tag: 0 --------------------- Currently the workaround are used -static route on the PE, but this way has corresponded issues. With best regards, Anton Danilov littlesmilingcloud(a)gmail.com

2 1

Syntax for setting bgp_origin
by Гаврилов Игорь 22 Dec '15

22 Dec '15

Hi everyone! Could someone show me how to set bgp_origin attribute on redistributed prefixes? I have tried if net =10.0.0.0/8 then { bgp_origin = ORIGIN_INCOMPLETE; accept; } But it doesn't work.

3 5

ECMP support
by Shaun Crampton 17 Dec '15

17 Dec '15

Hi, I found a few messages in the archive that mention multi path and ECMP but the website says it's TODO. I was just wondering what the status is? I'm interested in having BIRD configure the Linux routing table for ECMP, if possible. Thanks, -Shaun

6 7

default route via OSPF depending on the ISP
by Rohrmann Sascha 15 Dec '15

15 Dec '15

Dear users of the Bird internet routing daemon, First of all I am sorry for my e-mail which I have sent some minutes before. It was a mistake and you can ignore my last mail. Now to my question: I want my OSPF to distribute the default-route ONLY and ONLY if the ISP is available. Means, if the link, or the IP isn't available, my OSPF should be quite. Further information: ISP (ISP is up) l (Link is up) R1 (Interface is up) R1: everything is ok, I can reach the ISP, so I am the default-gateway for everybody below me. ISP (ISP is down) l (Link is up) R1 (Interface is up) R1: Oh gosh! The ISP is down! I am now no longer the default-gateway for everybody below me. ISP (ISP is up) l (Link is down) R1 (Interface is up) R1: Oh, I can't reach my ISP... Ok, I need to stop telling everybody below me I am the default-gateway. I was thinking about the bfd protocol, but bfd is kinda new and you can't run more than one instance in bird. So I need another solution... Btw, yes I've already searched for these problem in the mailing list but I am not satisfied. Either my keywords were wrong or there isn't any person with this kind of problem... yet. Thank you very much for reading. Regards.

5 11

segfault with BFD
by Michal Humpula 11 Dec '15

11 Dec '15

Hi, I came across this lovely segfault when using BFD in Bird v1.4.5 and v1.5: (gdb) bt #0 bfd_send_ctl (p=0x5555557cf840, s=0x5555557e2cf8, final=0) at ../../../proto/bfd/packets.c:66 #1 0x000055555556fc86 in timers_fire (loop=loop@entry=0x5555557dfba0) at ../../../proto/bfd/io.c:437 #2 0x000055555556fe24 in birdloop_main (arg=0x5555557dfba0) at ../../../proto/bfd/io.c:759 #3 0x00007ffff7bc4182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007ffff78f147d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Any idea if this is fixed in latest master or that it might be result of misconfiguration? Cheers Michal

3 5