mpls-linux-general Mailing List for MPLS for Linux (Page 2)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general — Mailing list for general discussion about MPLS for Linux
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(26) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(22) |
Feb
(19) |
Mar
(19) |
Apr
(45) |
May
(52) |
Jun
(101) |
Jul
(79) |
Aug
(24) |
Sep
(43) |
Oct
(54) |
Nov
(71) |
Dec
(53) |
| 2002 |
Jan
(111) |
Feb
(123) |
Mar
(67) |
Apr
(61) |
May
(75) |
Jun
(26) |
Jul
(36) |
Aug
(41) |
Sep
(79) |
Oct
(85) |
Nov
(58) |
Dec
(39) |
| 2003 |
Jan
(26) |
Feb
(61) |
Mar
(80) |
Apr
(56) |
May
(39) |
Jun
(44) |
Jul
(28) |
Aug
(25) |
Sep
(4) |
Oct
(20) |
Nov
(38) |
Dec
(9) |
| 2004 |
Jan
(14) |
Feb
(14) |
Mar
(68) |
Apr
(17) |
May
(45) |
Jun
(42) |
Jul
(41) |
Aug
(23) |
Sep
(46) |
Oct
(89) |
Nov
(55) |
Dec
(33) |
| 2005 |
Jan
(74) |
Feb
(39) |
Mar
(105) |
Apr
(96) |
May
(43) |
Jun
(48) |
Jul
(21) |
Aug
(22) |
Sep
(33) |
Oct
(28) |
Nov
(29) |
Dec
(81) |
| 2006 |
Jan
(37) |
Feb
(32) |
Mar
(147) |
Apr
(37) |
May
(33) |
Jun
(28) |
Jul
(15) |
Aug
(20) |
Sep
(15) |
Oct
(23) |
Nov
(30) |
Dec
(40) |
| 2007 |
Jan
(20) |
Feb
(24) |
Mar
(65) |
Apr
(69) |
May
(41) |
Jun
(53) |
Jul
(39) |
Aug
(76) |
Sep
(53) |
Oct
(43) |
Nov
(26) |
Dec
(24) |
| 2008 |
Jan
(19) |
Feb
(67) |
Mar
(91) |
Apr
(75) |
May
(47) |
Jun
(63) |
Jul
(68) |
Aug
(39) |
Sep
(44) |
Oct
(33) |
Nov
(62) |
Dec
(84) |
| 2009 |
Jan
(14) |
Feb
(39) |
Mar
(55) |
Apr
(63) |
May
(16) |
Jun
(9) |
Jul
(4) |
Aug
(6) |
Sep
(1) |
Oct
(2) |
Nov
(10) |
Dec
(5) |
| 2010 |
Jan
(3) |
Feb
(1) |
Mar
(5) |
Apr
(13) |
May
(4) |
Jun
(5) |
Jul
(2) |
Aug
(8) |
Sep
(6) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(21) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(6) |
Sep
|
Oct
|
Nov
(2) |
Dec
(6) |
| 2012 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(5) |
Aug
(3) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
|
From: kuldonk d. <ku...@ya...> - 2012-01-03 21:39:41
|
How are you getting on, lucky stiff? http://nymphea.ro/temc/anythings.php?imoxin=57 Tue, 3 Jan 2012 22:39:30 _________________________________ ", we considered the same seeds to be deficient in germinating power as soon as they began to yield only less than 45 per cent, of plants" (c) Paries wytwarzac |
|
From: Renato W. <ren...@gm...> - 2011-12-23 13:52:03
|
Hi Richard, I will provide new tarballs in the next few days and announce them in this list. I count on your patience =) Best Regards, Renato. 2011/12/23 <ma...@ri...>: > I am seeking mpls-linux/ldp-portable/quagga-mpls source as tarballs. > > According to a wiki page > (http://sourceforge.net/apps/mediawiki/mpls-linux/index.php?title=Main_Page), > the source tar balls can be found at http://mpls-linux.sf.net/source/ > . Unfortunately, following that link gives me an web "403" error and > indicates that directory indexing is disabled. That same error page > suggest I contact the projects' support resources, and this mailing > list is the top support resource. > > So, how can I get recent source tarballs? Can someone enable > directory indexing for the source directory? How does that source > differ from the git repository? > > Thanks much, > Richard -- Renato Westphal |
|
From: <ma...@ri...> - 2011-12-23 12:40:15
|
I am seeking mpls-linux/ldp-portable/quagga-mpls source as tarballs. According to a wiki page (http://sourceforge.net/apps/mediawiki/mpls-linux/index.php?title=Main_Page), the source tar balls can be found at http://mpls-linux.sf.net/source/ . Unfortunately, following that link gives me an web "403" error and indicates that directory indexing is disabled. That same error page suggest I contact the projects' support resources, and this mailing list is the top support resource. So, how can I get recent source tarballs? Can someone enable directory indexing for the source directory? How does that source differ from the git repository? Thanks much, Richard |
|
From: Ballu b. <dev...@gm...> - 2011-12-19 19:38:44
|
Hi all, I need some elp, I followed steps of "Renato Westphal" from thread link. http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTi%3DjAOyK1GyHrC9CEX9PQXnL4EgMaZa-LnWz0kqq%40mail.gmail.com&forum_name=mpls-linux-general I need is-is support in it and i think for this i have to use source code of quagga.i have to enable is-is. but i want to use the same .deb package of REnato Westphal. but in it is-is in not enabled. so guide me what i should do. any help or idea plz? Regards |
|
From: Ballu b. <dev...@gm...> - 2011-12-15 18:55:30
|
Hi all, I need some elp, I followed steps of "Renato Westphal" from thread link. http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTi%3DjAOyK1GyHrC9CEX9PQXnL4EgMaZa-LnWz0kqq%40mail.gmail.com&forum_name=mpls-linux-general I need is-is support in it and i think for this i have to use source code of quagga.i have to enable is-is. but i want to use the same .deb package of REnato Westphal. but in it is-is in not enabled. so guide me what i should do. any help or idea plz? Regards |
|
From: Igor M. <ig...@et...> - 2011-12-14 07:39:45
|
It's still active. You can try my source code: You can find it at: https://github.com/i-maravic/MPLS-Linux https://github.com/i-maravic/iproute2 BR IGor 2011/12/14 Reid Cheng <xin...@ci...>: > Hi Guys, > > Is this project still in development process ? or stale ? > > -- > Cheers, > > Reid > ----Bliss was it in that dawn to be alive. > +86 13842868250 (China) > +65 93754107 (Singapore) > > > ------------------------------------------------------------------------------ > Cloud Computing - Latest Buzzword or a Glimpse of the Future? > This paper surveys cloud computing today: What are the benefits? > Why are businesses embracing it? What are its payoffs and pitfalls? > http://www.accelacomm.com/jaw/sdnl/114/51425149/ > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > |
|
From: Reid C. <xin...@ci...> - 2011-12-14 03:16:30
|
Hi Guys, Is this project still in development process ? or stale ? -- Cheers, Reid ----Bliss was it in that dawn to be alive. +86 13842868250 (China) +65 93754107 (Singapore) |
|
From: kuldonk d. <ku...@ya...> - 2011-11-24 12:54:46
|
Dear Sir or Madam: http://www.cantortella.com/wp-admin/css/wm1pq.php?wocaFriendID=100 Thu, 24 Nov 2011 13:54:37 _________________________________ "She had great stores of pasteboard and coloured papers, to make boxes, and portfolios, and little pocket-books, and wallets of; and she had a paint-box, and pencils, and drawing-books, and portfolios of pictures and drawing lessons." (c) Kallye winsey |
|
From: Igor M. <ig...@et...> - 2011-11-20 11:36:08
|
Hi all, I put my code on git trees on GitHub. This are their sites: https://github.com/i-maravic/iproute2 https://github.com/i-maravic/MPLS-Linux Any feedback would be appreciated. @Jorge I didn't put you as one of the authors. If you wish to put you there, just say in which files I should put your name and how. BR Igor |
|
From: kuldonk d. <ku...@ya...> - 2011-08-24 04:08:27
|
2xa3qtz61f, k2xu2y. http://gamebot.org/blog/wp-content/themes/themorningafter/img/qhxe.html jlhcn5s 0agebq2t71g eta9sa7, d30emr1ka xmu3nbsr. 0valdo3 wndq3qjrf. |
|
From: Igor M. <ig...@et...> - 2011-08-22 14:32:16
|
Are there any developers here, which are engaged in developing RSVP-TE for quagga? I want to contribute to the development of the RSVP daemon and any help would be appreciated. BR Igor Maravić |
|
From: Renato W. <ren...@gm...> - 2011-08-16 21:18:55
|
Hello, James wrote a text about MPLS vs IPv4 performance a while ago (2007?). Please take a look above. "Why is MPLS Linux slower at forwarding packets then Linux's IPv4 stack? There are some misconceptions out their regarding the speed of MPLS vs IPv4 packet processing .... Back in the mid 90's the state-of-the-art in edge and core routing technology was processor based packet forwarding. At that same time the requirements for how per packet forwarding decisions were being made was getting more complicated. Edge and core routers were being asked to consider source and destination addresses, incoming and outgoing interfaces, as well as TCP/UDP port numbers. This forced router vendors to switch to some sort of "flow" or "hash" based look up to determine the forwarding treatment (next hop and/or queuing). As any CS major knows both flow and hash based look up schemes can suffer from high amounts of "key collisions" when 1000s of packet flows per second are being considered. This in essence change the look up depth from 32 bits to something greater then 32 bits depending on the technique and the amount of "key collisions". So per packet decisions making was becoming a bottle neck in the core of the network. Along came various "IP Switching" techniques and "tag switching" all of which contributed to MPLS. One of the benefits of MPLS at that time was that the complex decision making for forwarding treatment was done once before at "LSP setup time" and per packet processing would be a consistent 20 bit look up. If the state-of-the-art in packet forwarding has stood still, then MPLS would have been the savior of core routing, but in the time it took for MPLS to become a standard the world of packet forwarding was revolutionized by ASICs and FPGAs. These hardware based packet look up engines could do the complex look up required by core and edge routers faster then the pipes could transport the packets. So when people said "MPLS should be faster then IPv4 at packet processing" they were not referring to standard destination based IPv4 forwarding, they were talking about complex forwarding decision making. Theoretically standard IPv4 destination only processing has a worst case of 32 bits of look up and MPLS has a constant 20 bits of look up, not enough of a difference to show up in throughput tests. So if your comparison of MPLS Linux forwarding versus Linux IPv4 forward is only based on IPv4 destination look ups, you should not expect to see a performance benefit (in fact MPLS Linux forces all ILM keys into a 32 bit number, so it too is doing a 32 bit look up :-). That in combination with the fact that MPLS Linux has not under gone any sort of optimization and has enormous amount of debug/tracing code, while the Linux IPv4 stack has undergone years of optimization by some of the brightest minds in the world. I'm surprised that MPLS Linux has performed as well as it has in the tests results I've seen." 2011/8/16 Adrian Popa <adr...@gm...>: > Hello Topit, > > Make sure you disable debugging - I think it's still enabled by default. > With debugging on, you will get lousy performance, because it has to write a > lot of information to the logs. > > If memory serves me right, you need to do something like echo 0 > > /sys/net/mpls/debug (don't remember the path exactly). With debugging off > performance is about the same as regular IP. > > Cheers, > Adrian > > On Tue, Aug 16, 2011 at 1:06 AM, Topit <top...@ya...> wrote: >> >> Hi james and everybody, i am from indonesia and right now i am in the end >> of my final project but i got a problem with simple MPLS Network. my >> topology like below : >> http://i307.photobucket.com/albums/nn309/top_itlhox/Mpls.jpg >> I used Kernel-2.6.26.6-49.fc8.mpls.version 1.962.i686 on Fedora 8 as PC >> Router. >> >> for take a look THROUGHPUT on mpls network from client 1 to client 2, i >> used Iperf tool as generator TCP packet. >> iperf -c 192.168.1.1 >> ------------------------------------------------------------ >> Client connecting to 192.168.1.1, TCP port 5001 >> TCP window size: 8.00 KByte (default) >> ------------------------------------------------------------ >> [128] local 192.168.4.3 port 49176 connected with 192.168.1.1 port 5001 >> [ ID] Interval Transfer Bandwidth >> [128] 0.0-10.0 sec 5.29 MBytes 4.43 Mbits/sec >> The problem is Bandwidth result just 4.43 Mbits/sec, meanwhile the >> network using fast ethernet as LAN Card. Fast ethernet 100 mbps should be >> show Throughput value almost of 100 mbps. but i just got 4.43 Mbits/sec. a >> lot of simulation to get throughput is 80-90 mbps average. could you tell me >> what wrong with my case. >> >> i need your help soon. my lecturer gave me limit time to solve the >> problem. >> please.. >> i'll be waiting for the answer. >> Regard. >> Topit >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> uberSVN's rich system and user administration capabilities and model >> configuration take the hassle out of deploying and managing Subversion and >> the tools developers use with it. Learn more about uberSVN and get a free >> download at: http://p.sf.net/sfu/wandisco-dev2dev >> >> _______________________________________________ >> mpls-linux-general mailing list >> mpl...@li... >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general >> > > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > -- Renato Westphal |
|
From: Adrian P. <adr...@gm...> - 2011-08-16 05:46:42
|
Hello Topit, Make sure you disable debugging - I think it's still enabled by default. With debugging on, you will get lousy performance, because it has to write a lot of information to the logs. If memory serves me right, you need to do something like echo 0 > /sys/net/mpls/debug (don't remember the path exactly). With debugging off performance is about the same as regular IP. Cheers, Adrian On Tue, Aug 16, 2011 at 1:06 AM, Topit <top...@ya...> wrote: > Hi james and everybody, i am from indonesia and right now i am in the end > of my final project but i got a problem with simple MPLS Network. my > topology like below : > http://i307.photobucket.com/albums/nn309/top_itlhox/Mpls.jpg > > I used Kernel-2.6.26.6-49.fc8.mpls.version 1.962.i686 on Fedora 8 as PC > Router. > > for take a look THROUGHPUT on mpls network from client 1 to client 2, i > used Iperf tool as generator TCP packet. > iperf -c 192.168.1.1 > ------------------------------------------------------------ > Client connecting to 192.168.1.1, TCP port 5001 > TCP window size: 8.00 KByte (default) > ------------------------------------------------------------ > [128] local 192.168.4.3 port 49176 connected with 192.168.1.1 port 5001 > [ ID] Interval Transfer Bandwidth > [128] 0.0-10.0 sec 5.29 MBytes 4.43 Mbits/sec > > The problem is Bandwidth result just 4.43 Mbits/sec, meanwhile the > network using fast ethernet as LAN Card. Fast ethernet 100 mbps should be > show Throughput value almost of 100 mbps. but i just got 4.43 Mbits/sec. a > lot of simulation to get throughput is 80-90 mbps average. could you tell me > what wrong with my case. > > i need your help soon. my lecturer gave me limit time to solve the problem. > > please.. > > i'll be waiting for the answer. > > Regard. > > Topit > > > > > > > > > > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > |
|
From: Topit <top...@ya...> - 2011-08-15 22:06:14
|
Hi james and everybody, i am from indonesia and right now i am in the end of my final project but i got a problem with simple MPLS Network. my topology like below : http://i307.photobucket.com/albums/nn309/top_itlhox/Mpls.jpg I used Kernel-2.6.26.6-49.fc8.mpls.version 1.962.i686 on Fedora 8 as PC Router. for take a look THROUGHPUT on mpls network from client 1 to client 2, i used Iperf tool as generator TCP packet. iperf -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 8.00 KByte (default) ------------------------------------------------------------ [128] local 192.168.4.3 port 49176 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [128] 0.0-10.0 sec 5.29 MBytes 4.43 Mbits/sec The problem is Bandwidth result just 4.43 Mbits/sec, meanwhile the network using fast ethernet as LAN Card. Fast ethernet 100 mbps should be show Throughput value almost of 100 mbps. but i just got 4.43 Mbits/sec. a lot of simulation to get throughput is 80-90 mbps average. could you tell me what wrong with my case. i need your help soon. my lecturer gave me limit time to solve the problem. please.. i'll be waiting for the answer. Regard. Topit |
|
From: Renato W. <ren...@gm...> - 2011-08-10 17:59:50
|
Hello Jan, Thank you for your bug report. This bug have been fixed, please try the new patches available on the mpls-linux project page at SourceForge. Best Regards, Renato. 2011/7/7 <ja...@in...>: > Dear subscribers, > > I have a problem setting up the first IPv4 over MPLS example. > > the command: > "mpls nhlfe add key 0 instructions push gen 1000 nexthop eth2 ipv4 ...." > > gives the output: > "NHLFE entry key 0x00000002 mtu 65535 propagate_ttl > (0 bytes, 0 pkts)*" ^^^^^^^^^^^^^^ > > > Information about the components: > -------------------------------- > > 1. mpls-linux version: 1.971 > > 2. patched linux-source: linux-source-2.6.32, 2.6.32-34squeeze1 > dmesg | grep MPLS > MPLS: version 1.971 > MPLS: protocol driver interface - <jl...@mi...> > MPLS: IPv4 over MPLS support > > 3. iproute and iptables from: > http://www.inf.ufrgs.br/~rwestphal/mpls-linux/debian/lenny/ > iproute version: 1.4.8-3 > iptables version: 2.6.35-1 > > 4. Linux runs in a Virtual Machine from VmWare. > > > Effect > ------ > > After the next command from the example: > "ip route add 10.0.0.2/32 via 172.16.0.3 mpls 0x2" > > the load of the cpu goes up to 100% and Linux isnt responding anymore. > > > Perhaps someone has an idea how to solve this. > > > with best regards, > Jan > > > > > > > > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > -- Renato Westphal |
|
From: Sébastien C. <scr...@gm...> - 2011-07-24 15:57:03
|
Hello, I'm trying to build mpls support for debian squeeze and vyatta. I've been able to build clean patched packages for ppp, ebtables, iproute and iptables. I'm able to build the kernel with linux-kernel-v2.6.32.27.patch Unfortunately I'm unable to build kernel modules properly. Can you give me an hand to create mpls ready debian style kernel ? Moreover can you tell me how can I patch Quagga and Ldp-portable ? Note that I've use the git repository... Best regards |
|
From: <ja...@in...> - 2011-07-07 22:36:41
|
Dear subscribers,
I have a problem setting up the first IPv4 over MPLS example.
the command:
"mpls nhlfe add key 0 instructions push gen 1000 nexthop eth2 ipv4 ...."
gives the output:
"NHLFE entry key 0x00000002 mtu 65535 propagate_ttl
(0 bytes, 0 pkts)*" ^^^^^^^^^^^^^^
Information about the components:
--------------------------------
1. mpls-linux version: 1.971
2. patched linux-source: linux-source-2.6.32, 2.6.32-34squeeze1
dmesg | grep MPLS
MPLS: version 1.971
MPLS: protocol driver interface - <jl...@mi...>
MPLS: IPv4 over MPLS support
3. iproute and iptables from:
http://www.inf.ufrgs.br/~rwestphal/mpls-linux/debian/lenny/
iproute version: 1.4.8-3
iptables version: 2.6.35-1
4. Linux runs in a Virtual Machine from VmWare.
Effect
------
After the next command from the example:
"ip route add 10.0.0.2/32 via 172.16.0.3 mpls 0x2"
the load of the cpu goes up to 100% and Linux isnt responding anymore.
Perhaps someone has an idea how to solve this.
with best regards,
Jan
|
|
From: <ja...@in...> - 2011-07-07 22:36:40
|
Dear subscribers,
I have a problem setting up the first IPv4 over MPLS example.
the command:
"mpls nhlfe add key 0 instructions push gen 1000 nexthop eth2 ipv4 ...."
gives the output:
"NHLFE entry key 0x00000002 mtu 65535 propagate_ttl
(0 bytes, 0 pkts)*" ^^^^^^^^^^^^^^
Information about the components:
--------------------------------
1. mpls-linux version: 1.971
2. patched linux-source: linux-source-2.6.32, 2.6.32-34squeeze1
dmesg | grep MPLS
MPLS: version 1.971
MPLS: protocol driver interface - <jl...@mi...>
MPLS: IPv4 over MPLS support
3. iproute and iptables from:
http://www.inf.ufrgs.br/~rwestphal/mpls-linux/debian/lenny/
iproute version: 1.4.8-3
iptables version: 2.6.35-1
4. Linux runs in a Virtual Machine from VmWare.
Effect
------
After the next command from the example:
"ip route add 10.0.0.2/32 via 172.16.0.3 mpls 0x2"
the load of the cpu goes up to 100% and Linux isnt responding anymore.
Perhaps someone has an idea how to solve this.
with best regards,
Jan
|
|
From: Jonathan D. <im...@ya...> - 2011-03-31 19:11:39
|
Hi, I have to admit a degree of confusion regarding the current status of MPLS on Linux and the current direction. I'm hoping that someone can shed light on the following: 1) People appear to be running the existing code, that much is clear from postings to the list, but what exactly is the current status of the code? For example, what's the ratio of "old" code to code that's aware of kernel changes since the last major release? 2) There's lots of routers that would likely benefit from MPLS-awareness, but is the current thinking that this should go into each software router independently (eg: BIRD, Quagga, XORP, Click, etc) or to have it in the kernel with virtual circuits exposed as logical devices so that there's one implementation for all? 3) There are plenty of networking projects that involve MPLS in some way (Sourceforge alone has several) and others that are not really tied to MPLS but would likely be used by people using MPLS. If Linux-MPLS is below critical-mass, would it make sense to cobble together some sort of alliance between projects to get momentum and interest up a bit? 4) I saw comments along the lines of other OS kernels being more interesting at the moment, but by-and-large the differences between kernels are abstraction details. The protocol doesn't change, the logic of passing packets is independent of the exact struct used for a packet (or indeed an interface), so unless the code is going to be rewritten as an netfilter/nftables module, you've two entirely distinct problems - interfacing with the OS and doing something useful. (Which is why portable software routers are possible at all.) Does the change in OS direction indicate that the split between the problems needs revisiting? |
|
From: Renato W. <ren...@gm...> - 2011-02-28 21:08:09
|
Hello, You'll also need to patch the iproute2 utility. You can find the instructions here: http://mpls-linux.git.sourceforge.net/git/gitweb.cgi?p=mpls-linux/mpls-linux;a=blob;f=QUICK.START;h=4707c3a9bf4d710e149b87a55466de318d23fe69;hb=3055a77b0a44345231a7e5df7c5ce193e3b70bfa If you're a Debian Lenny user, you can avoid the patches and install the debs from here: http://www.inf.ufrgs.br/~rwestphal/mpls-linux/debian/lenny/ Kind regards, Renato. 2011/2/26 lili lili <lit...@gm...>: > Hello, > > I succeed to install mpls-linux version 1.971, but i can't have an LSP to be > fonctionnal. > > After configuring my interfaces like the example in "sourceforge site", i > have this output when i do "ip route show": > > # ip route add 10.0.2.1 via 10.0.2.1 eth1 > > I don't have something as "mpls 0x2" > > Can any body help me? > > Thanks. > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT > data > generated by your applications, servers and devices whether physical, > virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > -- Renato Westphal |
|
From: lili l. <lit...@gm...> - 2011-02-26 21:03:23
|
Hello, I succeed to install mpls-linux version 1.971, but i can't have an LSP to be fonctionnal. After configuring my interfaces like the example in "sourceforge site", i have this output when i do "ip route show": * # ip route add 10.0.2.1 via 10.0.2.1 eth1* *I don't have something as "mpls 0x2"* Can any body help me? Thanks. |
|
From: Renato W. <ren...@gm...> - 2011-02-16 04:03:40
|
Milos, You can grab the debs from here: http://www.inf.ufrgs.br/~rwestphal/mpls-linux/debian/lenny/ You should be able to install them with "sudo dpkg -i file.deb". The kernel package contains only what is necessary for basic MPLS forwarding. If you want a more complete kernel you must compile it yourself. Trust me, this is not so hard as you might think! To run Quagga with MPLS/LDP support there are some additional steps: # adduser quagga $ cd /usr/local/etc/ # cp zebra.conf.sample zebra.conf # cp ospfd.conf.sample ospfd.conf # cp bgpd.conf.sample bgpd.conf # cp ldpd.conf.sample ldpd.conf # chown quagga:quagga /usr/local/etc/ # chown quagga:quagga /var/run/ Please give me a feedback about these packages. Regards, Renato. 2011/2/9 Renato Westphal <ren...@gm...>: > @Milos Vujkovic > > I'll package up some debs for you as soon as I can, it may help other > people too. > > @Scott Whyte > > Your help would be greatly appreciated. You can ask for James to be > integrated into the project documentation on Sourceforge. > > Regards, > Renato. > > > 2011/2/9 Milos Vujkovic <fea...@gm...>: >> 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 >> >> > > > > -- > Renato Westphal > -- Renato Westphal |
|
From: Han C. <hjc...@gm...> - 2011-02-10 10:06:20
|
Dear MPLS-linux subscribers, @James Good to hear you have some time again. Could you update the project wiki, so ppl don't lose time using outdated links and are unable to find the latest and the greatest. == @Renato What subversion of the 2.6.35 kernel are you porting to (or have done so)? I was trying to get the stock kernel of Fedora 14 patched for MPLS, but started with the 2.6.32.16 kernel first as documented in the OpenLSR project tarfile. Status: not a working environment yet, due to other tasks. == Generic question: Can we agree on a FC14 (i686 for now; i686 and x86_64 both later) port as a next standard platform? I don't care to task myself with the RPM creation. I even like to create a DomU kernel RPM for ppl like me who use Xen (Citrix Xenserver 5.6-FP1 in my case) for their testing/lab-bing. (respondants, plz mention wich Xen based product you use/prefer; This includes Hyper-V). == @Scott Upstream integration should be achieved as soon as possible, but at the right time. Maybe some tools can already be submitted for upstream integration. Kernel integration would be very important IMHO. Regards, Han Coumans |
|
From: Renato W. <ren...@gm...> - 2011-02-09 19:41:55
|
@Milos Vujkovic I'll package up some debs for you as soon as I can, it may help other people too. @Scott Whyte Your help would be greatly appreciated. You can ask for James to be integrated into the project documentation on Sourceforge. Regards, Renato. 2011/2/9 Milos Vujkovic <fea...@gm...>: > 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 > > -- Renato Westphal |
|
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 > |
533 messages has been excluded from this view by a project administrator.
