Bird RIP does not send some packages

[Aleksey Chudov]

On 21.02.2013 1:46, Ondrej Filip wrote:
> I checked the code. And exactly what I was afraid happened. I was 
> surprised several times. :-( So I wrote a simple patch that sort of 
> solves the issue you have described. I put that patch into git 
> repository.However the current RIP implementation cannot handle any 
> shorter period than 12. It's because timers are triggered every 
> (period / 6) [+/- 1 sec]. And if there is no update, packets are sent 
> every 6th trigger. So I am sorry for this but this simple patch is all 
> I was able to produce here after quite busy and long day and dinner at 
> a hotel room. RIP code has to be cleaned but that will take some time. 
> Please let me know if this works. Ondrej

Thank you for such a quick response to the problem.

After applying the patch Bird started to send messages every 10-15 
seconds. At least it does so regularly. Is better than before :)

protocol rip {
     period 12;
     interface "gre*" { mode multicast; };
     export all;
}

16:27:42.937926 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:27:54.936797 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:28:07.938485 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:28:23.938492 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:28:38.936602 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:28:51.938484 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:29:03.936447 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:29:14.938487 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:29:29.408497 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:29:41.937292 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:29:53.937291 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:30:03.938237 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:30:18.402875 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:30:31.938027 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184
16:30:46.402386 IP 10.64.16.2.520 > 224.0.0.9.520: RIPv2, Response, 
length: 184


At best, I would like to set the following timeout values

protocol rip {
     period 1;
     timeout time 3;
     garbage time 5;
     interface "gre*" { mode multicast; };
     export all;
}

Is it realistic to implement such a feature?

Aleksey