On 2020-10-20, Bastien Durel <bast...@durel.org> wrote: > Le lundi 19 octobre 2020 à 17:17 +0100, Tom Smyth a écrit : >> Hi Bastien, > Hello > >> can you do a >> route show -n |grep 10\.42 > > Boot time: > > default 10.42.42.1 UGS 5 5 - 8 em0 > 10.42.2/24 10.42.42.21 UGS 0 0 - 8 em0 > 10.42.42/24 10.42.42.69 UCn 3 0 - 4 em0
so here you have 10.42.42/24 directly connected > 10.42.42.1 40:62:31:01:4b:66 UHLch 1 2 - 3 em0 > 10.42.42.3 d0:50:99:18:63:82 UHLc 1 4 - L 3 em0 > 10.42.42.21 link#1 UHLch 1 2 - 3 em0 > 10.42.42.69 08:00:27:d6:6e:dd UHLl 0 2 - 1 em0 > 10.42.42.255 10.42.42.69 UHb 0 12 - 1 em0 > > After bird is started : > > > default 10.42.42.1 UGS 5 6 - 8 em0 > 10.42.2/24 10.42.42.21 UGS 0 0 - 8 em0 > 10.42.42/24 10.42.42.69 U1 0 2 - 56 em0 > 10.42.42.69 08:00:27:d6:6e:dd UHLl 0 10 - 1 em0 > 10.42.42.255 10.42.42.69 UHb 0 14 - 1 em0 and here bird has overwritten it (the "prio 56" routes are a bit of a clue that it's likely to be added by bird; it doesn't understand openbsd's route priorities and just adds with the default priority which is 56) some way or other you'll need to stop it overriding your directly connected networks. I'm no expert in bird and when I've used it is has mostly not been handling the route table, only collecting BGP routes itself, but I would think you might be able to do that with a filter. >From the config you showed I'm not seeing anything that seems like a reason to use bird over the OSPF daemons in base; they are definitely preferred if possible because they were written with awareness of the rest of OpenBSD's network stack.
