March 2019 - Bird-users - Mailing Lists

Route redistribution between OSPF instances
by Yaroslav Dronskii 08 Mar '19

08 Mar '19

Hello, I need some help in understanding bird. Route redistribution between ospf instances doesn't work for me. I tried everything I could think of short of debugging source code, and narrowed it down to route type. If it's RTS_OSPF_IA, ospf_metric2 is set to LSINFINITY. How I wanted to use it: VM announces some /32 net in area 20. This net is received by vm's host into table_ospf_0 and redistributed to: 1) backbone area so other vm hosts can reach it 2) table_allroutes via a pipe. Ospf_allroutes protocol takes it from table_allroutes and announces it to everyone in area 30. Am I doing something stupid? Should it even work? Minimal config example: ipv4 table table_ospf_0; # contains host-host vm /32 ip announces ipv4 table table_allroutes; # contains all routes learned. protocol pipe pipe_ospf_0_allroutes { table table_ospf_0; peer table table_allroutes; import none ; export filter { if (net.len = 32) then accept; else reject; } ; } protocol ospf ospf_vm { ipv4 { table table_ospf_0; export all; import filter filter_from_ospf; }; # meant for host-host vm /32 ip announces # without it, best route to other host's vm will be via PE area 0.0.0.0 { interface "ospf0-br" { authentication cryptographic; password "pass1"; }; }; # meant for ip announces. area 0.0.0.20 { interface "ospf20-br" { authentication cryptographic; password "pass2"; }; }; } protocol ospf ospf_allroutes { ipv4 { table table_allroutes; import keep filtered on; export all; import filter filter_to_kernel; }; # Meant for vm's that want to accept ALL routes with per-vrf ospf tag area 0.0.0.30 { interface "ospf30-br" { authentication cryptographic; password "pass3"; }; }; } How route is seen: Imported from other vm host via ospf: bird> show route table table_ospf_0 10.20.5.135/32 all Table table_ospf_0: 10.20.5.135/32 unicast [ospf_vm 13:52:53.209] IA (150/20) [10.255.10.129] via 10.133.146.12 on ospf0-br Type: OSPF-IA univ Piped to table_allroutes: (as expected, nothing changed) bird> show route table table_allroutes 10.20.5.135/32 all Table table_allroutes: 10.20.5.135/32 unicast [ospf_vm 13:52:53.209] IA (150/20) [10.255.10.129] via 10.133.146.12 on ospf0-br Type: OSPF-IA univ In ospf_vm: # birdc show ospf state ospf_vm area 0.0.0.0 router 10.255.10.129 distance 10 ... xnetwork 10.20.5.135/32 metric 10 ... xrouter 10.20.5.135 metric 10 area 0.0.0.20 router 10.255.10.128 distance 0 xnetwork 10.20.5.135/32 metric 20 ... xrouter 10.20.5.135 metric 20 # birdc show ospf state ospf_allroutes area 0.0.0.30 router 10.255.10.128 distance 0 external 10.20.5.135/32 metric2 16777215

3 2

OSPF authentication supported for IPv6 / OSPFv3?
by Cybertinus 05 Mar '19

05 Mar '19

Hello Bird users, I'm trying to get authentication enabled on my OSPF sessions. I'm running Bird 1.6.4 on Debian 9.8. I have the following config in my ospf.conf: protocol ospf ospf1 { import filter only_loopbacks; export filter only_loopbacks; area 0.0.0.0 { interface "lo"; interface "eno1" { type pointopoint; bfd on; }; interface "eno2" { type pointopoint; bfd on; }; interface "eno3" { type pointopoint; bfd on; authentication cryptographic; password "Test123"; }; }; } I include this ospf.conf in both bird.conf and bird6.conf. For IPv4 Bird it works without an issue and the sessions (over eno3) are authenticated. For IPv6 I see the following error when I try to load the config: # birdc6 configure check BIRD 1.6.4 ready. Reading configuration from /etc/bird/bird6.conf /etc/bird/ospf.conf, line 17: Authentication not supported in OSPFv3 When I check https://bird.network.cz/?get_doc&v=16&f=bird-6.html#ss6.8 I see the following: "authentication cryptographic An authentication code is appended to every packet. The specific cryptographic algorithm is selected by option algorithm for each key. The default cryptographic algorithm for OSPFv2 keys is Keyed-MD5 and for OSPFv3 keys is HMAC-SHA-256. Passwords are not sent open via network, so this mechanism is quite secure. Packets can still be read by an attacker." So, I think it should work for IPv6 too. What am I doing wrong? Or did I hit a bug of some kind? Kind regards, Cybertinus

2 2

BGP Graceful Restart
by Derek Pan 04 Mar '19

04 Mar '19

Hi >From the post https://bird.network.cz/pipermail/bird-users/2016-December/010760.html I understood that it should use kill -9 to stop and restart BIRD process to trigger graceful restart function. But I still have a question: Suppose in one BIRD process, there are more than two BGP protocol instances and OSPF protocol instances, And there are some BGP instances without graceful restart. Once I stop the BIRD process using kill -9 and then start it, I know those BGP instances with graceful restart would work fine But the others BGP instances without graceful restart would just be restarted. But this is not my expect behavior (I expect the others BGP and OSPF protocols would not be touched). Is there any command to just restart only one BGP instance and to trigger the graceful restart function? Thanks.

1 0

Bird2.0.4 - make errors
by Tiago Felipe Goncalves 01 Mar '19

01 Mar '19

Hi, I'm trying to compile bird204 for test purpose, but I'm facing some errors, anyone have an idea? BIRD was configured with the following options: Source directory: . Object directory: obj Iproute2 directory: /etc/iproute2 System configuration: ./sysdep/cf/linux.h Debugging: no POSIX threads: yes Routing protocols: bgp pipe rpki Kernel MPLS support: no Client: yes root@lab-rs:~/bird# make MKDIR -p obj/client obj/conf obj/doc obj/filter obj/lib obj/nest obj/test obj/proto/bgp obj/proto/pipe obj/proto/rpki obj/sysdep/linux obj/sysdep/unix obj/doc m4 -s -P conf/gen_parser.m4 conf/confbase.Y conf/flowspec.Y obj/.dir-stamp filter/config.Y nest/config.Y proto/bgp/config.Y proto/pipe/config.Y proto/rpki/config.Y sysdep/linux/netlink.Y sysdep/unix/config.Y sysdep/unix/krt.Y >obj/conf/cf-parse.y bison -Dparse.lac=full -Dparse.error=verbose -dv -pcf_ -b obj/conf/cf-parse obj/conf/cf-parse.y conf/gen_parser.m4: warning: 11 nonterminals useless in grammar [-Wother] conf/gen_parser.m4: warning: 34 rules useless in grammar [-Wother] conf/confbase.Y:90.13-29: warning: nonterminal useless in grammar: label_stack_start [-Wother] %type <mls> label_stack_start label_stack ^^^^^^^^^^^^^^^^^ conf/confbase.Y:90.31-41: warning: nonterminal useless in grammar: label_stack [-Wother] %type <mls> label_stack_start label_stack ^^^^^^^^^^^ conf/confbase.Y:86.22-25: warning: nonterminal useless in grammar: time [-Wother] %type <time> expr_us time ^^^^ nest/config.Y:94.162-164: warning: nonterminal useless in grammar: tos [-Wother] %nonassoc PREFIX_DUMMY ^^^ nest/config.Y:440.1-13: warning: nonterminal useless in grammar: password_list [-Wother] []s

3 3

show route output explained
by Eugene M. Zheganin 01 Mar '19

01 Mar '19

Hello, Since the documentation doesn't specify the exact output format, could anyone please explain it to me ? 0.0.0.0/0 via 192.168.57.60 on re0 [ospfv4 11:17:31] ! E2 (150/10/10000) [192.168.100.254] via 90.150.180.20 on ng0 [kernel1 11:12:08] (10) I understand most of it, but not in detail. 1) What, for example, the exclamation mark means ? Bird mimics Juniper notation, but Juniper doesn't have exclamation mark in it, only +/-/*. (Since bird mimics the Juniper notation it would be cool if it would also print the mark meanings, like JunOS or Cisco IOS does) 2) What is the triplet (150/10/10000) ? I understand these are probably metric/cost/preference, but which is what ? Juniper here uses single metric. 3) When it comes to internal OSPF area, this field output changes to double-field one: 192.168.57.0/24 dev re0 [direct1 11:12:08] * (240) dev re0 [ospfv4 11:17:31] I (150/10) [192.168.100.254] again, which field in (150/10) is what ? Thanks.

3 2

Routes counting
by Miłosz Oller 01 Mar '19

01 Mar '19

Hello, Bird 2.0.3 from source, Debian 9. Sometimes I see very huge numbers of exported routes: Description: Lipka IPv4 BGP state: Established Neighbor address: 185.212.67.245 Neighbor AS: 205604 Neighbor ID: 185.212.64.1 Local capabilities Multiprotocol AF announced: ipv4 Route refresh Graceful restart 4-octet AS numbers Enhanced refresh Long-lived graceful restart Neighbor capabilities Multiprotocol AF announced: ipv4 Route refresh 4-octet AS numbers Session: external AS4 Source address: 185.212.67.246 Hold timer: 167.076/180 Keepalive timer: 22.324/60 Channel ipv4 State: UP Table: master4 Preference: 100 Input filter: ACCEPT Output filter: ACCEPT Routes: 756702 imported, 4294390282 exported But it should be max ca 756000. When I restart session several times, I see correct number of routes. Is it a bug or feature? :) -- Miłosz

5 9

BIRD 2.0.4 and 1.6.6
by Ondrej Filip 01 Mar '19

01 Mar '19

Dear BIRD users, we just released two new versions - 1.6.6 and 2.0.4. Many thanks mainly to Santiago and Maria! Version 1.6.6 o Several bugfixes related to route propagation Version 2.0.4 o OSPF: Opaque LSAs (RFC 5250) o OSPF: DN-bit handling (RFC 4576) o Preferred route counters are back o Important BGP bugfix o Several bugfixes related to route propagation o some minor bugfixes Cheers! Ondrej

1 0