Interesting. Did you happen to test installing the route (in our case default route from OSPF) to the kernel routing table from OSPF? -bn 0216331C On Fri, May 24, 2013 at 1:44 AM, Ondrej Zajicek <santiago@crfreenet.org>wrote:
On Thu, May 23, 2013 at 11:57:07AM +0200, Ondrej Zajicek wrote:
On Wed, May 22, 2013 at 10:29:49AM -0700, Bao Nguyen wrote:
Ondrej,
You are correct, the issue is not related to OSPF but related to BIRD's ability to install a route into the kernel routing table. It look like the issue was that the new kernel doesn't have this option enabled (which is hidden under the Kernel Wireless options)
CONFIG_COMPAT_NETLINK_MESSAGES=y
Well, this is a bit strange because this option is here since 2.6.32 and it works for me with both 2.6.32 and 3.0 without this option. I would check it with 3.8 to see if i get the same problem.
Hello
Tested with 3.9.2 and worked for me with COMPAT_NETLINK_MESSAGES disabled, so it is probably some different problem.
-- 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."
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAlGfKHQACgkQw1GB2RHercPKRgCeKBdc0udLJtVuEB3EyFj8h3Li 5RgAmgNbGMJXIVhHQ5MzIiESa70n9yCw =cORf -----END PGP SIGNATURE-----