January 2019 - Bird-users

UHb (broadcast) routes get into OSPF database on OpenBSD 6.4
by Igor Podlesny 21 Jan '19

21 Jan '19

I have an instance of Bird 1.6.4 on a freshly installed OpenBSD 6.4. My study of its OSPF database shown (with birdc show ospf lsadb self) that there were LSAs for broadcast routes that are indicated as ones having "UHb" in netstat -rn output. I suspect they're added by "protocol direct", but didn't check it yet. Looks like a bug, doesn't it? -- End of message. Next message?

2 1

Bird handles OpenBSD route priority differently
by Igor Podlesny 21 Jan '19

21 Jan '19

(compared to native OSPF daemon.) Test lab: just two routers with OSPF on both: A and B. OpenBSD 6.4. Bird 1.6.4p1. Router A has two default routes installed: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Prio Iface default 192.168.69.36 UGS 0 353 - 8 vio0 default 192.168.69.37 UGS 0 0 - 12 vio0 bird> show ospf state all area 0.0.0.0 router 192.168.69.34 distance 0 network 192.168.69.32/29 metric 10 external 0.0.0.0/0 metric2 10000 via 192.168.69.37 external 192.168.69.32/29 metric2 10000 Higher priority 12 is of a lesser significance, so kernel prefers default via .36. Trying OpenOSPFd it's seen that theirs OSPF also prefers default via .36 in its advertisements. -- End of message. Next message?

2 1

Does repeated config timeout work as single (first one) accumulated?
by Igor Podlesny 17 Jan '19

17 Jan '19

