Re: [mpls-linux-general] Setting up simple lab - how?
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-general] Setting up simple lab - how?
|
From: James R. L. <jl...@mi...> - 2011-02-08 03:02:48
|
Hey all, It is good to see discussions occurring. Last year about this time I made a plea for someone to step up and start maintaining the project. I had 3 people that started out very interested, but they've gone quiet. I'll be more then happy to help someone else start organizing the git repo or answer questions on the code. On Mon, Feb 07, 2011 at 03:02:21PM -0800, Scott Whyte wrote: > On 02/07/2011 09:25 AM, Adrian Popa wrote: > > Oh, sorry Steierlein - I misread the paper... I saw Google's logo and I > > thought somebody from google was working on it :) > > Its true that the OpenLSR project hosted on code.google.com is a system > integration project done by a very capable summer intern I had. Its > also true that I would love to be moving it forward onto current (x64) > kernel and quagga versions, but it seems the mpls-linux project > organization is in so much disarray that other OSes start to look more > interesting. In particular OpenBSD has support for LDP in their kernel. > > I'm very glad to hear that the code, including verilog, is found useful > by some. I'm actively working on better MPLS support in the NetFPGA > platform, if we could get mpls-linux a bit more organized with respect > to the code repository, I'm certain I could keep NetFPGA verilog updates > coming, in the interests of network research. > > -Scott > > > > > On Mon, Feb 7, 2011 at 6:13 PM, Steierlein Márton <st...@gm... > > <mailto:st...@gm...>> wrote: > > > > No, this is just a project hosted on Google code. Some students made > > major strides from the mpls-linux project, including a a hardware MPLS > > switch. The source code in verilog is even accessible. Such knowledge > > and codebase is priceless. > > > > Best regards, > > Márton > > > > 2011/2/7 Adrian Popa <adrian.popa.gh > > <http://adrian.popa.gh>@gmail.com <http://gmail.com>>: > > > Well, if google has started to work with mpls-linux I think it > > will breathe > > > new life into the project :) > > > > > > That's great news... > > > > > > On Mon, Feb 7, 2011 at 5:57 PM, Steierlein Márton > > <st...@gm... <mailto:st...@gm...>> wrote: > > >> > > >> Milos, > > >> > > >> Try this: > > >> > > >> > > >> > > http://www.nanog.org/meetings/nanog50/presentations/Monday/NANOG50.Talk17.swhyte_Opensource_LSR_Presentation.pdf > > >> > > >> There is a URL at the end of the slides. Follow the steps in the > > >> readme and disable sysctl table in the kernel. I also managed to > > >> install it on two debian systems. > > >> > > >> Unfortunately the sources are not up-to-date and the patch is a pain > > >> in the ass as well. > > >> > > >> If you need any help feel free to post your questions. > > >> > > >> Best regards, > > >> Márton > > >> > > >> 2011/2/7 Milos Vujkovic <fea...@gm... > > <mailto:fea...@gm...>>: > > >> > Hello everyone, > > >> > I am trying to give mpls-linux a test run in my VmWare lab. > > What I would > > >> > like to have running is this simple scenario: > > >> > host1 -- router1 -- router2 -- host2 , > > >> > where all nodes are Linux virtual machines, running Debian. > > However, I > > >> > am > > >> > having hard time finding any kind of documentation, support or > > >> > instructions > > >> > on how to perform this. Can someone point me to relevant place > > where I > > >> > could > > >> > get more help with this? > > >> > Thank you in advance, > > >> > Milos > > >> > > > >> > > > >> > > > ------------------------------------------------------------------------------ > > >> > The modern datacenter depends on network connectivity to access > > >> > resources > > >> > and provide services. The best practices for maximizing a physical > > >> > server's > > >> > connectivity to a physical network are well understood - see > > how these > > >> > rules translate into the virtual world? > > >> > http://p.sf.net/sfu/oracle-sfdevnlfb > > >> > _______________________________________________ > > >> > mpls-linux-general mailing list > > >> > mpl...@li... > > <mailto:mpl...@li...> > > >> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > >> > > > >> > > > >> > > >> > > >> > > ------------------------------------------------------------------------------ > > >> The modern datacenter depends on network connectivity to access > > resources > > >> and provide services. The best practices for maximizing a physical > > >> server's > > >> connectivity to a physical network are well understood - see how > > these > > >> rules translate into the virtual world? > > >> http://p.sf.net/sfu/oracle-sfdevnlfb > > >> _______________________________________________ > > >> mpls-linux-general mailing list > > >> mpl...@li... > > <mailto:mpl...@li...> > > >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > The modern datacenter depends on network connectivity to access resources > > and provide services. The best practices for maximizing a physical server's > > connectivity to a physical network are well understood - see how these > > rules translate into the virtual world? > > http://p.sf.net/sfu/oracle-sfdevnlfb > > > > > > > > _______________________________________________ > > mpls-linux-general mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > ------------------------------------------------------------------------------ > 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 -- James R. Leu jl...@mi... |
