mpls-linux-general Mailing List for MPLS for Linux (Page 148)
Status: Beta
Brought to you by:
jleu
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: James R. L. <jl...@mi...> - 2002-02-12 15:43:55
|
The patch for mpls-linux-1.0 is again linux kernel 2.4.13. Patching a 2.4.5 kernel may not work (as you're seeing). I'm copying instructions from the 'mini-howto' which was posted to the list. Although the mini-howto is for mpls-linux-1.1xx the kernel patching part is the same. MPLS Installation Guide Status MPLS for Linux comes as third-party addition. It means that fresh mainstream kernel does know nothing about MPLS protocol. To add MPLS support your need 1. patch your kernel 2. get and compile userland configuration utilities Note: MPLS is beta software! Compile Instruction 1. Change system headers cd /usr/include mv linux linux.old mv asm asm.old ln -s /usr/src/linux/include/linux linux ln -s /usr/src/linux/include/asm asm cd /usr/src rm linux 2. Get mpls-linux from SorceForge 3. Download kernel v2.4.13 to /usr/src. You can get it from http://www.kernel.org/pub/linux/kernel/v2.4/linux-2.4.13.tar.gz or nearest mirror cd /usr/src tar zxvf linux-2.4.13.tar.gz mv linux linux-2.4.13 ln -s linux-2.4.13 linux cd linux patch -p1 < /root/mpls-linux/patches/linux-mpls.diff make menuconfig under "Code maturity level options" turn on "Prompt for development and/or incomplete code/drivers" under "Networking Options" turn on "Kernel/User netlink socket" turn on " Routing messages" turn on "Multi-Protocol Label Switching" (do other kernel configuration) Then read QUICK.START utils/README.example for more info. Jim On Tue, Feb 12, 2002 at 07:22:03AM -0800, blue caddy wrote: > Hello, I'm trying to build a 2.4.5 linux kernel with > the mpls patch (1.0) applied. But I ran into the > following error. Can you help me out? > > make[3]: Entering directory > `/usr/src/linux-2.4.5/net/mpls' > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_if.o mpls_if.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_in_info.o mpls_in_info.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_init.o mpls_init.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_input.o mpls_input.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_ioctls.o mpls_ioctls.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_netlink.o mpls_netlink.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_opcode.o mpls_opcode.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_out_info.o mpls_out_info.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_output.o mpls_output.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_proc.o mpls_proc.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_ref.o mpls_ref.c > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_utils.o mpls_utils.c > mpls_utils.c: In function `mpls_instruction_build': > mpls_utils.c:136: warning: assignment makes integer > from pointer without a cast > gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall > -Wstrict-prototypes -O2 -f > omit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -marc > h=i586 -c -o mpls_tunnel.o mpls_tunnel.c > mpls_tunnel.c: In function `mpls_tunnel_init_gen': > mpls_tunnel.c:253: `ARPHRD_MPLS_TUNNEL' undeclared > (first use in this function) > mpls_tunnel.c:253: (Each undeclared identifier is > reported only once > mpls_tunnel.c:253: for each function it appears in.) > make[3]: *** [mpls_tunnel.o] Error 1 > make[3]: Leaving directory > `/usr/src/linux-2.4.5/net/mpls' > make[2]: *** [first_rule] Error 2 > make[2]: Leaving directory > `/usr/src/linux-2.4.5/net/mpls' > make[1]: *** [_subdir_mpls] Error 2 > make[1]: Leaving directory `/usr/src/linux-2.4.5/net' > make: *** [_dir_net] Error 2 > > __________________________________________________ > Do You Yahoo!? > Send FREE Valentine eCards with Yahoo! Greetings! > http://greetings.yahoo.com > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: blue c. <nom...@ya...> - 2002-02-12 15:22:05
|
Hello, I'm trying to build a 2.4.5 linux kernel with the mpls patch (1.0) applied. But I ran into the following error. Can you help me out? make[3]: Entering directory `/usr/src/linux-2.4.5/net/mpls' gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_if.o mpls_if.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_in_info.o mpls_in_info.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_init.o mpls_init.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_input.o mpls_input.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_ioctls.o mpls_ioctls.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_netlink.o mpls_netlink.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_opcode.o mpls_opcode.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_out_info.o mpls_out_info.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_output.o mpls_output.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_proc.o mpls_proc.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_ref.o mpls_ref.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_utils.o mpls_utils.c mpls_utils.c: In function `mpls_instruction_build': mpls_utils.c:136: warning: assignment makes integer from pointer without a cast gcc -D__KERNEL__ -I/usr/src/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -f omit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -marc h=i586 -c -o mpls_tunnel.o mpls_tunnel.c mpls_tunnel.c: In function `mpls_tunnel_init_gen': mpls_tunnel.c:253: `ARPHRD_MPLS_TUNNEL' undeclared (first use in this function) mpls_tunnel.c:253: (Each undeclared identifier is reported only once mpls_tunnel.c:253: for each function it appears in.) make[3]: *** [mpls_tunnel.o] Error 1 make[3]: Leaving directory `/usr/src/linux-2.4.5/net/mpls' make[2]: *** [first_rule] Error 2 make[2]: Leaving directory `/usr/src/linux-2.4.5/net/mpls' make[1]: *** [_subdir_mpls] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.5/net' make: *** [_dir_net] Error 2 __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com |
From: Abhijit G. <gab...@ee...> - 2002-02-12 06:16:19
|
Theorotically its simple. You won't run your LDP without any routing protocol(s). So as a result of exchange of routing messages and subsequent calculations, there will be routes added to new hosts/networks in the routing table. Since primary purpose of LDP is to create hop-by-hop LSPs, it will work with the routing table thus. Modifications to your routing table can generate necessary call-backs to your LDP implementation. (In LDP terminology, this is the new FEC.) If you are doing traffic engineering, there will be some CSPF algorithm (perhaps offline) working which will give u a constraint based path, now if you want to setup LSP for that, you would obviously require labels :-) . I recommend you to read rfc3031 and rfc3036 procedures to know more about it. there is also a FAQ maintained at mplsrc.com. You may have a look at that as well. hth, -abhijit jagdish Garg wrote : >Hi Experts >I have one small question on Downstream on demand . Who come to know there >is need for requesting a label , MPLS or LDP and how ? > > >Thanks in advance >Jagdish Garg -- How do u delete a letter in vi and paste it after the next one? "xp" -- |
From: jagdish G. <jag...@ie...> - 2002-02-12 04:51:04
|
Hi Experts I have one small question on Downstream on demand . Who come to know there is need for requesting a label , MPLS or LDP and how ? Thanks in advance Jagdish Garg |
From: James R. L. <jl...@mi...> - 2002-02-08 22:09:34
|
*sigh* You are correct. When I origianlly implemented mpls-linux the reason I stayed away from iptables was exactly this reason. For some reason when I was cosidering the move to iptables again, I completly ignored my "this doesn't feel right" sensation. I'm now regretting my change to iptables. ... but it is such a cleaner implementation then before ... I will see if there is any way to get iptable (netfilter) to do what I want (exact match in the FIB) otherwise I will have to add the FIB based FTN again. *sigh* Thank you for being the voice of reason .... Jim On Fri, Feb 08, 2002 at 01:44:54PM +0100, Yon Uriarte wrote: > Hello, > > I've just catched up some months list life. I see with concern that it > is no longer possible to bind a routing table entry to a label. > > Isn't the semantic of vanilla (ip routing table driven) ldp the longest > match selection? The FTN mib matches the iptables format almost perfectly > otherwise. But for longest match selection it is not very adequate. For > example, given the routing table > 1.1.1.0/24 > 1.2.0.0/16 > 1.0.0.0/8 > and a ldp mapping for 1.0.0.0/8 at least 3 iptables entries have to be > created: > -d 1.1.1.0/24 -j RETURN > -d 1.2.0.0/16 -j RETURN > -d 1.0.0.0/8 -j MPLS > > And I guess implementing this fec -> iptables behavior in the guts of the > ports will be kind of a pain. > > Or are my assumptions about semantics wrong? > > TIA, HAND > yon > > > > > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: Yon U. <hav...@gm...> - 2002-02-08 20:59:10
|
Hello, I've just catched up some months list life. I see with concern that it is no longer possible to bind a routing table entry to a label. Isn't the semantic of vanilla (ip routing table driven) ldp the longest match selection? The FTN mib matches the iptables format almost perfectly otherwise. But for longest match selection it is not very adequate. For example, given the routing table 1.1.1.0/24 1.2.0.0/16 1.0.0.0/8 and a ldp mapping for 1.0.0.0/8 at least 3 iptables entries have to be created: -d 1.1.1.0/24 -j RETURN -d 1.2.0.0/16 -j RETURN -d 1.0.0.0/8 -j MPLS And I guess implementing this fec -> iptables behavior in the guts of the ports will be kind of a pain. Or are my assumptions about semantics wrong? TIA, HAND yon |
From: James R. L. <jl...@mi...> - 2002-02-08 15:49:13
|
Hmmm. This is a prtty odd error. Something is going wrong in your kernel compile. The first thins I would try is to do a 'make clean vmlinux' and see if that helps. If that doesn't work, look thourgh linux/Documentation/ChangeLog and make sure you are running the correct version of gcc glibc binutiles etc. If that still doesn fix it, you mioght want to try searching the linux-kernel mailing list. Unfortunatly your failure is with something I have no clue about (the black magic involved in linking the kernel) Jim On Fri, Feb 08, 2002 at 04:29:25PM +0100, sj...@te... wrote: > > > Hi all, > > im not able to compile kernel 2.4.12 with the mpls patch applied, everytime i try to i get > this error : > > net/network.o \ > /usr/src/2.4.12/arch/i386/lib/lib.a /usr/src/2.4.12/lib/lib.a > /usr/src/2.4.12/arch/i386/lib/lib.a \ > --end-group \ > -o vmlinux > drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols in discarded > section .text.exit' > drivers/net/net.o(.data+0xbb4): undefined reference to `local symbols in discarded > section .text.exit' > make: *** [vmlinux] Error 1 > > > Anyone knows whats about ???? > The system is a pentium, with debian woody installed, i have read the docs and the mini > howto published on the list but its still broken . > > TIA > > Javier Sanchez > sj...@te... > > > > > > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: James R. L. <jl...@mi...> - 2002-02-08 15:45:39
|
Hello. First off I'd like to thank you for taking time to look at my work. Unfortunatly You have 2 things against you when it comes to ldp-portable. 1. I haven't had a chance to fully test or work on ldp-portable in about 8 months. I have no idea what does or doesn not work anymore. I hope to get back to working on ldp-portable soon. 2. LDP use multicast for sending hellos. ATM on Linux does not support sending multicast. You best bet at this point it to try and use the ldp_linux (not the zebra port) on ethernet interfaces and/or hack the ATM clip driver to allow you to sent multicast packets. Jim On Fri, Feb 08, 2002 at 10:02:28PM +0900, Katsuhiro SEBAYASHI wrote: > Hi, > > I'm trying to use ldp-portable zebra-port. But it dose not work on ATM > interface. > > Dose anyone make it work on ATM interface? > > K. Sebayashi > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: James R. L. <jl...@mi...> - 2002-02-08 15:41:08
|
On Fri, Feb 08, 2002 at 12:08:26PM -0000, Radu Dragos wrote: > Hi all. > I'm using mpls-linux-1.128 and linux-2.4.17 > > I can add a modifier using: > ./mplsadm2 -v -A -O gen:16:eth0:ipv4:IP > > ... but when i try to delete using: > ./mplsadm2 -v -D -O gen:16:eth0:ipv4:IP > > the entry in /proc/net/mpls_out remains unchanged. > > When I used the above commands in mpls-linux-0.996 everything was OK. > > Sugestions? mpls-linux-1.108 and above generate keys for the outgoing label info. Previously the key was the combination of "gen:16:eth0". This prohibited us from creating outgoing entries with the same label to differnt nexthops. So the only time up use the -O gen:<label>:<if> syntax is during the create. After that you should always use -O key:<key> syntax. You can get the key from /proc/net/mpls_out (it is also printed to STDOUT when the create succeeds.) You can also look at my post: http://www.geocrawler.com/lists/3/SourceForge/7968/0/7736459/ For more info. > Thanks in advance, > Radu > > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: <sj...@te...> - 2002-02-08 15:32:55
|
Hi all, im not able to compile kernel 2.4.12 with the mpls patch applied, everytime i try to i get this error : net/network.o \ /usr/src/2.4.12/arch/i386/lib/lib.a /usr/src/2.4.12/lib/lib.a /usr/src/2.4.12/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols in discarded section .text.exit' drivers/net/net.o(.data+0xbb4): undefined reference to `local symbols in discarded section .text.exit' make: *** [vmlinux] Error 1 Anyone knows whats about ???? The system is a pentium, with debian woody installed, i have read the docs and the mini howto published on the list but its still broken . TIA Javier Sanchez sj...@te... |
From: Katsuhiro S. <seb...@na...> - 2002-02-08 13:02:32
|
Hi, I'm trying to use ldp-portable zebra-port. But it dose not work on ATM interface. Dose anyone make it work on ATM interface? K. Sebayashi |
From: Radu D. <dr...@ee...> - 2002-02-08 12:07:38
|
Hi all. I'm using mpls-linux-1.128 and linux-2.4.17 I can add a modifier using: ./mplsadm2 -v -A -O gen:16:eth0:ipv4:IP ... but when i try to delete using: ./mplsadm2 -v -D -O gen:16:eth0:ipv4:IP the entry in /proc/net/mpls_out remains unchanged. When I used the above commands in mpls-linux-0.996 everything was OK. Sugestions? Thanks in advance, Radu |
From: clz <cui...@26...> - 2002-02-08 00:32:21
|
SGkhIEFsbC4NCihGaXJzdCBvZiBhbGwsIHNvcnJ5IGZvciBteSBlbmdsaXNoLi4uKQ0KSSBoYXZl IGluc3RhbGxlZCBsaW51eC1tcGxzLTAuOTk2ICBvdmVyIGxpbnV4IGtlcm5lbC4gaXQgc2VlbXMg DQp0byB3b3JrIHByb3Blcmx5LCBidXQgSSBoYXZlIHNvbWUgcXVlc3Rpb25zOg0KIC1Ob3cgSSBo YXZlIGNvbXBpbGVkIHRoZSBsZHAtcG9ydGFibGUgcGFja2FnZSwgYW5kIEkgZG9uJ3Qga25vdyBo b3cgaXQgZXhhY3RseSB3b3Jrcy4gDQogLVNvLCBjYW4gc29tZW9uZSB0ZWxsIG1lIGEgYmFzaWMg bGlzdCBvZiBpbnN0cnVjdGlvbnMgKGluIHRoZSBsZHAtcG9ydGFibGUgcHJvbXB0KSB0byB2ZXJp ZnkgdGhhdCBsZHAtcG9ydGFibGUgd29ya3MgcHJvcGVybHk/IA0KIC1JdCBzZWVtcyB5b3UgaGF2 ZSB0byBhZGQgaG9zdHMgYW5kIGludGVyZmFjZXMsIGJ1dCBkbyBJIGhhdmUgdG8gYWRkIGEgTFNQ IGJldHdlZW4gdGhlIGhvc3Qgd2l0aCBtcGxzYWRtIGJlZm9yZSB1c2luZyBsZHAtcG9ydGFibGU/ ICBvciBEb2VzIGxkcC1wb3J0YWJsZSBtYWtlICB0aGUgTFNQcz8gDQogLUlzIHRoZXJlIHNvbWUg ZG9jdW1lbnRhdGlvbiBhYm91dCB0aGlzIHBhY2thZ2U/DQoNClRoYW5rcyBpbiBhZHZhbmNlIQ0K IHRhb3Rhbw0K |
From: Radu D. <dr...@ee...> - 2002-02-07 18:20:33
|
Hi Anatoly. I think u should add to your mini-how-to in the section about configuring the kernel the following lines: Networking options ---> QoS and/or fair queueing ---> [*] QoS and/or fair queueing <*> CBQ packet scheduler <*> CSZ packet scheduler Maybe more but at least that. Regards, Radu ----- Original Message ----- From: Asviyan, Anatoly <ana...@te...> To: Mpls-Linux Mlist (E-mail) <mpl...@li...> Sent: Tuesday, February 05, 2002 4:34 PM Subject: [mpls-linux-general] mini-how-to > hi > this mini-how-to was compiled from posts to this mailing list > and various READMEs. It was helpfull to me and may be helpfull to others > > Regards, Anatoly > > |
From: James R. L. <jl...@mi...> - 2002-02-07 14:27:34
|
Hello, On Mon, Feb 04, 2002 at 06:02:35PM -0500, ncc49a wrote: > Hi James, > > I am trying out the diffserv functionality for the latest mpls patch. > > When I input this instruction: > > $MPLSADM -v -A -O gen:37:eth0 -o > ds2exp:0xff:0x1a:0x1:push:gen:37:set:eth0:ipv4:192.168.1.161 > > I get the errors saying: > 1) Mask for ds2exp is too large, must be less then 0x40 > 2) Out Instr: No such device or address. > > I must be using the above instruction wrongly. Can u provide me some > pointers on this? :-) Opps. grab 1.128 from CVS, it fixes a couple of mask/bounds checking bugs. > Next, for the above mask... is it applied to the DS code point or the entire > DS field? I am not sure, but I think "tc" from iproute2 applies the mask to > the whole field..., such that a mask of 0x3 and a DS field of 0x6b will give > a DS Code Point of 0x1a, which is AF. Good question. I think it is applied to just the DSCP. In the kernel I grab the DS field, shift 2 to the right then 'and' it with the mask. (take a look a mpls_output.c search for 'ipv4_get_dsfield' and you can see what I'm doing. You could add a printk (use just like printf) and add some debugging to help see if it is being done right. > > Thanks a lot! > > Paul > > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: Sanjeev C. <Sa...@co...> - 2002-02-07 01:35:30
|
Hi Anish, Help me understand, why you have the same IP adress on both the interfaces of router 2 in your config? It's not a realistic scenario in my opinion. Sanjeev -----Original Message----- From: anish verma [mailto:ani...@re...] Sent: Wednesday, February 06, 2002 1:37 AM To: mpl...@li... Subject: [mpls-linux-general] ldp_linux configuration hi jim n all, sorry for my previous mail coz the configuration i asked for is working fine. now i have a new problem 192.168.116.10 192.168.116.30 --------- ---------- --------- | Router1 | | router2 |------------| Router3 | --------- --------- --------- |eth0 eth0| |eth1 eth0| --------------- ----------------------- ip adress of router2 on both eth0 and eth1 is 192.168.116.20 all the machine can ping to one another ip_forwarding is 1 ie. on in router2 i am using this configuration but it's not working In router1: bash# route add 192.168.116.20/32 gw 192.168.116.20 bash# route add 192.168.116.30/32 gw 192.168.116.20 From inside ldp_linux: prompt> add global 192.168.116.10 prompt> add interface eth0 In router2: bash# route add 192.168.116.30/32 gw 192.168.116.30 dev eth1 bash# route add 192.168.116.10/32 gw 192.168.116.10 dev eth0 From inside ldp_linux: prompt> add global 192.168.116.20 prompt> add interface eth1 prompt> add interface eth0 In router3: bash# route add 192.168.116.20/32 gw 192.168.116.20 bash# route add 192.168.116.10/32 gw 192.168.116.20 From inside ldp_linux: prompt> add global 192.168.116.30 prompt> add interface eth0 mpls labelspace is on all eth* show databes showing no mapping n all the mpls_* files r empty.. except mpls_labelspace is this configuration right . or i have made some changes to make it working.. help me thanx in advance anish _______________________________________________ mpls-linux-general mailing list mpl...@li... https://lists.sourceforge.net/lists/listinfo/mpls-linux-general |
From: anish v. <ani...@re...> - 2002-02-06 17:44:37
|
hi jim,=0A as Kauder Thorsten suggested abt the three node network to assig= n different ip address to the ethernet card on same pc ... after that it's = working..=0A=0Aso jim please told me if it is neccessary to provide differe= nt ip address to the ethernet card on same pc to setup LSP successfully...= =0A=0Aif it is neccesary then what happens in case of triangle topology... = eg.=0A=0A ------- ------------=0A |router 1|----= -----------------| router2 |=0A -------- 6.2 5.2 --------= --=0A 7.2\ / 4.2=0A \ = /=0A \ / =0A 8.2 ---------= 9.2 / =0A |router 3 |-----=0A ---------=0A= =0Aall ip adress 10.0.*=0A=0Awill there be two lsp between router1 and rout= er 3 one through router2 and other one direct ..=0A=0Awhich lsp will be use= d in this case to reach route3 from router1 =0A=0Athanx in advance=0Abye=0A= anish=0A=0A=0A=0A=0A=0A =0A |
From: anish v. <ani...@re...> - 2002-02-06 15:39:47
|
hi jim,=0Ai am using ldp-portable from CVS on source forge=0Aanish=0A=0AOn = Wed, 06 Feb 2002 James R. Leu wrote :=0A> You still have neglected to tell = me which version you =0A> are using.=0A> Maybe a mutliple choice will help = you.=0A> =0A> Which version of ldp-portable are you using?=0A> a) ldp-porta= ble 0.060 (the tar file from the mpls-linux =0A> project page)=0A> b) ldp-p= ortable from the mpls-linux CVS on sourceforge=0A> c) I have no idea, what'= s my name?=0A> =0A> Jim=0A> =0A> On Wed, Feb 06, 2002 at 04:04:12AM -0000, = anish verma =0A> wrote:=0A> > =0A> > hi jim n all,=0A> > as it was ment= ioned some previous mail abt the how =0A> to congifure lsp using ldp_linux.= =0A> > =0A> > lo 10.0.0.6 lo 10.0.0.5=0A> > --------= - ---------=0A> > | Router2 |----------------| Router1= |=0A> > --------- ---------=0A> > |eth2 192= .168.12.0/24 |eth1=0A> > ---------------------------------------=0A= > > In router1:=0A> > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255= =0A> > bash# route add 10.0.0.6 gw 192.168.12.2=0A> > =0A> > From inside = ldp_linux:=0A> > prompt> add global 10.0.0.5=0A> > prompt> add interface = eth1=0A> > =0A> > In router2:=0A> > bash# ifconfig lo 10.0.0.6 netmask 25= 5.255.255.255=0A> > bash# route add 10.0.0.5 gw 192.168.12.1=0A> > =0A> > = From inside ldp_linux:=0A> > prompt> add global 10.0.0.6=0A> > prompt> a= dd interface eth2=0A> > =0A> > as it was mentioned in this mail to configur= e 'lo' =0A> > is it neccessary to configure lo?? can i the use this =0A> co= nfiguration??=0A> > =0A> > 192.168.116.20 192.168.116.10= =0A> > --------- ---------=0A> > | Router2 |-----= -----------| Router1 |=0A> > --------- ---------=0A> = > |eth2 |eth1=0A> > ----------------------= -----------------=0A> > both pcs r connected with crossover cable..=0A> > = =0A> > In router1:=0A> > bash# route add 192.168.116.20/32 gw 192.168.116= .20=0A> > =0A> > From inside ldp_linux:=0A> > prompt> add global 192.168.= 116.10=0A> > prompt> add interface eth1=0A> > =0A> > In router2:=0A> > ba= shsh# route add 192.168.116.10/32 gw 192.168.116.10=0A> > =0A> > From insi= de ldp_linux:=0A> > prompt> add global 192.168.116.20=0A> > prompt> add i= nterface eth2=0A> > =0A> > if this configuration is wrong then please tell = me =0A> the correct configuration which makes lsp without =0A> configuring = 'lo'.=0A> > =0A> > thanx in advance=0A> > bye=0A> > anish=0A> > =0A> > =0A>= > =0A> > =0A> > =0A> > _______________________________________________=0A= > > mpls-linux-general mailing list=0A> > mpl...@li...urcefo= rge.net=0A> > https://lists.sourceforge.net/lists/listinfo/mpls-linu-=0A> x= -general=0A> =0A> -- =0A> James R. Leu=0A> =0A> ___________________________= ____________________=0A> mpls-linux-general mailing list=0A> mpls-linux-gen= er...@li...=0A> https://lists.sourceforge.net/lists/listinfo= /mpls-linux--=0A> general=0A =0A |
From: James R. L. <jl...@mi...> - 2002-02-06 15:24:38
|
On Wed, Feb 06, 2002 at 01:44:12PM -0000, anish verma wrote: > > hi jim, > i added > int window > int irtt Why? > to struct mpls_out_label_req by making changes in mpls.h > ..i also made changes in mplsadm.c to pass it send_newnhlfe > but after compiling the kernel with the changes > making mpls-linux-1.0 but after that when i try to > give command > mplsadm -A -O gen:16:eth0:ipv4:192.168.10.20 > it shows > mpls_add_out_label : failed to create DST > what is problem > i am novice in linux coding regarding netlink socket. > please guide me what to do to add field to > struct mpls_out_label_req What are you trying to do? > thanx in advance > anish > > > > > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: James R. L. <jl...@mi...> - 2002-02-06 15:18:39
|
You still have neglected to tell me which version you are using. Maybe a mutliple choice will help you. Which version of ldp-portable are you using? a) ldp-portable 0.060 (the tar file from the mpls-linux project page) b) ldp-portable from the mpls-linux CVS on sourceforge c) I have no idea, what's my name? Jim On Wed, Feb 06, 2002 at 04:04:12AM -0000, anish verma wrote: > > hi jim n all, > as it was mentioned some previous mail abt the how to congifure lsp using ldp_linux. > > lo 10.0.0.6 lo 10.0.0.5 > --------- --------- > | Router2 |----------------| Router1 | > --------- --------- > |eth2 192.168.12.0/24 |eth1 > --------------------------------------- > In router1: > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255 > bash# route add 10.0.0.6 gw 192.168.12.2 > > From inside ldp_linux: > prompt> add global 10.0.0.5 > prompt> add interface eth1 > > In router2: > bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255 > bash# route add 10.0.0.5 gw 192.168.12.1 > > From inside ldp_linux: > prompt> add global 10.0.0.6 > prompt> add interface eth2 > > as it was mentioned in this mail to configure 'lo' > is it neccessary to configure lo?? can i the use this configuration?? > > 192.168.116.20 192.168.116.10 > --------- --------- > | Router2 |----------------| Router1 | > --------- --------- > |eth2 |eth1 > --------------------------------------- > both pcs r connected with crossover cable.. > > In router1: > bash# route add 192.168.116.20/32 gw 192.168.116.20 > > From inside ldp_linux: > prompt> add global 192.168.116.10 > prompt> add interface eth1 > > In router2: > bashsh# route add 192.168.116.10/32 gw 192.168.116.10 > > From inside ldp_linux: > prompt> add global 192.168.116.20 > prompt> add interface eth2 > > if this configuration is wrong then please tell me the correct configuration which makes lsp without configuring 'lo'. > > thanx in advance > bye > anish > > > > > > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |
From: anish v. <ani...@re...> - 2002-02-06 13:47:12
|
hi jim,=0A i added =0Aint window =0A int irtt =0Ato struct mpls_out_label= _req by making changes in mpls.h=0A..i also made changes in mplsadm.c to pa= ss it send_newnhlfe=0Abut after compiling the kernel with the changes =0Ama= king mpls-linux-1.0 but after that when i try to =0Agive command =0Amplsadm= -A -O gen:16:eth0:ipv4:192.168.10.20=0Ait shows =0Ampls_add_out_label : fa= iled to create DST=0Awhat is problem =0Ai am novice in linux coding regardi= ng netlink socket.=0Aplease guide me what to do to add field to =0Astruct m= pls_out_label_req=0A=0Athanx in advance=0Aanish=0A=0A=0A =0A |
From: anish v. <ani...@re...> - 2002-02-06 09:37:09
|
hi jim n all,=0A sorry for my previous mail coz the configuration i asked = for is working fine.=0Anow i have a new problem=0A=0A192.168.116.10 = 192.168.116.30=0A--------- ---------- --= -------=0A| Router1 | | router2 |------------| Router3 |=0A--------- = --------- ---------=0A |eth0 eth0| |eth1 = eth0|=0A --------------- -----------------------=0Aip adress of rou= ter2 on both eth0 and eth1 is 192.168.116.20 =0Aall the machine can ping to= one another ip_forwarding is 1 ie. on in router2 =0A=0Ai am using this con= figuration but it's not working=0A=0A In router1:=0A bash# route add 192.16= 8.116.20/32 gw 192.168.116.20=0A bash# route add 192.168.116.30/32 gw 192.1= 68.116.20=0A=0AFrom inside ldp_linux:=0A prompt> add global 192.168.116.10= =0A prompt> add interface eth0=0A=0A In router2:=0A bash# route add 192.168= .116.30/32 gw 192.168.116.30 dev eth1=0A bash# route add 192.168.116.10/32 = gw 192.168.116.10 dev eth0=0A=0A From inside ldp_linux:=0A prompt> add glob= al 192.168.116.20=0A prompt> add interface eth1=0A prompt> add interface et= h0=0A=0AIn router3:=0A bash# route add 192.168.116.20/32 gw 192.168.116.20= =0A bash# route add 192.168.116.10/32 gw 192.168.116.20=0A=0AFrom inside ld= p_linux:=0A prompt> add global 192.168.116.30=0A prompt> add interface eth0= =0A=0A=0Ampls labelspace is on all eth*=0A=0Ashow databes showing no mappin= g =0An all the mpls_* files r empty.. except mpls_labelspace=0A=0Ais this c= onfiguration right . or i have made some changes to make it working..=0Ahel= p me=0Athanx in advance=0Aanish=0A =0A |
From: anish v. <ani...@re...> - 2002-02-06 04:07:06
|
hi jim n all,=0A as it was mentioned some previous mail abt the how to co= ngifure lsp using ldp_linux. =0A=0A lo 10.0.0.6 lo 10.0.0.5= =0A --------- ---------=0A | Router2 |-------------= ---| Router1 |=0A --------- ---------=0A |eth2 = 192.168.12.0/24 |eth1=0A ---------------------------------------=0A= In router1:=0A bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255=0A bash#= route add 10.0.0.6 gw 192.168.12.2=0A=0A From inside ldp_linux:=0A prompt>= add global 10.0.0.5=0A prompt> add interface eth1=0A=0A In router2:=0A bas= h# ifconfig lo 10.0.0.6 netmask 255.255.255.255=0A bash# route add 10.0.0.5= gw 192.168.12.1=0A=0A From inside ldp_linux:=0A prompt> add global 10.0.0.= 6=0A prompt> add interface eth2=0A=0Aas it was mentioned in this mail to co= nfigure 'lo' =0Ais it neccessary to configure lo?? can i the use this confi= guration??=0A=0A 192.168.116.20 192.168.116.10=0A ----= ----- ---------=0A | Router2 |----------------| Router1= |=0A --------- ---------=0A |eth2 = |eth1=0A ---------------------------------------=0Aboth pcs r c= onnected with crossover cable..=0A=0A In router1:=0A bash# route add 192.16= 8.116.20/32 gw 192.168.116.20=0A=0A From inside ldp_linux:=0A prompt> add g= lobal 192.168.116.10=0A prompt> add interface eth1=0A=0A In router2:=0Abash= sh# route add 192.168.116.10/32 gw 192.168.116.10=0A=0A From inside ldp_lin= ux:=0A prompt> add global 192.168.116.20=0A prompt> add interface eth2=0A= =0Aif this configuration is wrong then please tell me the correct configura= tion which makes lsp without configuring 'lo'.=0A=0Athanx in advance=0Abye= =0Aanish=0A=0A=0A =0A |
From: <due...@cs...> - 2002-02-05 16:49:40
|
Hi! >> Excerpt from our configuration script: >> >> ... >> mplsadm -v -A -O gen:33:eth1:ipv4:192.168.2.3 >> >> KEY3=`grep 'gen 33' /proc/net/mpls_out | cut -d' ' -f1` >> >> iptables -v -I PREROUTING -t mangle -d 192.168.6.1 \ >> -s 192.168.5.2 -j MPLS --set-mpls 0x$KEY3 >> >All seems correct. Can you send me the topology of the network ? Is >192.168.2.3 the Egress node ? Where do you perform this command ? on the >Ingress node ? > >I post some month ago (look at the mailing list) a version 0.4 of our >patch which resolved some pb., add TC support and let the user use >directly the label for iptables instead of the key. We have attached a small eps-file showing the topology of our network. 192.168.2.3 is not the egress but configured as LSR. (For this example node 1 is the egress.) The above commands are executed at the ingress (node 4). When we ping 192.168.6.1 from 192.168.5.2 we expect the traffic to go via 192.168.2.3 (with label 33), but using tcpdump on interface 192.168.3.3, we see that the traffic arrives there. (The normal routing at the ingress points there.) After the ping, we can see the following at the ingress: # iptables -v -n -L -t mangle Chain PREROUTING (policy ACCEPT 171 packets, 10624 bytes) pkts bytes target prot opt in out source destination 13 1092 MPLS all -- * * 192.168.5.2 192.168.6.1 MPLS index set to :0x40008403 # cat /proc/net/mpls_out 40008403 PUSH(gen 33) SET(eth1) We couldn't find the newest patch (0.4) on the net. The archive of this list doesn't provide it, neither does the mpls-linux homepage at sourceforge. Could you please post it again? Maybe as a personal mail, if you like. >Can activate the trace i.e. perform mplsadm -d then ping 192.168.6.2 >from 192.168.5.2 and look at the console kernel log. Normally you'll can >see some mpls stuff and especially the rt_next_sethop message telling >that you match the iptable rules. We turned on debugging at the ingress, there are a lot of "normal" mpls messages (when we run our little script), but no messages later on (during the ping) and no rt_next_sethop message at all (problem here?) # tail /var/log/messages Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: enter Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: labelspace(0) Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: exit Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: enter Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: labelspace(0) Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: exit Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: enter Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: labelspace(0) Feb 5 18:41:18 bb4 kernel: mpls_set_labelspace: exit Feb 5 18:41:18 bb4 kernel: mpls_add_out_label: enter Feb 5 18:41:18 bb4 kernel: mpls_make_dst: enter Feb 5 18:41:18 bb4 kernel: mpls_make_dst: before bind neighbor Feb 5 18:41:18 bb4 kernel: mpls_make_dst: bind neighbor succeeded Feb 5 18:41:18 bb4 kernel: mpls_make_dst: exit(cf420080) Feb 5 18:41:18 bb4 kernel: mpls_info_default_moi_instruction: enter Feb 5 18:41:18 bb4 kernel: mpls_info_default_moi_instruction: exit Feb 5 18:41:18 bb4 kernel: Label GEN 33 Feb 5 18:41:18 bb4 kernel: Key GEN 33 3 Feb 5 18:41:18 bb4 kernel: mpls_add_out_label: exit Thank you very much, Uli & Daniel |
From: Asviyan, A. <ana...@te...> - 2002-02-05 16:34:50
|
hi this mini-how-to was compiled from posts to this mailing list and various READMEs. It was helpfull to me and may be helpfull to others Regards, Anatoly |