Re: [mpls-linux-devel] [quagga-dev 5315] Help with bgp_mplsvpn
Status: Beta
Brought to you by:
jleu
From: Zaida V. <za...@gm...> - 2008-08-05 12:32:24
|
Hi, I know it's a long time but I'm still alive and working :) I have been looking at Quagga_0.99.9's code to try to understand what's done and what isn't. Till now I see that even thought there's "support" for vpnv4 address family in BGP (RD, capabilities negotiation, NLRI parsing, etc.) all that information stays in bgpd and zebra doesn't know anything about it (am I right? If not pliz tell me) So we need to make zebra aware of all that's happening above to tell the kernel about it (with netlink). I'm also installing the Quagga patch por VRF-linux in order to see how it works.(I'm having some minor troubles doing it, as I haven't been able to comunicate with the vrfd daemon it comes with. But I hope to solve them) I intend to update it and integrate it with the above. In the mail you (James) sent me you talked about ''tags' received via BGP'. As far as I know this tags refer to the VPN label, don't they? This week I'll be on holidays, but when I come back I think I'll be ready to make some debugging as you suggested and to design a simple label manager for zebra. I would be thankfull if any of you would advise me about anything else I could be missing or should take into account. I know I'm not beeing very specific, hope you'll forgive my english =) Thank you in advance :) On Thu, May 1, 2008 at 4:12 AM, James R. Leu <jl...@mi...> wrote: > Hello Zaida, > > As you know Jon Ander ported the linux-vrf code to a more > recent kernel. Hey sent me the results of his work and I > started the process of integrating it into the linux-vrf project. > During that effort I learned about a project being integrated into > the linux 2.6.25 kernel. It is called network namespaces which basically > as VRF functionality across all aspect of the linux networking stack. > So the focus of the linux-vrf project is changing, I'm re-tooling to > add VRF functionality to quagga. > > It sounds like you are not necessarily interested in VRF interaction > with quagga, but your trying to work on the distribution of labels > regardless of what family the NLRI belong to. I recently added code > to quagga that will make install NHLFE and try to install FTN mappings > for 'tags' received via BGP. The only way to access this recent code > is from my my development tree via p4 (perforce). I suggest you > pull a p4 client for quagga-mpls and ldp-portable so you can see the > updates I've been working on. > > To start your work, I think you will want to design a CLI > indicating what NLRI should have 'tags' sent along. Part of this > will be to build your own trivial label manager (maybe just allow > configuration of a label range per BGP peer). Don't get to fancy, > because one area I'm working on is a proper label manager that > will live in the zebra daemon. Part of the work of the label > manager will be to add the ILM entries to the kernel before sending the > NLRI update containing the corresponding tag. In theory the receive > side should already work because of the code I put in place, of course you > may have to do some debugging :-) > > Once you are that far then you can help me with the next problem area. > hierarchical labels! MPLS linux supports them, I just have to figure out > the logic of when a recursive lookup that contains a label results in > hierarchy. > > I'm getting way ahead of myself ... > Get the code from my dev tree, start poking around the BGP code looking > for MPLS stuff, and then we can start talking about the MPLS > infrastructure. > > |