mpls-linux-general — Mailing list for general discussion about MPLS for Linux

[mpls-linux-general] Packet Identification

[Muhammad R. S. <sa...@cc...>]

You outlined the following steps, require assistance for the following.

 

A quick overview of what you will need to setup:

-bind a IPv4 route to a LSP-----DONE

-use iptables to identify and mark packets----DONE

-use the markings to set EXP values (or choose differnt LSPs)----DONE

-use EXP value to determin queuing priority--------How to do this part? How
can I assign priority on the basis of EXP bits value?

 

 

Muhammad R. Sami 
Research Assistant, 
Computer Engineering Department 
P.O.Box 354 
King Fahd University of Petroleum & Minerals 
Dhahran 31261 
Saudi Arabia. 
Tel: +96638601423 
Cell: +96657982951 
www.ccse.kfupm.edu.sa/sami

 

[mpls-linux-general] Packet Identification

[Muhammad R. S. <sa...@cc...>]

You outlined the following steps; I require assistance for the last one.

 

A quick overview of what you will need to setup:

-bind a IPv4 route to a LSP-----DONE

-use iptables to identify and mark packets----DONE

-use the markings to set EXP values (or choose differnt LSPs)----DONE

-use EXP value to determin queuing priority--------How to do this part? How
can I assign priority on the basis of EXP bits value?

 

Thanks in advance

 

Muhammad R. Sami 
Research Assistant, 
Computer Engineering Department 
P.O.Box 354 
King Fahd University of Petroleum & Minerals 
Dhahran 31261 
Saudi Arabia. 
Tel: +96638601423 
Cell: +96657982951 
www.ccse.kfupm.edu.sa/sami

 

[mpls-linux-general] TCP checksum problem with the MPLS linux 2.6 patch

[Pierre A. <pie...@po...>]

Hello !

We set up an MPLS path between two linux boxes. The patch was applied on a 
2.6.3 kernel. We're able to ping a host from the other. But our attemps to 
establish a TCP connection (for FTP or SSH) don't work : the connection is 
set up correctly (SYN / SYN&ACK / ACK), but the following packets (data 
packets) have a wrong TCP checksum ! Ethereal, both on the server and on the 
client, shows that the checksum is bad on both hosts (emission and 
reception). We use 3COM 905C NICs...

Is there a known issue ? Thanks a lot for your help !

Regards,
Pierre Ansel.

[mpls-linux-general] problem of iproute2 on linux-2.6.1

[T. T. <t_t...@ho...>]

Thanks for your quick reply.
I  succeed to make linux 2.6.1 with mpls-1.922 by not using .config of 
2.4.18.
Thank you.

On the other hand, I have another problem with iproute2.
When I execute "make" in iproute2 directory, an error appears as following.

# cd iproute2
# patch -p1 < ../iproute2.diff
# make
make[1]: Entering directory `/usr/src/mpls-linux/patches/iproute2/lib'
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -Werror -g 
-I../include-glibc -include ../include-glibc/glibc-bugs.h 
-I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES   -c -o utils.o 
utils.c
In file included from /usr/src/linux/include/linux/compiler.h:16,
                 from /usr/src/linux/include/asm/bitops.h:9,
                 from ../include/utils.h:5,
                 from utils.c:30:
/usr/src/linux/include/linux/compiler-gcc3.h:19:1: "__attribute_used__" 
redefined
In file included from /usr/include/features.h:291,
                 from ../include-glibc/glibc-bugs.h:4,
                 from <command line>:1:
/usr/include/sys/cdefs.h:192:1: this is the location of the previous 
definition
In file included from /usr/src/linux/include/linux/compiler.h:16,
                 from /usr/src/linux/include/asm/bitops.h:9,
                 from ../include/utils.h:5,
                 from utils.c:30:
/usr/src/linux/include/linux/compiler-gcc3.h:22:1: "__attribute_pure__" 
redefined
In file included from /usr/include/features.h:291,
                 from ../include-glibc/glibc-bugs.h:4,
                 from <command line>:1:
/usr/include/sys/cdefs.h:183:1: this is the location of the previous 
definition
cc1: warnings being treated as errors
In file included from ../include/utils.h:6,
                 from utils.c:30:
/usr/src/linux/include/linux/inetdevice.h: In function `inet_make_mask':
/usr/src/linux/include/linux/inetdevice.h:169: warning: implicit 
declaration of function `htonl'
/usr/src/linux/include/linux/inetdevice.h: In function `inet_mask_len':
/usr/src/linux/include/linux/inetdevice.h:175: warning: implicit 
declaration of function `ntohl'
make[1]: *** [utils.o] Error 1
make[1]: Leaving directory `/usr/src/mpls-linux/patches/iproute2/lib'
make: *** [all] Error 2


Thank you in advance for your help.


>What makes you think your .config from 2.4.18 will work on a 2.6.1 kernel?
>Make sure to that MPLS is not a module.
>
>On Tue, Jun 15, 2004 at 02:57:58PM +0900, T. Take wrote:
> > Hello.
> >
> > I have tried to update.
> >
> >  kernel: 2.6.1
> > mplsadm: 1.922
> >
> > I executed the following command, but I didn't succeed.
> >
> > # make mrproper
> > # patch -p1 < ../mpls-linux/patches/linux-kernel.diff
> > # cp /boot/config-2.4.18 .config
> > # make oldconfig
> > # make menuconfig
> > # make
> >
> >  CHK     include/linux/compile.h
> >  UPD     include/linux/compile.h
> >  CC      init/version.o
> >  LD      init/built-in.o
> >  LD [M]  net/mpls/mpls.o
> > net/mpls/mpls_netlink.o: In function `mpls_netlink_init':
> > net/mpls/mpls_netlink.o(.init.text+0x0): multiple definition of
> > `init_module'
> > net/mpls/mpls_init.o(.init.text+0xb0): first defined here
> > ld: Warning: size of symbol `init_module' changed from 472 to 48 in
> > net/mpls/mpl
> > s_netlink.o
> > net/mpls/mpls_netlink.o: In function `cleanup_module':
> > net/mpls/mpls_netlink.o(.exit.text+0x0): multiple definition of
> > `cleanup_module'
> > net/mpls/mpls_init.o(.exit.text+0x20): first defined here
> > ld: Warning: size of symbol `cleanup_module' changed from 231 to 8 in
> > net/mpls/m
> > pls_netlink.o
> > make[2]: *** [net/mpls/mpls.o] error 1
> > make[1]: *** [net/mpls] error 2
> > make: *** [net] error 2
> >

_________________________________________________________________
メッセンジャーで総額1億円プレゼント！ http://im.msn.co.jp/home.htm 

Re: [mpls-linux-general] Egress Router, how?

[James R. L. <jl...@mi...>]

What makes you think your .config from 2.4.18 will work on a 2.6.1 kernel?
Make sure to that MPLS is not a module.

