Bird handles OpenBSD route priority differently
(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?
On Mon, Jan 21, 2019 at 02:58:19PM +0700, Igor Podlesny wrote:
(compared to native OSPF daemon.)
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.
Hi Yes, our BSD code does not handle kernel route priorities, i didn't even know there is such feature, it seems to be OpenBSD specific. Therefore, in your test case BIRD chooses one route arbitrarily. Should not be hard to implement this. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@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."
participants (2)
-
Igor Podlesny -
Ondrej Zajicek