RIP authentication problem with cisco

[Damjan]

> I hope I'll roll out a new release in two weeks to get the things at
> least crawling if not moving :)

That will be nice,

I've had some problems with the BGP protocol in Bird. It's working good
most of the time, but sometimes when the BGP connection fails, and Bird
tries to reestablish the connection it will corrupt its settings (I
think)..

Look at the following log:
02-04-2003 12:23:52 <RMT> UUNET: Error: Hold timer expired
02-04-2003 12:23:52 <TRACE> UUNET: State changed to flush
02-04-2003 12:23:52 <TRACE> UUNET: State changed to down
02-04-2003 12:56:18 <TRACE> UUNET: Starting
02-04-2003 12:56:18 <TRACE> UUNET: State changed to start
02-04-2003 12:56:18 <ERR> UUNET: Invalid next hop 0.10.182.0

The BGP config is:
protocol bgp UUNET {
    debug { states, events };
    local as 16333;
    source address 217.16.69.57;
    multihop 40 via 146.188.54.185;
    neighbor 146.188.54.185 as 702;
...

Are there any fixes about this??




-- 
Damjan Georgievski