On Tue, Jun 15, 2004 at 02:57:58PM +0900, T. Take wrote:
> Hello.
> 
> I have tried to update.
> 
>  kernel: 2.6.1
> mplsadm: 1.922
> 
> I executed the following command, but I didn't succeed.
> 
> # make mrproper
> # patch -p1 < ../mpls-linux/patches/linux-kernel.diff
> # cp /boot/config-2.4.18 .config
> # make oldconfig  
> # make menuconfig
> # make
> 
>  CHK     include/linux/compile.h
>  UPD     include/linux/compile.h
>  CC      init/version.o
>  LD      init/built-in.o
>  LD [M]  net/mpls/mpls.o
> net/mpls/mpls_netlink.o: In function `mpls_netlink_init':
> net/mpls/mpls_netlink.o(.init.text+0x0): multiple definition of 
> `init_module'
> net/mpls/mpls_init.o(.init.text+0xb0): first defined here
> ld: Warning: size of symbol `init_module' changed from 472 to 48 in 
> net/mpls/mpl
> s_netlink.o
> net/mpls/mpls_netlink.o: In function `cleanup_module':
> net/mpls/mpls_netlink.o(.exit.text+0x0): multiple definition of 
> `cleanup_module'
> net/mpls/mpls_init.o(.exit.text+0x20): first defined here
> ld: Warning: size of symbol `cleanup_module' changed from 231 to 8 in 
> net/mpls/m
> pls_netlink.o
> make[2]: *** [net/mpls/mpls.o] error 1
> make[1]: *** [net/mpls] error 2
> make: *** [net] error 2
> 
> 
> 
> If you could take a few minutes to answer my question, I would really 
> appreciate it. 
> 
> Best regards 
> 
> >From: "James R. Leu" <jl...@mi...>
> >Reply-To: jl...@mi...
> >To: "T. Take" <t_t...@ho...>
> >CC: mpl...@li...
> >Subject: Re: [mpls-linux-general] Egress Router, how?
> >Date: Mon, 24 May 2004 21:26:05 -0500
> >
> >On Tue, May 25, 2004 at 11:01:31AM +0900, T. Take wrote:
> >> Mr. Leu
> >>
> >> Thanks for your quick reply.
> >>
> >> I have reset LSPs on C as following.
> >>
> >> # mplsadm2 -L eth1:0
> >> # mplsadm2 -A -I gen:101:0
> >> # mplsadm2 -A -I gen:201:0
> >> # mplsadm2 -I gen:101:0 -i pop:peek
> >> In Instr: No such device or address
> >
> >Hmm.  I just excuted the above commands on 1.930 (on a 2.6.1 kernel) and
> >it works fine.  Obviously something must have changed since 1.172 and 
> 1.930.
> >I do not have a 2.4 kernel to test on.  I will try and build a 2.4 
> environment
> >to test and debug on.
> >
> >My gut response is to tell you to upgrade to 1.930 (which is based on a
> >2.6 kernel).
> >
> >
> >> But they seemed to be set properly except the last command again.
> >> How should I do this?
> >>
> >> The information of the machine is
> >>
> >>  OS : Redhat 8.0
> >>  kernel : 2.4.22
> >>  mpls : mpls-linux-1.172
> >>
> >> If you could take a few minutes to answer my question, I would really
> >> appreciate it.
> >>
> >> Best regards
> >>
> >> >From: "James R. Leu" <jl...@mi...>
> >> >Reply-To: jl...@mi...
> >> >To: "T. Take" <t_t...@ho...>
> >> >CC: mpl...@li...
> >> >Subject: Re: [mpls-linux-general] Egress Router, how?
> >> >Date: Mon, 24 May 2004 09:05:47 -0500
> >> >
> >> >On Mon, May 24, 2004 at 06:58:28PM +0900, T. Take wrote:
> >> >> Hi.
> >> >>
> >> >> I have a similar problem.
> >> >> I have executed "MPLS Hierarchy" in README and succeeded to setup 
> 200
> >> and
> >> >> 202 LSP.
> >> >>
> >> >>          101
> >> >>   200    201    202
> >> >> A------B------C------D
> >> >
> >> >Here is how I do it:
> >> >
> >> >on C
> >> >----
> >> >mplsadm2 -A -I gen:101:0
> >> >mplsadm2 -A -I gen:201:0
> >> >mplsadm2 -I gen:101:0 -i pop:peek
> >> >
> >> >on B
> >> >----
> >> >mplsadm2 -A -O 0
> >> >mplsadm2 -O 0x2 -o push:gen:101:set:eth1:192.169.1.2
> >> >mplsadm2 -A -O 0
> >> >mplsadm2 -O 0x3 -o push:gen:201:fwd:0x2
> >> >mplsadm2 -A -I gen:200:0
> >> >mplsadm2 -B -I gen:200:0 -O 0x3
> >> >
> >> >>
> >> >> But, I had a problem at "On C" setting about 101 and 201. The 
> command
> >> is
> >> >>
> >> >> # mplsadm2 -I gen:101:0 -i pop:peek
> >> >> In Instr: No such device or address
> >> >>
> >> >> It didn't seem to be set properly.
> >> >> When I have executed "mplsadm2 -d", the output of the above command 
> is
> >> >>
> >> >> mpls_set_in_label_instructions: enter
> >> >> mpls_in_info_hold: enter
> >> >> mpls_in_info_hold: new count 2
> >> >> mpls_in_info_hold: exit
> >> >> mpls_instruction_build: enter
> >> >> mpls_instruction_build: exit(2)
> >> >> mpls_instruction_clear: enter
> >> >> mpls_instruction_clear: exit
> >> >> mpls_in_info_release: enter
> >> >> mpls_in_info_release: new count 1
> >> >> mpls_in_info_release: exit
> >> >> mpls_set_in_label_structions: exit
> >> >>
> >> >> What should I do?
> >> >> I hope any help.
> 
> _________________________________________________________________
> ?$B%a%C%;%s%8%c!<$GAm3[1?$B2/1_%W%l%<%s%H!* http://im.msn.co.jp/home.htm 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-general] Egress Router, how?

[T. T. <t_t...@ho...>]

Hello.

I have tried to update.

  kernel: 2.6.1
 mplsadm: 1.922

I executed the following command, but I didn't succeed.

# make mrproper
# patch -p1 < ../mpls-linux/patches/linux-kernel.diff
# cp /boot/config-2.4.18 .config
# make oldconfig  
# make menuconfig
# make

  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD [M]  net/mpls/mpls.o
net/mpls/mpls_netlink.o: In function `mpls_netlink_init':
net/mpls/mpls_netlink.o(.init.text+0x0): multiple definition of 
`init_module'
net/mpls/mpls_init.o(.init.text+0xb0): first defined here
ld: Warning: size of symbol `init_module' changed from 472 to 48 in 
net/mpls/mpl
s_netlink.o
net/mpls/mpls_netlink.o: In function `cleanup_module':
net/mpls/mpls_netlink.o(.exit.text+0x0): multiple definition of 
`cleanup_module'
net/mpls/mpls_init.o(.exit.text+0x20): first defined here
ld: Warning: size of symbol `cleanup_module' changed from 231 to 8 in 
net/mpls/m
pls_netlink.o
make[2]: *** [net/mpls/mpls.o] error 1
make[1]: *** [net/mpls] error 2
make: *** [net] error 2



If you could take a few minutes to answer my question, I would really 
appreciate it. 

Best regards 

>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: "T. Take" <t_t...@ho...>
>CC: mpl...@li...
>Subject: Re: [mpls-linux-general] Egress Router, how?
>Date: Mon, 24 May 2004 21:26:05 -0500
>
>On Tue, May 25, 2004 at 11:01:31AM +0900, T. Take wrote:
> > Mr. Leu
> >
> > Thanks for your quick reply.
> >
> > I have reset LSPs on C as following.
> >
> > # mplsadm2 -L eth1:0
> > # mplsadm2 -A -I gen:101:0
> > # mplsadm2 -A -I gen:201:0
> > # mplsadm2 -I gen:101:0 -i pop:peek
> > In Instr: No such device or address
>
>Hmm.  I just excuted the above commands on 1.930 (on a 2.6.1 kernel) and
>it works fine.  Obviously something must have changed since 1.172 and 
1.930.
>I do not have a 2.4 kernel to test on.  I will try and build a 2.4 
environment
>to test and debug on.
>
>My gut response is to tell you to upgrade to 1.930 (which is based on a
>2.6 kernel).
>
>
> > But they seemed to be set properly except the last command again.
> > How should I do this?
> >
> > The information of the machine is
> >
> >  OS : Redhat 8.0
> >  kernel : 2.4.22
> >  mpls : mpls-linux-1.172
> >
> > If you could take a few minutes to answer my question, I would really
> > appreciate it.
> >
> > Best regards
> >
> > >From: "James R. Leu" <jl...@mi...>
> > >Reply-To: jl...@mi...
> > >To: "T. Take" <t_t...@ho...>
> > >CC: mpl...@li...
> > >Subject: Re: [mpls-linux-general] Egress Router, how?
> > >Date: Mon, 24 May 2004 09:05:47 -0500
> > >
> > >On Mon, May 24, 2004 at 06:58:28PM +0900, T. Take wrote:
> > >> Hi.
> > >>
> > >> I have a similar problem.
> > >> I have executed "MPLS Hierarchy" in README and succeeded to setup 
200
> > and
> > >> 202 LSP.
> > >>
> > >>          101
> > >>   200    201    202
> > >> A------B------C------D
> > >
> > >Here is how I do it:
> > >
> > >on C
> > >----
> > >mplsadm2 -A -I gen:101:0
> > >mplsadm2 -A -I gen:201:0
> > >mplsadm2 -I gen:101:0 -i pop:peek
> > >
> > >on B
> > >----
> > >mplsadm2 -A -O 0
> > >mplsadm2 -O 0x2 -o push:gen:101:set:eth1:192.169.1.2
> > >mplsadm2 -A -O 0
> > >mplsadm2 -O 0x3 -o push:gen:201:fwd:0x2
> > >mplsadm2 -A -I gen:200:0
> > >mplsadm2 -B -I gen:200:0 -O 0x3
> > >
> > >>
> > >> But, I had a problem at "On C" setting about 101 and 201. The 
command
> > is
> > >>
> > >> # mplsadm2 -I gen:101:0 -i pop:peek
> > >> In Instr: No such device or address
> > >>
> > >> It didn't seem to be set properly.
> > >> When I have executed "mplsadm2 -d", the output of the above command 
is
> > >>
> > >> mpls_set_in_label_instructions: enter
> > >> mpls_in_info_hold: enter
> > >> mpls_in_info_hold: new count 2
> > >> mpls_in_info_hold: exit
> > >> mpls_instruction_build: enter
> > >> mpls_instruction_build: exit(2)
> > >> mpls_instruction_clear: enter
> > >> mpls_instruction_clear: exit
> > >> mpls_in_info_release: enter
> > >> mpls_in_info_release: new count 1
> > >> mpls_in_info_release: exit
> > >> mpls_set_in_label_structions: exit
> > >>
> > >> What should I do?
> > >> I hope any help.

_________________________________________________________________
メッセンジャーで総額1億円プレゼント！ http://im.msn.co.jp/home.htm 

[mpls-linux-general] Re: [quagga-dev 1233] RSVP-TE, OSPF-TE free source code

[Vadim S. <su...@ne...>]

Hi.
I've updated the code since the previous version has
a problem with build. Now, it is fixed.
The code location is the same:
http://www.angelfire.com/theforce/suraev/zebra/index.html .

Regards,
 Vadim.
----- Original Message -----
From: "James R. Leu" <jl...@mi...>
To: "Vadim Suraev" <su...@ne...>
Cc: <Qua...@li...>;
<mpl...@li...>
Sent: Tuesday, June 01, 2004 5:39 PM
Subject: Re: [quagga-dev 1233] RSVP-TE, OSPF-TE free source code


> I'd like to work with you to clean up the layout of the code, port
> to quagga, and integrate with my MPLS infrastructure work.  If you are
> interested in such an effort, please respond to the list, otherwise I
> will begin the effort myself.  Thank you for your contribution.
>
> BTW I didn't see a license or copyright in any of the files.  You will
> probably want to do that.
>
> (I've CC'd the mpls-linux mailing list)
>
> --
> James R. Leu
> jl...@mi...
>
> On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
> > Hi.
> > I'd like to contribute to the Zebra users & developers' community
several software
> > modules that I've developed recently:
> > RSVP-TE, TE application, TE extensions for OSPF.
> > The software has been tested against CISCO.
> > If you decide to try it, please read the short manuel at:
> > http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
> > The code is located at:
> > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
> > If you have any questions, you are welcome to ask.
> > Any request for any help and support is welcome.
> >
> > Regards,
> >  Vadim.
>
> > _______________________________________________
> > Quagga-dev mailing list
> > Qua...@li...
> > http://lists.quagga.net/mailman/listinfo/quagga-dev
>
>

Re: [mpls-linux-general] EXP bits

[James R. L. <jl...@mi...>]

By adding the instruction:

	set_exp:<exp>

to your output instructions you can explicitly set the EXP value.  If you
want the EXP value to be decided based on the TC index, the NF mark or
the DSCP value then there are other instructions you can use.

Example:

mplsadm2 -A -O 0
mplsadm2 -O <key> -o push:gen:1000:set_exp:0x3:set:eth0:ipv4:192.168.2.1


On Mon, Jun 14, 2004 at 02:23:24PM +0300, Itrat Rasod Quadri wrote:
> Hello,
> 
> Thanks a bunch for your feedback regarding iptables. I am now able to get the 
> output through tcpdump and the forwarding is also taking place. 
> One thing I would like to ask you know is to how can I set the EXP bits 
> according to my requirements. Can it be done through mpls commands or will it 
> require change in code in some file.
> 
> Thanks once again.
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the
> one installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] EXP bits

