Re: [mpls-linux-general] Setting up simple lab - how?
Status: Beta
Brought to you by:
jleu
From: Milos V. <fea...@gm...> - 2011-02-09 15:21:45
|
Guys, thank you so much for your input regarding the lab setup. I will, however, have to whine a little more.. I have background with Cisco MPLS, with Linux in general is honestly not my best side. Even though links you provided me with would be useful to some Linux guru, I still find them really hard to follow. Is the a possibility of finding a more newbie-friendly guide on how to install this lab setup? Thank you, Milos On Wed, Feb 9, 2011 at 2:52 AM, Scott Whyte <sw...@go...> wrote: > On 02/07/11 19:45, Renato Westphal wrote: > > @Milos Vujkovic > > > > I also recommend you to start with the MPLS Labs from Adrian Popa. The > > only problem is that the kernel and tools used in those experiments > > are a bit old. If you want you may use that documentation but use the > > lastest MPLS code from Sourceforge (kernel 2.6.32 instead of kernel > > 2.6.15). The commands are the same and the MPLS Labs scripts should > > work. > > > > You can grab the lastest MPLS code with this command: > > git clone git:// > mpls-linux.git.sourceforge.net/gitroot/mpls-linux/mpls-linux > > > > Compile& install instructions (no rpms sorry ^^): > > > http://mpls-linux.git.sourceforge.net/git/gitweb.cgi?p=mpls-linux/mpls-linux;a=blob;f=QUICK.START;h=4707c3a9bf4d710e149b87a55466de318d23fe69;hb=3055a77b0a44345231a7e5df7c5ce193e3b70bfa > > > > > > @Scott Whyte > > > > I have to agree that the mpls-linux project is a disaster in terms of > > organization. The wiki is outdated and this mailing list is almost > > dead. > > > > The problem IMHO is the lack of contributors. When James decided to > > retire from the project I have offered myself to maintain the > > Quagga/MPLS integration and work in the LDP support. Some other people > > were named to maintain the kernel and the documentation. Since then > > the Quagga/MPLS integration got working and the LDP reached an usable > > state, working OK when acting in an ingress LSR. Now I'm working to > > port the OpenBSD LDP to Quagga/Linux. > > > > Since the others maintainers gone quiet, I ported myself the MPLS code > > to the newer versions of the upstream projects: iproute2-2.6.35, > > iptables-1.4.10, linux-2.6.32.27. I also ported the MPLS code to the > > kernel 2.6.35, which is the version that I'm currently using. However > > I'm not a kernel developer, this project needs a real kernel developer > > to keep improving the MPLS stack in the kernel. > > > > Renato, > > I appreciate all you have done for this project since James started > looking for people to hand off to. I was aware of his request for help, > but I never knew what the results were, so this organizational structure > is news. > > I would very much like to get this project integrated into its various > upstreams including the kernel, and also get the Quagga LDP code > integrated over there too. > > I'd like to offer help documenting the mpls-linux part, I can easily put > together a small lab to test interop with cisco and Juniper once we get > some repositories that build, or even a current set of patches if that's > the best place to start. > > -Scott > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > |