1.1.3 segfaults on seeing certain routes

[Ondrej Zajicek]

On Mon, Sep 21, 2009 at 01:39:56PM +0200, KORN Andras wrote:
> Hi,
> 
> Background: I'm completely new to BIRD. I have five locations connected via
> OpenVPN in a full mesh, using Linux 2.6 routers, and I thought I'd try
> dynamic instead of static routing. At first I just wanted to see how/what
> BIRD would do, so I set it to use kernel routing table 3 which I don't use
> for policy routing. I copied the contents of my other routing tables into
> table 3 and fired up bird, which promptly segfaulted.

Just a remark - it is usually better idea to use static section in bird.conf
to configure static routes than to import alien routes from kernel. But both
variants should work.

> The following routes are sufficient (but maybe not all of them necessary) to
> reproduce the segfault:
> 
> # ip ro sh table 3
> 172.18.68.254 dev tap5  scope link  src 172.18.32.254 
> 10.10.107.0/24 via 172.18.68.254 dev tap5  src 172.18.32.254 
> 192.168.12.0/22 via 172.18.68.254 dev tap5  src 172.18.32.254 
> 172.18.64.0/20 via 172.18.68.254 dev tap5  src 172.18.32.254 

Could you send me shell commands that sets these routes?
It seems that problem is that BIRD does not properly import these routes
(and does not consider 172.18.68.254 as a neighbor).

> Additionally, when running with an empty table 3 on one of the neighbours of
> this router, it logged messages like:
> 
> 21-09-2009 12:55:08 <WARN> Received HELLO packet address (172.18.32.254) is inconsistent with the primary address of interface tap4.
> 
> It indeed is inconsistent, because all tap interfaces have the same address
> on each router (specific to the router, with a /32 mask)

BIRD expects that interface uses either 'standard' network address, or address
with /32 mask and specified peer address (configured with 'ip address add IP1
peer IP2 dev DEV' or similarly using ifconfig and pointopoint). In both cases
there should not be this warning as this warning means that Hello message was
ignored.

Is seems that you set up /32 peer routes in a different manner. Maybe we could
extend BIRD to handle such configuration.

-- 
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: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20090922/769c7c87/attachment-0001.asc>