ERR when redistributing to OSPF NSSA

[Ondrej Zajicek]

On Thu, Sep 29, 2011 at 07:36:23PM +0400, Alexander V. Chernikov wrote:
> Okay, there is a small bug in bird preventing actual errors to come up.
> Patch attached.

Thanks for this one.

> Real error is: bird: ospf1: Cannot find forwarding address for NSSA-LSA
> 81.19.94.167/32
> 
> 
> Actual problem with redistribution resides in the following:
> when ospf comes up it interpretes all its active interfaces as
> interfaces with DOWN state. Interfaces with DOWN state are skipped on
> forwarding address lookup (we need to do this since P-bit is set).

Yes, you are right.

I think that a good quick fix is just allow to use addresses from
interfaces with DOWN state (patch attached). Note that in usual
circumstances on non-vlink iface the DOWN state is just transitional
and not really used - if real interface goes down, ospf interface is
removed.

BTW, there is a similar (but mostly harmless) bug not related to NSSA -
if an interface appears and there is a static route configured that goes
through that iface, the static protocol receives the iface notification and
generates the route, which is propagated to an ospf protocol before the
iface notification, so gw is not found and the route is propagated without
one.

-- 
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_nssa.patch
Type: text/x-diff
Size: 363 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20110929/7da3f11e/attachment-0001.patch>
-------------- 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/20110929/7da3f11e/attachment-0001.asc>