[Itrat R. Q. <iq...@cc...>]

Hello,

Thanks a bunch for your feedback regarding iptables. I am now able to get the 
output through tcpdump and the forwarding is also taking place. 
One thing I would like to ask you know is to how can I set the EXP bits 
according to my requirements. Can it be done through mpls commands or will it 
require change in code in some file.

Thanks once again.

Re: [mpls-linux-general] Problem with MPLS on Kernel 2.6.3

[James R. L. <jl...@mi...>]

The iproute2 patch for the 2.6 series is differnt then the 2.4 series.  Make
sure you have a recent iproute2 patch.  The command syntax has changed as
well for the 2.6 series:

ip route add 10.100.0.4/32 via 10.100.0.4 spec_nh 0x8847 <key>

I'm not sure of the iptables problem, but others have reported issues with
the new iptables.  I will have to look into it.

On Thu, Jun 10, 2004 at 07:39:12PM +0200, Pierre ANSEL wrote:
> Hello,
> 
> We are trying to make MPLS run on a kernel 2.6.3 but we can't see any MPLS 
> packet going out of our machines.
> 
> We are using this topology :
> Machine 1 -------------- Machine 2
> 10.100.0.1				10.100.0.4
> 
> On machine 1, we installed mplsadm2 and configured a label with
> mplsadm2 -A -O 0
> mplsadm2 -O 0x2 -o push:gen:10000:set:eth1:ipv4:10.100.0.4
> 
> cat /proc/net/mpls/out gives :
> 
> NHLFE Key:0x00000002 Instruction Set
> PUSH PUSH(gen 10000)
> SET SET(eth1,<unk l3>)
> 
> ip route show give :
> 10.100.0.4 via 10.100.0.4 dev eth1 lsp 0x2
> 
> With tcpdump, we can only see IPv4 packets when we ping 10.100.0.4 and no MPLS 
> packets.
> 
> Moreover, we can't make iptables run properly. 
> We tried iptables -A OUTPUT -d 10.100.0.4/32 -j spec_nh --spec_nh 0x8847:0x2 
> and we got
> iptables: No chain/target/match by that name
> 
> Nevertheless, it seems that iptables succeeded in loading libspec_nh.so 
> without any problems.
> 
> Do someone have any idea on how to fix these 2 problems ?
> 
> Thanks a lot !
> 
> Pierre
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the
> one installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] Problem with MPLS on Kernel 2.6.3

