bird 2.0.1: SIGSEGV in nexthop_size

[Ondrej Zajicek]

On Sun, Jan 28, 2018 at 06:39:46PM +0100, Svenne Krap wrote:
> Ok, I send you the files privately.
> 
> Svenne

Hi

The first attached patch (fix-nexthop.patch) should fix the crash.

But seems like there are some strange factors in your setup that
triggered the issue:

  jan 28 14:59:29 R1 bird[6648]: Next hop address 185.38.27.64 is a local
  address of iface bond0.3670

This means that BGP on R1 received a route with bgp_next_hop 185.38.27.64,
which is on R1.


There are also these messages:

  jan 28 14:59:14 R1 bird[6648]:         Assertion 'f->addr_type ==
  a->type' failed at nest/rt-fib.c:241
  jan 28 14:59:14 R1 bird[6648]:         Assertion 'f->addr_type ==
  a->type' failed at nest/rt-fib.c:204

Which are some other issue (likely some mixed-up IPv4 and IPv6).
Could you try to build and run BIRD with the second patch
(force-assert.patch)? That would case crash and core dump
on assert.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-nexthop.patch
Type: text/x-diff
Size: 1112 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180129/e5e5413e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: force-assert.patch
Type: text/x-diff
Size: 534 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180129/e5e5413e/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180129/e5e5413e/attachment.sig>