RIP multicast is receiving, but can't transmit
Stéphan Kochen
stephan at kochen.nl
Fri Jun 11 13:28:55 CEST 2010
Hello!
I'm setting up a test environment with Ubuntu 10.04 and BIRD 1.2.3 from
the PPA. First step was to try and get a simple static route announced
with RIP. This is the small test configuration I'm working with:
> log stderr all; debug protocols all;
> router id 10.2.2.1;
>
> protocol device { scan time 10; }
> protocol kernel { export all; import none; }
>
> protocol static { route 10.5.5.0/24 via 10.2.2.2; }
>
> protocol rip {
> interface "eth0" { mode multicast; };
> export all; import all;
> }
With this set-up, the static route is imported, and exported to the
kernel and RIP protocols as expected:
> 11-06-2010 13:18:19 <TRACE> kernel1 < added 10.5.5.0/24 via 10.2.2.2 on eth1
> 11-06-2010 13:18:19 <TRACE> rip1 < added 10.5.5.0/24 via 10.2.2.2 on eth1
> 11-06-2010 13:18:19 <TRACE> kernel1: 10.5.5.0/24: reinstalling
There's a Quagga ripd in the network announcing another route for a
subnet that lives inside a VLAN. It's picked up by the RIP protocol:
> 11-06-2010 13:18:19 <TRACE> rip1: block: 192.168.123.6 tells me: 10.123.16.0/20 available, metric 1...
> 11-06-2010 13:18:19 <TRACE> rip1 > added [best] 10.123.16.0/20 via 192.168.123.6 on eth0
> 11-06-2010 13:18:19 <TRACE> kernel1 < added 10.123.16.0/20 via 192.168.123.6 on eth0
> 11-06-2010 13:18:19 <TRACE> rip1 < forced accept by protocol 10.123.16.0/20 via 192.168.123.6 on eth0
> 11-06-2010 13:18:19 <TRACE> rip1 < added 10.123.16.0/20 via 192.168.123.6 on eth0
But BIRD is unable to transmit the static route I created. The RIP
protocol seems to know about the route, as indicated above, but when it
tries to transmit, I get:
> 11-06-2010 13:18:29 <TRACE> rip1: Broadcasting routing table to eth0
> 11-06-2010 13:18:29 <ERR> rip1: Unexpected error at rip transmit: Invalid argument
> 11-06-2010 13:18:29 <ERR> rip1: Unexpected error at rip transmit: Unknown error 18446744073709551615
The code is littered with DBG statements that I cannot seem to enable
in the output. I tried a manual build with --enable-debug, and I'm
running bird in the foreground with -d, but I'm still not seeing them.
What is the proper way to get to this information?
And is there something simple I'm missing to get RIP to work?
Thanks in advance,
-- Stéphan Kochen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20100611/24b373b8/attachment.asc>
More information about the Bird-users
mailing list