[Pierre A. <pie...@po...>]

Hello,

We are trying to make MPLS run on a kernel 2.6.3 but we can't see any MPLS 
packet going out of our machines.

We are using this topology :
Machine 1 -------------- Machine 2
10.100.0.1				10.100.0.4

On machine 1, we installed mplsadm2 and configured a label with
mplsadm2 -A -O 0
mplsadm2 -O 0x2 -o push:gen:10000:set:eth1:ipv4:10.100.0.4

cat /proc/net/mpls/out gives :

NHLFE Key:0x00000002 Instruction Set
PUSH PUSH(gen 10000)
SET SET(eth1,<unk l3>)

ip route show give :
10.100.0.4 via 10.100.0.4 dev eth1 lsp 0x2

With tcpdump, we can only see IPv4 packets when we ping 10.100.0.4 and no MPLS 
packets.

Moreover, we can't make iptables run properly. 
We tried iptables -A OUTPUT -d 10.100.0.4/32 -j spec_nh --spec_nh 0x8847:0x2 
and we got
iptables: No chain/target/match by that name

Nevertheless, it seems that iptables succeeded in loading libspec_nh.so 
without any problems.

Do someone have any idea on how to fix these 2 problems ?

Thanks a lot !

Pierre

Re: [mpls-linux-general] packet identification

[James R. L. <jl...@mi...>]

Hello,

I'm not sure what else you expect for a response.  I said I think it
can be done you will need to use iptables and the do packet marking.  Then
use the markings to set the EXP bits.  If you're looking for specific
commands RTFM.

The steps for doing the above are very similar to how you would go about
implement DiffServ for linux.  Read up on how to use the DSCP to affect queuing
and you will be very close to the task at hand.

On Wed, Jun 09, 2004 at 10:08:35AM +0300, Muhammad R. Sami wrote:
> In reference to my previous mail, basically I want the ingress router to read specific information in the application layer header and then set EXP value and forward the packet. It is basically an If-Else situation:
> 
>  If this (in application payloiad) -> then EXP value = x
>  else EXP value = y
> 
> Is this possible. If yes then please let me know how?
> Looking forward for your kind cooperation.
> regards
> 
> ----------
> 
> Muhammad R. Sami
> Research Assistant,
> Computer Engineering Department
> P.O.Box 354
> King Fahd University of Petroleum & Minerals
> Dhahran 31261
> Saudi Arabia.
> Tel: +96638601423
> Cell: +96657982951
> www.ccse.kfupm.edu.sa/sami
-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-general] packet identification

[Muhammad R. S. <sa...@cc...>]

In reference to my previous mail, basically I want the ingress router to =
read specific information in the application layer header and then set =
EXP value and forward the packet. It is basically an If-Else situation:

 If this (in application payloiad) -> then EXP value =3D x
 else EXP value =3D y

Is this possible. If yes then please let me know how?
Looking forward for your kind cooperation.
regards
  ----- Original Message -----=20
  From: James R. Leu=20
  To: Muhammad R. Sami=20
  Cc: mpl...@li...=20
  Sent: Thursday, June 03, 2004 4:58 PM
  Subject: Re: [mpls-linux-general] packet identification


  On Thu, Jun 03, 2004 at 09:44:21AM +0300, Muhammad R. Sami wrote:
  > hello,
  > I am relatively new in this group, I want to add a packet =
identification scheme in a MPLS router, and then based on the =
application layer, want to set EXP bits value. Can anyone help me on =
this one, like is it already implemented, if not, what files do I have =
to play with.=20
  > looking forward for your kind guidance.
  > regards

  There already exists some mechanisms for EXP setting.  Although there =
is
  probably area for improvment.  I should not that I have not tested EXP
  setting for about a year and a significant amount of development has
  occureded since then, so you may run into some bugs, if so let me know =
and
  I'll try and produce fixes.

  A quick overview of what you will need to setup:
  -bind a IPv4 route to a LSP
  -use iptables to identify and mark packets
  -use the markings to set EXP values (or choose differnt LSPs)
  -use EXP value to determin queuing priority

  > Muhammad R. Sami
  > Research Assistant,
  > Computer Engineering Department
  > P.O.Box 354
  > King Fahd University of Petroleum & Minerals
  > Dhahran 31261
  > Saudi Arabia.
  > Tel: +96638601423
  > Cell: +96657982951
  > www.ccse.kfupm.edu.sa/sami
  >   ----- Original Message -----=20
  >   From: James R. Leu=20
  >   To: Vadim Suraev=20
  >   Cc: Qua...@li... ; =
mpl...@li...=20
  >   Sent: Tuesday, June 01, 2004 5:39 PM
  >   Subject: [mpls-linux-general] Re: [quagga-dev 1233] RSVP-TE, =
OSPF-TE free source code
  >=20
  >=20
  >   I'd like to work with you to clean up the layout of the code, port
  >   to quagga, and integrate with my MPLS infrastructure work.  If you =
are
  >   interested in such an effort, please respond to the list, =
otherwise I
  >   will begin the effort myself.  Thank you for your contribution.
  >=20
  >   BTW I didn't see a license or copyright in any of the files.  You =
will
  >   probably want to do that.=20
  >=20
  >   (I've CC'd the mpls-linux mailing list)
  >=20
  >   --=20
  >   James R. Leu
  >   jl...@mi...
  >=20
  >   On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
  >   > Hi.
  >   > I'd like to contribute to the Zebra users & developers' =
community several software=20
  >   > modules that I've developed recently:
  >   > RSVP-TE, TE application, TE extensions for OSPF.
  >   > The software has been tested against CISCO.
  >   > If you decide to try it, please read the short manuel at:
  >   > =
http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
  >   > The code is located at:
  >   > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
  >   > If you have any questions, you are welcome to ask.
  >   > Any request for any help and support is welcome.
  >   >=20
  >   > Regards,
  >   >  Vadim.
  >=20
  >   > _______________________________________________
  >   > Quagga-dev mailing list
  >   > Qua...@li...
  >   > http://lists.quagga.net/mailman/listinfo/quagga-dev
  >=20
  >=20
  >=20
  >=20
  >   -------------------------------------------------------
  >   This SF.Net email is sponsored by: Oracle 10g
  >   Get certified on the hottest thing ever to hit the market... =
Oracle 10g.=20
  >   Take an Oracle 10g class now, and we'll give you the exam FREE.
  >   http://ads.osdn.com/?ad_id=3D3149&alloc_id=3D8166&op=3Dclick
  >   _______________________________________________
  >   mpls-linux-general mailing list
  >   mpl...@li...
  >   https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

  --=20
  James R. Leu
  jl...@mi...

[mpls-linux-general] packet identification

[Muhammad R. S. <sa...@cc...>]

In reference to my previous mail, basically I want the ingress router to =
read specific information in the application layer header and then set =
EXP value and forward the packet. It is basically an If-Else situation:

 If this (in application payloiad) -> then EXP value =3D x
 else EXP value =3D y

Is this possible. If yes then please let me know how?
Looking forward for your kind cooperation.
regards

----------

Muhammad R. Sami
Research Assistant,
Computer Engineering Department
P.O.Box 354
King Fahd University of Petroleum & Minerals
Dhahran 31261
Saudi Arabia.
Tel: +96638601423
Cell: +96657982951
www.ccse.kfupm.edu.sa/sami

