Bird RIP does not send some packages

[Aleksey Chudov]

Hello,

 

I ran into a situation that Bird RIP does not send some packages.

 

Bird configuration file /etc/bird.conf

 

log syslog all;

 

debug protocols all;

 

protocol device {

    scan time 5;

}

 

protocol direct {

    interface "*";

}

 

protocol kernel {

    persist;

    scan time 5;

    export filter {

        if source = RTS_RIP then {

            if rip_metric > 15 then reject;

            if net ~ 10.0.0.0/8 then accept;

            if net ~ 192.168.0.0/16 then accept;

        }

        reject;

    };

}

 

protocol rip {

    period 5;

    timeout time 20;

    garbage time 30;

    interface "gre*" { mode multicast; };

    export filter {

        if net ~ 10.64.0.0/20 then accept;

        reject;

    };

}

 

 

Log messages from Bird daemon

 

Feb 19 18:25:00 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:03 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:06 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:12 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:13 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:15 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:20 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:26 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:28 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:33 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:36 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:38 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:44 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:48 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:50 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:56 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:25:58 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:00 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:03 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:05 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:06 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:07 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:13 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:16 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:19 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:21 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:25 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:31 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:33 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:39 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:42 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:45 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:46 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:49 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:51 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:52 srvc1 bird: rip1: Broadcasting routing table to gre1

Feb 19 18:26:57 srvc1 bird: rip1: Broadcasting routing table to gre1

 

And tcpdump for the same period

 

18:25:00.479028 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
24

18:25:03.482132 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
184

18:25:15.639027 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
24

18:25:26.478329 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
184

18:25:48.476297 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
184

18:26:05.639030 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
184

18:26:13.473560 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
24

18:26:16.639029 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
24

18:26:21.473055 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
184

18:26:31.473049 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
24

18:26:33.472083 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
44

18:26:39.638030 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
24

18:26:45.471432 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
184

18:26:57.637236 IP 10.64.16.18.520 > 224.0.0.9.520: RIPv2, Response, length:
24

 

 

Are there any ideas why this is happening?

 

 

Best regards,

Aleksey

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20130219/e4543d01/attachment.html>