Another RIP problem...

[Pavel Machek]

Hi!

> Its getting late, or rather to say early now, and I am tracing
> sporadic dials on my setup. What I have seen so far is that they
> are caused by sporadic loss of the RIP route.
> 
> Sporadic in this case means always after timeout/garbage timer run.
> Debug says it kicks the route out because it is too old, and a couple second
> later it is back in, most likely from the next broadcast.
> Bird is getting the broadcasts. In "show route", said RIP route has an
> updated timestamp, and that one gets updated each time a broadcast happens
> and the bird log says > ignored ... (because its already there).
> 
> A quick examination of the source shows that in this "ignored" case,
> the lastmod timestamp gets updated, which is what show route shows.
> But the route gets cleaned out according to the lastmodX timer, which does not
> get updated. 
> 
> Is this a bug or is that mandated behaviour (which I doubt, since it is
> silly & causes routing instability...) ?

It is a bug. Fix is to use lastmod timer instead (in all places but
assignments; remove assignments). I'll commit fix to cvs in short time.
								Pavel
-- 
I'm pavel at ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents me at discuss at linmodems.org