Re: [mpls-linux-general] waiting for your feedback

[James R. L. <jl...@mi...>]

Sorry about the delay.

I've been doing some thinking on this and I just want to make sure you have
everything setup correctly.  Without the iptables commands, do your test
packets go out the correct interface? (ie is there a IPv4 route for the
destination address).  I would make sure you can get this working via
IPv4 before adding in MPLS.  After you have it work via IPv4, then add MPLS
and remove any IPv4 routing info on the LSR.

For further testing of iptables and spec_nh, change the following lines in 
the target() function (from net/ipv4/netfilter/ipt_spec_nh.c):

        if ((spec_nh = spec_nh_find(spec_nh_info->proto)))
                spec_nh->func((*pskb)->dst, spec_nh_info->data, spec_nh);


		-- to --

	printk("SPEC_NH proto: 0x%04x\n", spec_nh_info->proto);
        if ((spec_nh = spec_nh_find(spec_nh_info->proto))) {
		printk("SPEC_NH ptr: %p\n", spec_nh);
                spec_nh->func((*pskb)->dst, spec_nh_info->data, spec_nh);
	}

These printks will result show up in the output of dmesg after you have tried
to send traffic that hits this rule in iptables.

On Mon, Jun 07, 2004 at 07:44:11AM +0300, Itrat Rasod Quadri wrote:
> Hello,
> 
> I am waiting for your feedback regarding iptables. Kindly give me further 
> guidance.
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] waiting for your feedback

[Itrat R. Q. <iq...@cc...>]

Hello,

I am waiting for your feedback regarding iptables. Kindly give me further 
guidance.

[mpls-linux-general] u need to get urself high salary now pie repetition practice

[Melda C. <cum...@ap...>]

lightning able ask daughter build pay world, remember eleven stopped sign excuse enjoy servant"



    O N L I N E   U N I V E R S I T Y   D I P L O M A S   D E G R E E S

                    Obtain Diploma, Degree, Master
                  
           We send the certificate to all countries (WORLDWIDE)

            Consider a prosperous future, money earning power
    
             No tests, study, coursework, or interviews required. 
                      Discrete and affordable.
                         Everyone eligible. 

                 Call now - your diploma awaits you!!!

                  212-330-8202 (24 hours on call)
                    
                     Calls returned promptly.
                     Confidentiality assured.


 CALL NOW ----->>>  212-330-8202 (24 hours on call)
 
 

heard spoke aunt hundred soon perform fly, attention speak blood along? dont wished open looks realize promised twenty cheat supper sun, play began temper died strength either table reference become success.

RE: [mpls-linux-general] Binding a MOI to a tunnel in kernel 2.6

[Ramon C. <cas...@in...>]

Hi James,Jonathan,

Finally I can come back to the code after some time in other projects..
I'll take a look at that. There are also 2 students that are working on
2.6 which will compare different implementations. They have set up debian
LSRs and are documenting everything.

IIRC, it was possible to dump an hex number as a MOI (atoi-like function
takes care of the base)...

I'll take a look at this... two questions:

* MOI 2 is the tunnel MOI?
If you use moi A to have a set of ops that finish with a FWD to another
MOI that has the same number (A) weird things may happen...

* Are wrong binding and something happened executed in completely
incorrelated kernels ? (e.g. boot, test config, reboot, test config 2)


best regards,
R.



On Fri, 4 Jun 2004 Jon...@cs... wrote:

> Hi James,
>
> Thanks for your hints on looking at the "dmesg".
>
> It seems that in the current code I should not echo a hex number to moi.
> If I use a decimal number, everything seems set but there was a complain
> in the dmesg about "assertion failed at net/ipv4/devinet.c (941)"!!!
> i.e.,
>
> [root@saturn root]# cat /proc/net/mpls/*
> Iface   LSpc    Refcnt
>     lo    -1     9
>   eth0    -1     9
>   eth1     0     7
>   eth2     0     5
>   eth3    -1     1
>   eth4    -1     1
>   eth5    -1     1
> tunnel1   -1     3
> MOI Key:0x00000002 Instruction Set
> PUSH PUSH(gen 2000)
> SET SET(eth1,10.70.10.1)
> tunnel1 0x00000002
>
> However, if I looked at the dmesg (see below), there was an
> error/warning. Is that a worry??
>
> Thanks again for your help...
>
> Cheers,
> Jonathan
>
>
> [wrong binding]
> echo "0x2" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> *** dmesg ***
> MPLS DEBUG net/mpls/mpls_tunnel.c:225:mpls_tunnel_set_moi: enter
> MPLS DEBUG net/mpls/mpls_tunnel.c:235:mpls_tunnel_set_moi: reset moi 0
> MPLS DEBUG net/mpls/mpls_tunnel.c:239:mpls_tunnel_set_moi: exit
>
> [something happened]
> echo "2" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> *** dmesg ***
> MPLS DEBUG net/mpls/mpls_tunnel.c:225:mpls_tunnel_set_moi: enter
> MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 5
> MPLS DEBUG net/mpls/mpls_tunnel.c:382:mpls_tunnel_change_mtu: enter
> MPLS DEBUG net/mpls/mpls_tunnel.c:385:mpls_tunnel_change_mtu: exit
> RTNL: assertion failed at net/ipv4/devinet.c (941)
> Call Trace:
>  [<0226ca6f>] inetdev_event+0x4c/0x14e
>  [<0212888a>] notifier_call_chain+0x17/0x2b
>  [<02238944>] dev_set_mtu+0x54/0x5b
>  [<0228c38d>] mpls_tunnel_set_moi+0x1e5/0x221
>  [<0228c9de>] mpls_tunnel_store_moi+0x31/0x40
>  [<0228c9ad>] mpls_tunnel_store_moi+0x0/0x40
>  [<0228ca3a>] mpls_tunnel_attr_store+0x1a/0x22
>  [<0217c8d6>] flush_write_buffer+0x1d/0x22
>  [<0217c900>] sysfs_write_file+0x25/0x38
>  [<0214ea3d>] vfs_write+0xb8/0xe4
>  [<0214ead7>] sys_write+0x2c/0x42
>
> MPLS DEBUG net/mpls/mpls_tunnel.c:267:mpls_tunnel_set_moi: exit
>
>
> > -----Original Message-----
> > From: James R. Leu [mailto:jl...@mi...]
> > Sent: Friday, 4 June 2004 12:01 AM
> > To: Chan, Jonathan (ICT Centre, Marsfield)
> > Cc: mpl...@li...
> > Subject: Re: [mpls-linux-general] Binding a MOI to a tunnel
> > in kernel 2.6
> >
> >
> > Can you send me the output of 'dmesg' after doing the above steps?
> >
> > Thanks
> >
> > On Thu, Jun 03, 2004 at 06:32:14PM +1000,
> > Jon...@cs... wrote:
> > > Dear all,
> > >
> > > Just upgraded one of my linux mpls boxes to Fedora Core 2 and linux
> > > mpls 1.992. Sorry if this question has been asked before... But how
> > > can I bind a MOI to a tunnel??
> > >
> > > Basically, I tried to use "echo 0xkey >
> > > /sys/mpls/mpls_tunnel/mtp-tunnel_name/moi. But nothing
> > seems being set
> > > if I look at /proc/net/mpls.
> > >
> > > Did I do anything stupid or am I just looking at the wrong place??
> > > This is the log of events...
> > >
> > > [root@saturn]# mplsadm2 -AO 0 -o
> > > push:gen:2000:set:eth1:ipv4:10.70.10.1
> > > MPLSADM mplsadm.c:692:main: Out segment input: 0
> > > MPLSADM mplsadm.c:688:main: Out instr input:
> > > push:gen:2000:set:eth1:ipv4:10.70.10.1
> > > Key: 0x00000003
> > > Out Segment add: Success
> > > MPLSADM mplsadm.c:292:fill_instructions: Instruction: push
> > > MPLSADM mplsadm.c:229:fill_label: Label type: gen
> > > MPLSADM mplsadm.c:292:fill_instructions: Instruction: set
> > > MPLSADM mplsadm.c:181:parse_nh_info: eth1
> > > MPLSADM mplsadm.c:182:parse_nh_info: 10.70.10.1
> > > MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol: ipv4
> > > MPLSADM mplsadm.c:596:fill_instructions: Length: 2
> > > Out Instr: Success
> > >
> > > [root@saturn]# mplsadm2 -AT tunnel1
> > > MPLSADM mplsadm.c:696:main: Tunnel input: tunnel1
> > >
> > > [root@saturn]# ifconfig tunnel1 10.70.10.2 netmask 255.255.255.255
> > >
> > > [root@saturn]# mplsadm2 -BO 0x00000003 -T tunnel1
> > > MPLSADM mplsadm.c:692:main: Out segment input: 0x00000003 MPLSADM
> > > mplsadm.c:696:main: Tunnel input: tunnel1 Using mplsadm2 to
> > > bind/unbind MOIs to tunnels is deprecated in 2.6
> > > Use:
> > > echo "<key>|0" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> > >  to bind / unbind a MOI to a tunnel
> > > Bind/Unbind MOI: Invalid argument
> > >
> > > [root@saturn]# echo "0x3" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> > >
> > > [root@saturn]# cat  /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> > > moi: 0
> > >
> > > [root@saturn]# cat /proc/net/mpls/tunnels
> > > tunnel1 0x00000000
> > >
> > > Any comments/suggestions are much appreciated...
> > >
> > > Cheers,
> > > Jonathan
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by the new InstallShield X.
> > > >From Windows to Linux, servers to mobile, InstallShield X
> > is the one
> > > installation-authoring solution that does it all. Learn more and
> > > evaluate today! http://www.installshield.com/Dev2Dev/0504
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> > --
> > James R. Leu
> > jl...@mi...
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>

