bird 1.4.3 ospfv3 issue on openbsd
Hi all, I just upgraded from 1.4.0 to 1.4.3 (compiled from -current ports) on OpenBSD 5.5, now OSPFv3 adjecencies don't establish any longer, they remain stuck in exstart. I saw a thread a while ago about IPv6 issues on FreeBSD with 1.4.1, maybe this is related but the bug fix does not work on OpenBSD? syslog is filled with these messages: Jun 23 15:34:14 dcg-1 bird6: ospf1: Socket error on bnx0: Invalid argument Jun 23 15:34:24 dcg-1 last message repeated 6 times Jun 23 15:34:24 dcg-1 bird6: ospf1: Socket error on bnx2: Invalid argument Jun 23 15:34:24 dcg-1 bird6: ospf1: Socket error on bnx0: Invalid argument Jun 23 15:34:28 dcg-1 last message repeated 3 times this is my config: [root@dcg-1 ~]# cat /etc/bird6.conf log syslog all; router id 94.142.247.1; protocol kernel { scan time 20; export all; } protocol device { scan time 2; } protocol direct { interface "lo1"; interface "bnx0"; interface "bnx2"; } protocol static { route 2a02:898::/32 blackhole; } filter only_loopbacks { if net ~ [ 2a02:898:0:300:0:0:0:0/64{128,128} ] then accept; reject; } protocol ospf ospf1 { tick 2; rfc1583compat yes; import filter only_loopbacks; export filter only_loopbacks; area 0.0.0.0 { interface "bnx0", "bnx2" { hello 10; retransmit 2; wait 10; dead 40; type pointopoint; }; }; } [root@dcg-1 ~]# birdc6 show ospf nei BIRD 1.4.3 ready. ospf1: Router ID Pri State DTime Interface Router IP 195.85.225.5 128 exstart/ptp 00:34 bnx0 fe80::21f:12ff:fe1c:3482 Kind regards, Job
Hi all, I've upgraded up and down to see when the issue was introduced: between 1.4.0 and 1.4.1. Ondrej, Martin, how can I help debug this? Would you like access to the machines? Kind regards, Job On Mon, Jun 23, 2014 at 04:02:25PM +0000, Job Snijders wrote:
Hi all,
I just upgraded from 1.4.0 to 1.4.3 (compiled from -current ports) on OpenBSD 5.5, now OSPFv3 adjecencies don't establish any longer, they remain stuck in exstart. I saw a thread a while ago about IPv6 issues on FreeBSD with 1.4.1, maybe this is related but the bug fix does not work on OpenBSD?
syslog is filled with these messages:
Jun 23 15:34:14 dcg-1 bird6: ospf1: Socket error on bnx0: Invalid argument Jun 23 15:34:24 dcg-1 last message repeated 6 times Jun 23 15:34:24 dcg-1 bird6: ospf1: Socket error on bnx2: Invalid argument Jun 23 15:34:24 dcg-1 bird6: ospf1: Socket error on bnx0: Invalid argument Jun 23 15:34:28 dcg-1 last message repeated 3 times
this is my config:
[root@dcg-1 ~]# cat /etc/bird6.conf log syslog all; router id 94.142.247.1; protocol kernel { scan time 20; export all; } protocol device { scan time 2; } protocol direct { interface "lo1"; interface "bnx0"; interface "bnx2"; } protocol static { route 2a02:898::/32 blackhole; } filter only_loopbacks { if net ~ [ 2a02:898:0:300:0:0:0:0/64{128,128} ] then accept; reject; } protocol ospf ospf1 { tick 2; rfc1583compat yes; import filter only_loopbacks; export filter only_loopbacks; area 0.0.0.0 { interface "bnx0", "bnx2" { hello 10; retransmit 2; wait 10; dead 40; type pointopoint; };
}; }
[root@dcg-1 ~]# birdc6 show ospf nei BIRD 1.4.3 ready. ospf1: Router ID Pri State DTime Interface Router IP 195.85.225.5 128 exstart/ptp 00:34 bnx0 fe80::21f:12ff:fe1c:3482
Kind regards,
Job
On Wed, Jun 25, 2014 at 11:25:23AM +0200, Job Snijders wrote:
Hi all,
I've upgraded up and down to see when the issue was introduced: between 1.4.0 and 1.4.1.
Using git bisect I've traced down the bug to this commit: https://gitlab.labs.nic.cz/labs/bird/commit/48e5f32db676645640f84ab3d630cce9... I do see some OpenBSD specific stuff in the commit, but I cannot decypher what could cause the problem, and the commit is quite large. Hope this helps. Kind regards, Job
On Wed, Jun 25, 2014 at 11:25:23AM +0200, Job Snijders wrote:
Hi all,
I've upgraded up and down to see when the issue was introduced: between 1.4.0 and 1.4.1.
Ondrej, Martin, how can I help debug this? Would you like access to the machines?
Hi There were significant changes in socket code in this version, but most of them were related to IPv4. I tested it on OpenBSD 4.5 and some NetBSD and everything worked, but it is possible that with some combinations of OS versions, configurations and interface types there are problems, esp. on systems with small coverage likeh NetBSD and OpenBSD. Access to the machines would be the best. -- 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)
-
Job Snijders -
Ondrej Zajicek