May 2024 - Bird-users - Mailing Lists

IPv6 OSPF stub interface not taken into account
by Alarig Le Lay 06 May '24

06 May '24

Hello, I have two OSPF protocols, one for IPv4 and one for IPv6. I’ve set the lo interface for both, but it only shows up for IPv4: protocol ospf ospf_ipv4 { merge external; ipv4 { import all; import keep filtered; import limit 200 action block; import filter { if (net ~ [ 0.0.0.0/0 ]) then { reject; } else { igp_metric = ospf_metric1; accept; } }; export all; export filter { if (proto = "kernel_grt_ipv4" || proto = "direct1") then { ospf_metric2 = 64; ospf_tag = 1336561914; accept; } else reject; }; }; area 0.0.0.0 { interface "lo" { stub; }; include "/etc/bird.lag-*.conf"; interface "wg0" { cost 200; }; }; }; protocol ospf v3 ospf_ipv6 { merge external; ipv6 { import all; import keep filtered; import limit 200 action block; import filter { if (net ~ [ ::/0 ]) then { reject; } else { igp_metric = ospf_metric1; accept; } }; export filter { if (proto = "kernel_grt_ipv6" || proto = "direct1") then { ospf_tag = 1336561914; accept; } else reject; }; }; area 0.0.0.0 { interface "lo" { stub; }; include "/etc/bird.lag-*.conf"; interface "wg0" { cost 200; }; }; }; edge03-stolon ~ # birdc BIRD 2.15.1 ready. bird> show ospf interface ospf_ipv6 "lo" ospf_ipv6: bird> show ospf interface ospf_ipv4 "lo" ospf_ipv4: Interface lo (45.91.126.241/32) Type: nbma Area: 0.0.0.0 (0) State: Waiting (stub) Priority: 1 Cost: 10 ECMP weight: 1 Hello timer: 10 Poll timer: 20 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 Designated router (ID): 0.0.0.0 Designated router (IP): 0.0.0.0 Backup designated router (ID): 0.0.0.0 Backup designated router (IP): 0.0.0.0 It looks like a bug to me, but perhaps I missed something. -- Alarig

2 2

EVPN support in BIRD
by Ondrej Zajicek 06 May '24

06 May '24

Hello Recently, we made a beta release of EVPN support in BIRD: https://gitlab.nic.cz/labs/bird/-/tree/evpn (branch 'evpn' in BIRD git repository) You are welcome to try it and give us your feedback and suggestions. The primary documentation is still missing, but there are comprehensive examples and comments here: https://gitlab.nic.cz/labs/bird-tools/-/tree/master/netlab/cf-evpn-bgp (especially bird_m11.conf and bird_m12.conf) For filter expressions related to EVPN, see function t_net_evpn() in: https://gitlab.nic.cz/labs/bird/-/blob/evpn/filter/test.conf If you have any questions, feel free to ask here on the mailing list. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago(a)crfreenet.org) "To err is human -- to blame it on a computer is even more so."

2 3

bird2 doesn't negotiate with gobgp over ipv6
by Vladimir Pouzanov 06 May '24

06 May '24