// -------------------------------------------------------------------
// Ramon Casellas - GET/ENST/INFRES/RHD/A508 - cas...@in...
// Tel: +33 (0)1 45 81 75 88                 Fax: +33 (0)1 45 81 71 58
// 37/39 rue Dareau 75014 Paris   --    http://perso.enst.fr/~casellas

RE: [mpls-linux-general] Binding a MOI to a tunnel in kernel 2.6

[<Jon...@cs...>]

Hi James,

Thanks for your hints on looking at the "dmesg".

It seems that in the current code I should not echo a hex number to moi.
If I use a decimal number, everything seems set but there was a complain
in the dmesg about "assertion failed at net/ipv4/devinet.c (941)"!!!
i.e.,

[root@saturn root]# cat /proc/net/mpls/*
Iface   LSpc    Refcnt
    lo    -1     9
  eth0    -1     9
  eth1     0     7
  eth2     0     5
  eth3    -1     1
  eth4    -1     1
  eth5    -1     1
tunnel1   -1     3
MOI Key:0x00000002 Instruction Set
PUSH PUSH(gen 2000)
SET SET(eth1,10.70.10.1)
tunnel1 0x00000002

However, if I looked at the dmesg (see below), there was an
error/warning. Is that a worry??

Thanks again for your help...

Cheers,
Jonathan


[wrong binding]
echo "0x2" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi=20
*** dmesg ***
MPLS DEBUG net/mpls/mpls_tunnel.c:225:mpls_tunnel_set_moi: enter
MPLS DEBUG net/mpls/mpls_tunnel.c:235:mpls_tunnel_set_moi: reset moi 0
MPLS DEBUG net/mpls/mpls_tunnel.c:239:mpls_tunnel_set_moi: exit

[something happened]
echo "2" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
*** dmesg ***
MPLS DEBUG net/mpls/mpls_tunnel.c:225:mpls_tunnel_set_moi: enter
MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 5
MPLS DEBUG net/mpls/mpls_tunnel.c:382:mpls_tunnel_change_mtu: enter
MPLS DEBUG net/mpls/mpls_tunnel.c:385:mpls_tunnel_change_mtu: exit
RTNL: assertion failed at net/ipv4/devinet.c (941)
Call Trace:
 [<0226ca6f>] inetdev_event+0x4c/0x14e
 [<0212888a>] notifier_call_chain+0x17/0x2b
 [<02238944>] dev_set_mtu+0x54/0x5b
 [<0228c38d>] mpls_tunnel_set_moi+0x1e5/0x221
 [<0228c9de>] mpls_tunnel_store_moi+0x31/0x40
 [<0228c9ad>] mpls_tunnel_store_moi+0x0/0x40
 [<0228ca3a>] mpls_tunnel_attr_store+0x1a/0x22
 [<0217c8d6>] flush_write_buffer+0x1d/0x22
 [<0217c900>] sysfs_write_file+0x25/0x38
 [<0214ea3d>] vfs_write+0xb8/0xe4
 [<0214ead7>] sys_write+0x2c/0x42

MPLS DEBUG net/mpls/mpls_tunnel.c:267:mpls_tunnel_set_moi: exit
=20

> -----Original Message-----
> From: James R. Leu [mailto:jl...@mi...]=20
> Sent: Friday, 4 June 2004 12:01 AM
> To: Chan, Jonathan (ICT Centre, Marsfield)
> Cc: mpl...@li...
> Subject: Re: [mpls-linux-general] Binding a MOI to a tunnel=20
> in kernel 2.6
>=20
>=20
> Can you send me the output of 'dmesg' after doing the above steps?
>=20
> Thanks
>=20
> On Thu, Jun 03, 2004 at 06:32:14PM +1000,=20
> Jon...@cs... wrote:
> > Dear all,
> >=20
> > Just upgraded one of my linux mpls boxes to Fedora Core 2 and linux=20
> > mpls 1.992. Sorry if this question has been asked before... But how=20
> > can I bind a MOI to a tunnel??
> >=20
> > Basically, I tried to use "echo 0xkey >=20
> > /sys/mpls/mpls_tunnel/mtp-tunnel_name/moi. But nothing=20
> seems being set=20
> > if I look at /proc/net/mpls.
> >=20
> > Did I do anything stupid or am I just looking at the wrong place??=20
> > This is the log of events...
> >=20
> > [root@saturn]# mplsadm2 -AO 0 -o=20
> > push:gen:2000:set:eth1:ipv4:10.70.10.1
> > MPLSADM mplsadm.c:692:main: Out segment input: 0
> > MPLSADM mplsadm.c:688:main: Out instr input:
> > push:gen:2000:set:eth1:ipv4:10.70.10.1
> > Key: 0x00000003
> > Out Segment add: Success
> > MPLSADM mplsadm.c:292:fill_instructions: Instruction: push
> > MPLSADM mplsadm.c:229:fill_label: Label type: gen
> > MPLSADM mplsadm.c:292:fill_instructions: Instruction: set
> > MPLSADM mplsadm.c:181:parse_nh_info: eth1
> > MPLSADM mplsadm.c:182:parse_nh_info: 10.70.10.1
> > MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol: ipv4
> > MPLSADM mplsadm.c:596:fill_instructions: Length: 2
> > Out Instr: Success
> >=20
> > [root@saturn]# mplsadm2 -AT tunnel1
> > MPLSADM mplsadm.c:696:main: Tunnel input: tunnel1
> >=20
> > [root@saturn]# ifconfig tunnel1 10.70.10.2 netmask 255.255.255.255
> >=20
> > [root@saturn]# mplsadm2 -BO 0x00000003 -T tunnel1
> > MPLSADM mplsadm.c:692:main: Out segment input: 0x00000003 MPLSADM=20
> > mplsadm.c:696:main: Tunnel input: tunnel1 Using mplsadm2 to=20
> > bind/unbind MOIs to tunnels is deprecated in 2.6
> > Use:
> > echo "<key>|0" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> >  to bind / unbind a MOI to a tunnel
> > Bind/Unbind MOI: Invalid argument
> >=20
> > [root@saturn]# echo "0x3" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> > =20
> > [root@saturn]# cat  /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
> > moi: 0
> >=20
> > [root@saturn]# cat /proc/net/mpls/tunnels
> > tunnel1 0x00000000
> >=20
> > Any comments/suggestions are much appreciated...
> >=20
> > Cheers,
> > Jonathan
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.Net email is sponsored by the new InstallShield X.
> > >From Windows to Linux, servers to mobile, InstallShield X=20
> is the one
> > installation-authoring solution that does it all. Learn more and=20
> > evaluate today! http://www.installshield.com/Dev2Dev/0504
> > _______________________________________________
> > mpls-linux-general mailing list=20
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>=20
> --=20
> James R. Leu
> jl...@mi...
>=20

