OSPF fails after birdc "configure"

[Roberto Moreda]

A quick update:

The error also appears using simple authentication. With only a few
nodes (two will suffice), and two quick "configure" commands, we can
fire a chain reaction: authentication errors, malformed packets,
signal 11, ...

I'll try to know something more with gdb...

Regards.

	Roberto

On Jul/18/2005, Roberto Moreda wrote:
> Hi!
> 
> Using bird for OSPF I've found that after two fast and consecutive
> configuration reloads (using birdc, command "configure") the md5 authentication
> fails, logging something like that:
> 
> 18-07-2005 16:21:16 <ERR> Bad OSPF packet from 192.168.1.20 -
> authentification failed
> 18-07-2005 16:21:16 <ERR> Bad OSPF packet from 192.168.2.20 -
> authentification failed
> ...
> 
> As side effect the bird process on other OSPF nodes die with signal 11 
> (!)
> 
> All works again if bird is restarted on the reconfigured node and on the
> others who died.
> 
> The password config section on the ospf protocol defined is something
> like:
> 
>                 ...
>                 interface "tun*" {
>                         authentication cryptographic;
>                         passwords { password "verysecretindeed"; };
>                 };
>                 ...
> 
> Do you any issues on stability of bird using birdc to reload configuration and
> such?
> 
> Thanks in advance.
> 
> 	Roberto
> 

-- 
Roberto Moreda
Allenta Consulting
UNIX, Linux & Security Services