BIRD OSPF floods illegal LSA seq no 0x80000000 after premature aging

Ondrej Zajicek santiago at
Mon May 24 10:52:28 CEST 2010

On Sun, May 23, 2010 at 03:49:03PM +0200, Dennis Koegel wrote:
> On Sat, May 22, 2010 at 11:36:43AM +0200, Ondrej Zajicek wrote:
> > > we have reproducible case in the lab where BIRD's OSPF sends LSUPDs with
> > > illegal sequence number 0x80000000.
> > 
> > Which protocol created the route that was exported to the OSPF and
> > caused the problem in your case? And what change to bird.conf was made
> > (it was change to the OSPF or a change to the first protocol)?
> Changing the "interface" statement within "protocol direct" triggered
> the problem here. The routes also came from "direct", interface
> addresses actually.
> We'll try the current version from git when the checks are in,
> thank you!

I just commited that, you can try it.

OTOH, in most cases it is unreasonable to export interface addresses
from protocol 'direct' to OSPF. It is usually much better to just add
these interfaces as OSPF interfaces (possibly with 'stub yes' option)
and the OSPF protocol propagates their addresses itself (using stub
records in router-LSA).

Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3,
"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: <>

More information about the Bird-users mailing list