Re: [mpls-linux-general] Binding a MOI to a tunnel in kernel 2.6

[James R. L. <jl...@mi...>]

Can you send me the output of 'dmesg' after doing the above steps?

Thanks

On Thu, Jun 03, 2004 at 06:32:14PM +1000, Jon...@cs... wrote:
> Dear all,
> 
> Just upgraded one of my linux mpls boxes to Fedora Core 2 and linux mpls
> 1.992. Sorry if this question has been asked before... But how can I
> bind a MOI to a tunnel??
> 
> Basically, I tried to use "echo 0xkey >
> /sys/mpls/mpls_tunnel/mtp-tunnel_name/moi. But nothing seems being set
> if I look at /proc/net/mpls.
> 
> Did I do anything stupid or am I just looking at the wrong place?? This
> is the log of events...
> 
> [root@saturn]# mplsadm2 -AO 0 -o push:gen:2000:set:eth1:ipv4:10.70.10.1
> MPLSADM mplsadm.c:692:main: Out segment input: 0
> MPLSADM mplsadm.c:688:main: Out instr input:
> push:gen:2000:set:eth1:ipv4:10.70.10.1
> Key: 0x00000003
> Out Segment add: Success
> MPLSADM mplsadm.c:292:fill_instructions: Instruction: push
> MPLSADM mplsadm.c:229:fill_label: Label type: gen
> MPLSADM mplsadm.c:292:fill_instructions: Instruction: set
> MPLSADM mplsadm.c:181:parse_nh_info: eth1
> MPLSADM mplsadm.c:182:parse_nh_info: 10.70.10.1
> MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol: ipv4
> MPLSADM mplsadm.c:596:fill_instructions: Length: 2
> Out Instr: Success
> 
> [root@saturn]# mplsadm2 -AT tunnel1
> MPLSADM mplsadm.c:696:main: Tunnel input: tunnel1
> 
> [root@saturn]# ifconfig tunnel1 10.70.10.2 netmask 255.255.255.255
> 
> [root@saturn]# mplsadm2 -BO 0x00000003 -T tunnel1
> MPLSADM mplsadm.c:692:main: Out segment input: 0x00000003
> MPLSADM mplsadm.c:696:main: Tunnel input: tunnel1
> Using mplsadm2 to bind/unbind MOIs to tunnels is deprecated in 2.6 
> Use: 
> echo "<key>|0" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
>  to bind / unbind a MOI to a tunnel
> Bind/Unbind MOI: Invalid argument
> 
> [root@saturn]# echo "0x3" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
>  
> [root@saturn]# cat  /sys/mpls/mpls_tunnel/mtp-tunnel1/moi 
> moi: 0
> 
> [root@saturn]# cat /proc/net/mpls/tunnels 
> tunnel1 0x00000000
> 
> Any comments/suggestions are much appreciated...
> 
> Cheers,
> Jonathan
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-general] packet identification

[James R. L. <jl...@mi...>]

On Thu, Jun 03, 2004 at 09:44:21AM +0300, Muhammad R. Sami wrote:
> hello,
> I am relatively new in this group, I want to add a packet identification scheme in a MPLS router, and then based on the application layer, want to set EXP bits value. Can anyone help me on this one, like is it already implemented, if not, what files do I have to play with. 
> looking forward for your kind guidance.
> regards

There already exists some mechanisms for EXP setting.  Although there is
probably area for improvment.  I should not that I have not tested EXP
setting for about a year and a significant amount of development has
occureded since then, so you may run into some bugs, if so let me know and
I'll try and produce fixes.

A quick overview of what you will need to setup:
-bind a IPv4 route to a LSP
-use iptables to identify and mark packets
-use the markings to set EXP values (or choose differnt LSPs)
-use EXP value to determin queuing priority

> Muhammad R. Sami
> Research Assistant,
> Computer Engineering Department
> P.O.Box 354
> King Fahd University of Petroleum & Minerals
> Dhahran 31261
> Saudi Arabia.
> Tel: +96638601423
> Cell: +96657982951
> www.ccse.kfupm.edu.sa/sami
>   ----- Original Message ----- 
>   From: James R. Leu 
>   To: Vadim Suraev 
>   Cc: Qua...@li... ; mpl...@li... 
>   Sent: Tuesday, June 01, 2004 5:39 PM
>   Subject: [mpls-linux-general] Re: [quagga-dev 1233] RSVP-TE, OSPF-TE free source code
> 
> 
>   I'd like to work with you to clean up the layout of the code, port
>   to quagga, and integrate with my MPLS infrastructure work.  If you are
>   interested in such an effort, please respond to the list, otherwise I
>   will begin the effort myself.  Thank you for your contribution.
> 
>   BTW I didn't see a license or copyright in any of the files.  You will
>   probably want to do that. 
> 
>   (I've CC'd the mpls-linux mailing list)
> 
>   -- 
>   James R. Leu
>   jl...@mi...
> 
>   On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
>   > Hi.
>   > I'd like to contribute to the Zebra users & developers' community several software 
>   > modules that I've developed recently:
>   > RSVP-TE, TE application, TE extensions for OSPF.
>   > The software has been tested against CISCO.
>   > If you decide to try it, please read the short manuel at:
>   > http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
>   > The code is located at:
>   > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
>   > If you have any questions, you are welcome to ask.
>   > Any request for any help and support is welcome.
>   > 
>   > Regards,
>   >  Vadim.
> 
>   > _______________________________________________
>   > Quagga-dev mailing list
>   > Qua...@li...
>   > http://lists.quagga.net/mailman/listinfo/quagga-dev
> 
> 
> 
> 
>   -------------------------------------------------------
>   This SF.Net email is sponsored by: Oracle 10g
>   Get certified on the hottest thing ever to hit the market... Oracle 10g. 
>   Take an Oracle 10g class now, and we'll give you the exam FREE.
>   http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
>   _______________________________________________
>   mpls-linux-general mailing list
>   mpl...@li...
>   https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] packet identification

[Muhammad R. S. <sa...@cc...>]

hello,
I am relatively new in this group, I want to add a packet identification =
scheme in a MPLS router, and then based on the application layer, want =
to set EXP bits value. Can anyone help me on this one, like is it =
already implemented, if not, what files do I have to play with.=20
looking forward for your kind guidance.
regards

