BIRD <-> Quagga Compatiblity

[Ondrej Filip]

Vonlanthen, Elmar wrote:
> Hello

Hello!

> 
> At the moment, I do some tests with BIRD. We would like to replace our
> currently used routing daemon Quagga with this piece of software.
> 
> My first impressions are very good. There are lot of features, which are
> missing in Quagga. And the design is much better.
> 
> I do some tests with OSPF in the following configuration:
> 
> 172.16.101.0/24 -- router/gw 1 -- 10.254.1.4 --- P-t-P --- 10.254.4.1 --
> router/gw 4 -- 172.16.104.0/24
> 

There are two problems I notice:

1) Bird thinks that the P-t-P interfaces are unnumbered. I am not sure 
whether this is correct. Could you please send me: "show interfaces" 
and "show ospf interface" ?

2) I guess that Quagga has a bug in routing table calculation if the 
network contains unnumbered P-t-P interfaces. We can me a workaround: 
Bird will send the interface as numbered.

I prepared a quick and dirty solution (and I didn't test it!). Try to 
apply the attached patch. It is definitely wrong way, but it may solve 
your case. Let me know, if this helps.

			Ondrej

> The complete setup is much more complicated. The Point-to-Point
> Connection is made between two GRE Interfaces with multicast enabled.
> The GRE interfaces have a tunnel over an Ipsec transport connection.
> There are 4 Tunnels between these two routers (two "wan" links for each
> site), but only tunnel linkA to linkA is up (like above).
> The gre tunnel ist working. Both routing daemons can talk together.
> 
> On both routers/gateways I can switch between Quagga and Bird.
> The OS on the routers is Debian Woody with Kernel 2.4.32.
> 
> My first test results:
> 
> Quagga - Quagga: Working fine (our currently productive setup).
> Bird - Bird: Working fine.
> 
> Quagga - Bird:
> 
> It is not working! But im not sure if the problem ist Quagga or Bird.
> Bird gets the routes from Quagga, but Quagga doesn't take the routes
> from Bird. But Bird is sending the packet with the routing information.
> 
> I have the following message in the quagga-ospfd logfile:
> 2007/05/25 08:12:05 OSPF: Route[External]: Calculate AS-external-LSA to
> 172.16.104.0/24
> 2007/05/25 08:12:05 OSPF: Route[External]: Can't find originating ASBR
> route
> 
> With quagga - quagga (which is working) I have the following log entry:
> 2007/05/25 08:06:08 OSPF: Route[External]: Calculate AS-external-LSA to
> 172.16.104.0/24
> 2007/05/25 08:06:08 OSPF: Route[External]: AS-external-LSA is MAXAGE
> 2007/05/25 08:06:08 OSPF: LSA[Type5,id(172.16.104.0),ar(172.16.104.1)]:
> MaxAge LSA remover scheduled.
> 
> The Quagga router of router 4 is listed in router 1 as border-router. If
> I replace the routing daemon in router 4 with Bird, it will not appear
> again as border-router.
>  
> Another strange thing is, that in the LSA Update packets from 10.254.4.1
> to 224.0.0.5, with Quagga I have the following data:
> Type: PTP
> Router ID: 172.16.101.1 (-> the difference!)
> Link Data: 10.254.4.1
> Link Type: 1 -Point-to-point connection to another router
> 
> In Bird the data looks like this:
> Type: PTP
> Router ID: 172.16.101.1
> Link Data: 0.0.0.60 (-> the difference!)
> Link Type: 1 -Point-to-point connection to another router
> 
> Is the link data field only informational?
> 
> Unfortunately it is necessary for us, that the communication between
> Bird and Quagga is working until everything is migrated to Bird.
> 
> As attachement you will find tcpdump output, quagga log files and the
> configuration files.
> 
> Please, let me know if there are some informations missing.
> 
> Thanks in advance.
> 
> Best regards
> Elmar
> 
> P.S. Sorry for my bad english :-(

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ifa-unn-wrong.patch
Type: text/x-patch
Size: 378 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20070526/f6e045c0/attachment-0001.bin>