Bird to quagga interoperation

[Vonlanthen, Elmar]

> On Mon, Feb 09, 2009 at 02:27:20PM +0100, Vonlanthen, Elmar wrote:
> > > > In the thread "BIRD <-> Quagga Compatiblity" (started in
> > > May, 2007) I
> > > > have already posted some informations.
> > > > If you haven't access to the old thread, I could post the
> > > mails/infos
> > > > again.
> > > 
> > > Thank you for a hint, i found that thread.
> > > 
> > > > Is possible that Quagga does something wrong?
> > > 
> > > Perhaps Quagga has a different interpretation of some 
> terms in OSPF 
> > > RFC. There are Linux networking configurations (for example ptp 
> > > network addresses) that does not fit well to assumptions used in 
> > > OSPF RFC.
> > 
> > I have no problem to apply this little patch for every new release.
> > But what is the difference between these two lines?
> > 
> > 1.)ln->data = ifa->iface->index;
> > 
> > 2.)ln->data = ipa_to_u32(ifa->iface->addr->ip);
> 
> RFC expects that network link has either 'classical' IP 
> addresses from one subnet or are 'unnumbered'. The first line 
> is the rule for LSA data in a case of 'unnumbered' interface 
> and second line is the rule for 'classical' IP subnet 
> interface. Linux PtP addresses does not fit well to any of 
> these cases and Bird handles them as 'unnumbered'. Perhaps 
> Quagga handles them in a different manner and do some 
> consistency checking.
> 
> So i would like do some research about this issue and 
> probably communicate this with Quagga developers to have 
> consistent handling of Linux-specific network setting before 
> merging some changes to it.

Ok, many thanks in advance for your research.

Best regards
Elmar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5222 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20090210/e42d2cf2/attachment-0001.bin>