Muhammad R. Sami
Research Assistant,
Computer Engineering Department
P.O.Box 354
King Fahd University of Petroleum & Minerals
Dhahran 31261
Saudi Arabia.
Tel: +96638601423
Cell: +96657982951
www.ccse.kfupm.edu.sa/sami
  ----- Original Message -----=20
  From: James R. Leu=20
  To: Vadim Suraev=20
  Cc: Qua...@li... ; =
mpl...@li...=20
  Sent: Tuesday, June 01, 2004 5:39 PM
  Subject: [mpls-linux-general] Re: [quagga-dev 1233] RSVP-TE, OSPF-TE =
free source code


  I'd like to work with you to clean up the layout of the code, port
  to quagga, and integrate with my MPLS infrastructure work.  If you are
  interested in such an effort, please respond to the list, otherwise I
  will begin the effort myself.  Thank you for your contribution.

  BTW I didn't see a license or copyright in any of the files.  You will
  probably want to do that.=20

  (I've CC'd the mpls-linux mailing list)

  --=20
  James R. Leu
  jl...@mi...

  On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
  > Hi.
  > I'd like to contribute to the Zebra users & developers' community =
several software=20
  > modules that I've developed recently:
  > RSVP-TE, TE application, TE extensions for OSPF.
  > The software has been tested against CISCO.
  > If you decide to try it, please read the short manuel at:
  > http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
  > The code is located at:
  > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
  > If you have any questions, you are welcome to ask.
  > Any request for any help and support is welcome.
  >=20
  > Regards,
  >  Vadim.

  > _______________________________________________
  > Quagga-dev mailing list
  > Qua...@li...
  > http://lists.quagga.net/mailman/listinfo/quagga-dev




  -------------------------------------------------------
  This SF.Net email is sponsored by: Oracle 10g
  Get certified on the hottest thing ever to hit the market... Oracle =
10g.=20
  Take an Oracle 10g class now, and we'll give you the exam FREE.
  http://ads.osdn.com/?ad_id=3D3149&alloc_id=3D8166&op=3Dclick
  _______________________________________________
  mpls-linux-general mailing list
  mpl...@li...
  https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

[mpls-linux-general] Binding a MOI to a tunnel in kernel 2.6

[<Jon...@cs...>]

Dear all,

Just upgraded one of my linux mpls boxes to Fedora Core 2 and linux mpls
1.992. Sorry if this question has been asked before... But how can I
bind a MOI to a tunnel??

Basically, I tried to use "echo 0xkey >
/sys/mpls/mpls_tunnel/mtp-tunnel_name/moi. But nothing seems being set
if I look at /proc/net/mpls.

Did I do anything stupid or am I just looking at the wrong place?? This
is the log of events...

[root@saturn]# mplsadm2 -AO 0 -o push:gen:2000:set:eth1:ipv4:10.70.10.1
MPLSADM mplsadm.c:692:main: Out segment input: 0
MPLSADM mplsadm.c:688:main: Out instr input:
push:gen:2000:set:eth1:ipv4:10.70.10.1
Key: 0x00000003
Out Segment add: Success
MPLSADM mplsadm.c:292:fill_instructions: Instruction: push
MPLSADM mplsadm.c:229:fill_label: Label type: gen
MPLSADM mplsadm.c:292:fill_instructions: Instruction: set
MPLSADM mplsadm.c:181:parse_nh_info: eth1
MPLSADM mplsadm.c:182:parse_nh_info: 10.70.10.1
MPLSADM mplsadm.c:204:parse_nh_info: Nexthop protocol: ipv4
MPLSADM mplsadm.c:596:fill_instructions: Length: 2
Out Instr: Success

[root@saturn]# mplsadm2 -AT tunnel1
MPLSADM mplsadm.c:696:main: Tunnel input: tunnel1

[root@saturn]# ifconfig tunnel1 10.70.10.2 netmask 255.255.255.255

[root@saturn]# mplsadm2 -BO 0x00000003 -T tunnel1
MPLSADM mplsadm.c:692:main: Out segment input: 0x00000003
MPLSADM mplsadm.c:696:main: Tunnel input: tunnel1
Using mplsadm2 to bind/unbind MOIs to tunnels is deprecated in 2.6=20
Use:=20
echo "<key>|0" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
 to bind / unbind a MOI to a tunnel
Bind/Unbind MOI: Invalid argument

[root@saturn]# echo "0x3" > /sys/mpls/mpls_tunnel/mtp-tunnel1/moi
=20
[root@saturn]# cat  /sys/mpls/mpls_tunnel/mtp-tunnel1/moi=20
moi: 0

[root@saturn]# cat /proc/net/mpls/tunnels=20
tunnel1 0x00000000

Any comments/suggestions are much appreciated...

Cheers,
Jonathan

[mpls-linux-general] still having problems with iptables

[Itrat R. Q. <iq...@cc...>]

OK, I tried the command

./iptables <other args> -j spec_nh --spec_nh 0x4788:0x2

but it didn=92t work.

My configuration is something like this

PC            INGRESS        LSR        EGRESS       PC

172.16.70.91  .90  .1      .10 .11     .12  .13      172.16.134.36
|--------------|    |--------|  |--------|   |--------|=20
eth0          eth2 eth0    eth0 eth1  eth0 eth1      eth0

I am using the following iptable commands at the INGRESS

./iptables =96F
./iptables =96P INPUT DROP
./iptables =96P FORWARD DROP
./iptables =96A INPUT =96i lo =96d 127.0.0.1 =96j ACCEPT                 =
       =20
./iptables =96A INPUT =96i eth2 =96d 172.16.134.36 =96j ACCEPT=20
./iptables =96A FORWARD =96i eth2 =96d 172.16.134.36 =96j ACCEPT
./iptables =96A OUTPUT =96o eth0 =96d 172.16.134.36 =96j spec_nh  --spec_=
nh 0x8847:0x2=20

Kindly tell me if there is something wrong with these rules or their orde=
r, if=20
not then kindly mention the specific printk commands to add in the target=
()=20
function of the ipt_spec_nh.c file.

Thanks in advance once again.

[mpls-linux-general] Re: [quagga-dev 1233] RSVP-TE, OSPF-TE free source code

[Vadim S. <su...@ne...>]

James,
----- Original Message ----- 
From: "James R. Leu" <jl...@mi...>
To: "Vadim Suraev" <su...@ne...>
Cc: <Qua...@li...>; <mpl...@li...>
Sent: Tuesday, June 01, 2004 5:39 PM
Subject: Re: [quagga-dev 1233] RSVP-TE, OSPF-TE free source code


> I'd like to work with you to clean up the layout of the code, port
> to quagga, and integrate with my MPLS infrastructure work.  If you are
> interested in such an effort, please respond to the list, otherwise I
> will begin the effort myself.  Thank you for your contribution.
yes, I'm interested to do that with you.
> 
> BTW I didn't see a license or copyright in any of the files.  You will
> probably want to do that. 
yes.
> 
> (I've CC'd the mpls-linux mailing list)
> 
> -- 
> James R. Leu
> jl...@mi...
> 
> On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
> > Hi.
> > I'd like to contribute to the Zebra users & developers' community several software 
> > modules that I've developed recently:
> > RSVP-TE, TE application, TE extensions for OSPF.
> > The software has been tested against CISCO.
> > If you decide to try it, please read the short manuel at:
> > http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
> > The code is located at:
> > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
> > If you have any questions, you are welcome to ask.
> > Any request for any help and support is welcome.
> > 
> > Regards,
> >  Vadim.
> 
> > _______________________________________________
> > Quagga-dev mailing list
> > Qua...@li...
> > http://lists.quagga.net/mailman/listinfo/quagga-dev
> 
>