Hi! I'm running bird 2.15.1 and I'm trying to make it talk to cilium that uses gobgp under the hood. I can negotiate the session over ipv4 with no issues, but due to a bug in the cilium implementation, the ipv6 routes aren't advertised properly. The suggestion from cilium was to negotiate the session over ipv6, but this creates issues for bird. I have a config that looks somewhat like this: protocol bgp { local port 179 as 65100; neighbor range 0::/0 port 179 as 65100 internal; dynamic name "GW6_"; direct; passive; ipv4 { import all; }; ipv6 { import all; }; } protocol bgp { local port 179 as 65100; neighbor range 10.0.0.0/8 port 179 as 65100 internal; dynamic name "GW4_"; direct; passive; ipv4 { import all; }; ipv6 { import all; }; } When I connect to bird over ipv4, gobgp sends a packet like this: Frame 4: 154 bytes on wire (1232 bits), 154 bytes captured (1232 bits) on interface vmbrdev, id 0 Ethernet II, Src: 22:fc:7f:47:6b:f4 (22:fc:7f:47:6b:f4), Dst: 6e:82:6c:1b:e9:95 (6e:82:6c:1b:e9:95) Internet Protocol Version 4, Src: 10.224.129.15, Dst: 10.224.129.1 Transmission Control Protocol, Src Port: 39201, Dst Port: 179, Seq: 1, Ack: 1, Len: 88 Border Gateway Protocol - OPEN Message Marker: ffffffffffffffffffffffffffffffff Length: 88 Type: OPEN Message (1) Version: 4 My AS: 65100 Hold Time: 90 BGP Identifier: 10.224.129.15 Optional Parameters Length: 59 Optional Parameters Optional Parameter: Capability Parameter Type: Capability (2) Parameter Length: 57 Capability: Route refresh capability Type: Route refresh capability (2) Length: 0 Capability: FQDN Capability Type: FQDN Capability (73) Length: 12 Hostname Length: 10 Hostname: dev-master Domain Name Length: 0 Domain Name: Capability: Unknown capability 75 Type: Unknown (75) Length: 13 Unknown: 0c476f4247502f332e32332e30 Capability: Multiprotocol extensions capability Type: Multiprotocol extensions capability (1) Length: 4 AFI: IPv4 (1) Reserved: 00 SAFI: Unicast (1) Capability: Multiprotocol extensions capability Type: Multiprotocol extensions capability (1) Length: 4 AFI: IPv6 (2) Reserved: 00 SAFI: Unicast (1) Capability: Support for 4-octet AS number capability Type: Support for 4-octet AS number capability (65) Length: 4 AS Number: 65100 Capability: Extended Next Hop Encoding Type: Extended Next Hop Encoding (5) Length: 6 AFI: IPv4 (1) SAFI: Unicast (1) Next hop AFI: IPv6 (2) Which is followed up by OPEN from bird2 and they establish the session. The logs say: May 04 14:47:02 ammy bird[7755]: bgp2: Incoming connection from 10.224.129.15 (port 39201) accepted May 04 14:47:02 ammy bird[7755]: GW4_1: Initializing May 04 14:47:02 ammy bird[7755]: GW4_1: Starting May 04 14:47:02 ammy bird[7755]: GW4_1: State changed to start May 04 14:47:02 ammy bird[7755]: GW4_1: Started May 04 14:47:02 ammy bird[7755]: GW4_1: Got OPEN(as=65100,hold=90,id=10.224.129.15) May 04 14:47:02 ammy bird[7755]: GW4_1: Sending OPEN(ver=4,as=65100,hold=240,id=0ae08101) May 04 14:47:02 ammy bird[7755]: GW4_1: Sending KEEPALIVE May 04 14:47:02 ammy bird[7755]: GW4_1: Got KEEPALIVE May 04 14:47:02 ammy bird[7755]: GW4_1: BGP session established When I try to establish the connection over ipv6, gobgp sends an OPEN that's exactly the same sans being transferred over ipv6: Frame 15: 174 bytes on wire (1392 bits), 174 bytes captured (1392 bits) on interface vmbrdev, id 0 Ethernet II, Src: 22:fc:7f:47:6b:f4 (22:fc:7f:47:6b:f4), Dst: 6e:82:6c:1b:e9:95 (6e:82:6c:1b:e9:95) Internet Protocol Version 6, Src: 2a01:xxx:xxx:xxx:xxx:xxx:xxx:d930, Dst: fd00::53 Transmission Control Protocol, Src Port: 58663, Dst Port: 179, Seq: 1, Ack: 1, Len: 88 and then bird just stalls the connection. The logs say: May 04 14:49:17 ammy bird[7755]: bgp1: Incoming connection from 2a01:4f8:173:fe11:6f81:e7cd:2787:fb71 (port 35581) accepted May 04 14:49:17 ammy bird[7755]: GW6_1: Initializing May 04 14:49:17 ammy bird[7755]: GW6_1: Starting May 04 14:49:17 ammy bird[7755]: GW6_1: State changed to start May 04 14:49:17 ammy bird[7755]: GW6_1: Waiting for 2a01:xxx:xxx:xxx:xxx:xxx:xxx:d930 to become my neighbor I suspect it's either a bug or a misconfiguration on the bird side, because gobgp behaves the same in both scenarios. How do I investigate/debug this further?

3 7

why ABR flood lsa3 to non-backbone area?
by chan alfie 06 May '24

06 May '24

hi community, I got some confused of ospf lsa3. topology: r1 --a12-- r2 --a0-- r3 --a34-- r4 | | +---a23 ---+ r1(intf:r1r2) and r2(intf:r2r1) are belong to area 12, ptp network: 10.0.12.0/30 r2(intf:r20r30) and r3(intf:r30r20) are composed to area 0, ptp network: 10.0.100.0/30 r2(intf:r2r3) and r3(intf:r3r2) are composed to area 0, ptp network: 10.0.23.0/30 r3(intf:r3r4) and r4(intf:r4r3) are cmposed to area 34, ptp network: 10.0.34.0/30 r1 has a stub net: 10.1.1.0/30 r4 has a stub net: 10.4.2.0/30 why r2/r3 regenerated lsa3 and advertise on area 23, isn't it prohibited ABR to flood lsa3 to non-backbone area? r2 ``` bird> s o l type 3 area 23 Area 0.0.0.23 Type LS ID Router Sequence Age Checksum 0003 10.0.12.3 10.0.0.2 80000004 1088 6885 0003 10.0.34.3 10.0.0.2 80000004 1064 d9f3 0003 10.0.100.3 10.0.0.2 80000004 1088 9cf8 0003 10.1.1.3 10.0.0.2 80000004 1070 3ab3 0003 10.4.2.3 10.0.0.2 80000004 1060 6f70 0003 10.0.12.3 10.0.0.3 80000004 1063 c61c 0003 10.0.34.3 10.0.0.3 80000004 1069 6f67 0003 10.0.100.3 10.0.0.3 80000004 1069 96fd 0003 10.1.1.3 10.0.0.3 80000004 1063 984a 0003 10.4.2.3 10.0.0.3 80000004 1062 05e3 ```

1 0

build: symbol ‘bfd_auth_type’ is used, but is not defined as a token and has no rules
by Zhang Maiyun 01 May '24

01 May '24

Hello, I was trying to build the latest commit and encountered this error: nest/config.Y:615.19-31: error: symbol ‘bfd_auth_type’ is used, but is not defined as a token and has no rules It looks like commit e6dbde688 introduced a dependency on the type `bfd_auth_type` into `nest/config.Y`. However, if protocol bfd is not enabled (e.g. because of disabling pthreads), `proto/bfd/config.Y` won’t get included in the parser and thus `bfd_auth_type` is undefined. Perhaps this should be fixed? Thanks! Maiyun Zhang (he/him)

1 0