IOW, let's say we have config version 1. Then if config has been changed (become version 2) and temporarily applied with config timeout 10 and then before it's been rolled back (assuming control still isn't lost of course), entered config timeout 30 would it be effectively the same as if you'd have entered just "config timeout 40" in the first time? Or would the second "config timeout" commit version 2 instead and when timeout is reached would rollback from version 3 (which is equal by content to version 2) to version 2 instead of version 1? -- End of message. Next message?

2 3

Do filters support accessing properties of some interfaces?
by Igor Podlesny 16 Jan '19

16 Jan '19

-- Is it possible to get link status (up/down? anything else?) of an interface (specified by interface name or other reference way if there're any) for further use in routes' preferences/metrics calculations? Hi :) -- End of message. Next message?

2 3

bird-2.0.3 - centos 7 rpm
by Shahan Agha 16 Jan '19

16 Jan '19

Hi all, Do we have any updates if there is official Cent OS 7 rpm for bird-2.0.3 or bird-2.0.2 to be released any soon? There was a thread mentioning that packages for bird 2.0 are expected with next release. Thanks, Shahan

3 3

Bird Version Ubuntu
by marcelo henrique 11 Jan '19

11 Jan '19

Hi People, In this week, was released a new version the bird, version bird-2.0.3.tar.gz but i don't found version to ubuntu packages. Would be possible to release the version package to ubuntu ? Thanks a Lot, Marcelo Frota

3 3

Re: cannot export routes (AS_PATH problem ?)
by Ondrej Zajicek 08 Jan '19

08 Jan '19

On Mon, Jan 07, 2019 at 09:38:12AM +0100, Julien Sansonnens wrote: > Hi Ondrej, > > policy routing was exactly what I was looking for, thanks for your help > I managed to have it done using the "secondary" switch, it's working great. Hi 'secondary' switch could be used for that, but note that when used for BGP, it does not change forwarding table. It is useful for route servers, but less for policy routing and forwarding. If you are using route A, but propagating route B to your peer, then if you receive network traffic from the peer, it is still routed according to route A (unless you do some other tricks). To have proper forwarding with policy routing, you generally would need two kernel routing tables, appropriate policy routing rules, two BIRD routing tables connected with pipe (with appropriate filtering on the pipe) and two BIRD kernel protocols synchronizing BIRD tables with kernel tables. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago(a)crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."

1 0

BIRD 2.0.3 and 1.6.5
by Ondrej Filip 07 Jan '19

07 Jan '19

Dear BIRD users, we just released two new versions - 1.6.5 and 2.0.3. Many thanks mainly to Santiago and Maria! Version 1.6.5 o MRT table dumps (RFC 6396) o BGP Long-lived graceful restart o Filter: Make ifname attribute modifiable o Improved keeping track of IPv6 link-local addresses o Many bugfixes Version 2.0.3 (2019-01-05) o MRT table dumps (RFC 6396) o BGP Long-lived graceful restart o BGP: Optional import table (Adj-RIB-In) o BGP: Extend 'next hop keep' and 'next hop self' options o BGP: Improved VRF support o OSPF: Authentication trailer for OSPFv3 (RFC 7166) o Babel: New option to randomize router ID o Filter: Custom route attributes o Filter: Support for src accessor to SADR source prefix o Filter: Support for VPN_RD sets o Filter: Make ifname attribute modifiable o Perf: Protocol to measure BIRD performance internally o More verbose error messages in config processing o Log file size limit / log rotation o Many bugfixes Notes: Export of routes to RS EBGP (route server) sessions from other sources than RS EBGP sessions was changed that ASN is no longer prepended to BGP_PATH in that case. The change does not affect regular BGP configurations or regular route servers that have only RS EBGP peers. For BGP route servers and route reflectors, the default value of option 'next hop keep' was changed to a more appropriate value. Attributes for OSPF and Babel metrics are no longer reset when exported to these protocols and could be set anywhere in BIRD. As a result, OSPF metric is kept when a route is reannounced between OSPF instances. Also, when route is exported to OSPF with both ospf_metric1 and ospf_metric2 attributes it is now propagated as OSPF-E2 route instead of as OSPF-E1 route. Compiling BIRD with --enable-debug no longer automatically activates debug mode (-d option) nor local mode (-l option). Also, debug mode with output to file (-D option) no longer not forces foreground mode (-f option). The configure script now uses standard option --runstatedir, the old option --with-runtimedir is deprecated. Happy hacking in 2019! Ondrej

1 0

Check bgp_path.len without some AS
by Xavier Trilla 06 Jan '19

06 Jan '19

Hi, For some route selection configurations I need to check the bgp_path.len without some AS numbers. I tried something like: bgp_path.delete(AS_1); bgp_path.delete(AS_2); if bgp_path.len < N then ... But doing this I modify permanently the AS path. I've tried using a temp variable, but looks like bird doesn't allow to create bgppath "variables". Any ideas about how this could be achieved? Thanks! Xavier

3 5

cannot export routes (AS_PATH problem ?)
by Julien Sansonnens 06 Jan '19

06 Jan '19

Hi, Using BIRD 1.6.4 I want to do something very basic: export routes to a peer to allow transit. for that, I start by adding communities to my received routes, so I can distinguish the upstream. import filter { if !is_martian() && !is_self_net() && from = bgp_next_hop then { bgp_large_community.add((myas, 100, XX)); #XX for each upstream accept; } else reject; }; A community is (apparently?) added to each route. I get about 61'000 ipv6 routes from my upstream. Now I want to export them to "peer1". Here is my export function: function bgp_export_peer (){ if (myas,100,20) ~ bgp_large_community then return true; } here is the problem: it looks like only 123 routes are exported ! bird> show route export peer count 123 of 362489 routes for 61724 networks Here is an example of an exported route: 2001:9d8:200b::/48 via 2a06:1287:3308:c0c0::1 on peer-mmnetworks [mmnet 22:24:20] * (100) [AS25577i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 207149 206499 204893 206313 6724 8560 25577 BGP.next_hop: 2a0c:b640:fffe:10:192:220:4:2 BGP.local_pref: 100 BGP.community: (666,666) (997,6499) (6724,900) (6724,960) (8560,4) (8560,10000) (57555,0) (57555,4100) (57555,4101) (65010,10000) BGP.large_community: (206313, 206313, 206313) (207149, 100, 20) and an example of a non-exported route: 2406:3003:2032::/48 via 2a06:1287:3308:c0c0::1 on peer-mmnetworks [mmnet 20:48:51] (100) [AS55430i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 206499 6939 38861 55430 BGP.next_hop: 2a06:1287:3308:c0c0::1 fe80::b9d7:d605 BGP.med: 0 BGP.local_pref: 100 BGP.community: (0,2906) (0,6939) (0,12876) (0,12989) (0,13335) (0,15133) (0,15169) (0,16265) (0,16276) (0,16509) (0,20940) (0,22822) (0,32934) BGP.large_community: (207149, 100, 20) as you see, my lare community are added on both routes. The exported route has my AS as the first value on the left (AS_PATH), which is not the case for the non-exported route. Logically, all exported routes should have my AS on the left. Am I missing something? It's probably logical, but I do not understand what's going on here. In the same way, I can not export any route that comes from my peers (direct connection), since they have only their AS in the path. help would be highly appreciated. cheers, Julien Sansonnens

4 5