[quagga-dev 5099] Re: [PATCH][RFC] Seperate common netlink code from rt_netlink

James R. Leu jleu at mindspring.com
Sun Oct 14 01:53:56 BST 2007

On Sat, Oct 13, 2007 at 10:55:57AM -0400, Greg Troxel wrote:
> I skimmed the patch and separating <talk netlink> from <get routing
> stuff over netlink> seems fine.
> So how does this all work on systems that don't use netlink?  Or is this
> just a cleanup within netlink, and the MPLS framework might or might
> require changes to kernel communication on other systems?

This patch is as you say "just a cleanup within netlink".  The MPLS
framework I've written does have a layer of indirection, just like the
route/interface/address communication does.  My implementation of MPLS
on Linux uses netlink for the kernel communication, but the layer
of indirection should be able to support any form of forwarding plane

My change to quagga to support MPLS can be retrieved at

> It's perfectly fine not to support other systems at first, but I think
> architectural cleanliness requires that there be a plan for any support
> to be multi-OS, ensuring that the approach and structure doesn't depend
> on one particular flavor's structure.  I don't mean to accuse you of not
> doing this, but I thought I'd raise the issue since your note was only
> about netlink.

James R. Leu
jleu at mindspring.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20071014/06e07647/attachment-0001.sig>

More information about the Quagga-dev mailing list