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

[mpls-linux-general] Help me on iproute2

[<e7...@ti...>]

Hi everybody
before  doing what i've illustrated in the precedent mail i've tryed to
send MPLS packets  from my pc (IP address 10.0.3.100) to another pc (10.0=
.3.17)
following the instruction that are in the mail "Sorry if i ask again" in
this mailing list (except ip route add 10.0.3.17 via 10.0.3.100 lsp 0x000=
00002)
and, after, pinging the other pc. I've seen with ethereal that my pc send=
s
correctly MPLS packets. I've tryed to make the same tsending to other pcs=

and all works well.
After this i've tryed to do
 [root@localhost utils]# mplsadm -A -O 0
  > Key: 0x00000007
  > Out Segment add: Success
  > [root@localhost utils]# mplsadm -O 0x00000007 -o push:gen:16:set:eth0=
:ipv4:10.0.3.17
  > Out Instr: Success
  > [root@localhost utils]# ip route add 10.0.3.17 via 10.0.3.100 lsp 0x0=
0000007
  > Error: either "to" is duplicate, or "lsp" is a garbage. Why does it
work well if there is an error?
What's happened?
Thanks in advance

__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

[mpls-linux-general] Can you help me on iproute2

[<e7...@ti...>]

I've tryed to patch iproute2 like James had told me but i'e the follow er=
ror

[root@localhost iproute2]# make
make[1]: Entering directory `/home/efacchin/iproute2/lib'
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -in=
clude
../include-glibc/glibc-bugs.h -I/usr/src/linux-2.4.20/include/ -I../inclu=
de
   -c -o ll_map.o ll_map.c
In file included from /usr/include/sys/socket.h:35,
                 from ll_map.c:18:
../include-glibc/bits/socket.h:33: warning: redefinition of `socklen_t'
/usr/include/unistd.h:247: warning: `socklen_t' previously declared here
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -in=
clude
../include-glibc/glibc-bugs.h -I/usr/src/linux-2.4.20/include/ -I../inclu=
de
   -c -o libnetlink.o libnetlink.c
In file included from /usr/include/sys/socket.h:35,
                 from /usr/include/net/if_arp.h:29,
                 from libnetlink.c:18:
../include-glibc/bits/socket.h:33: warning: redefinition of `socklen_t'
/usr/include/unistd.h:247: warning: `socklen_t' previously declared here
ar rcs libnetlink.a ll_map.o libnetlink.o
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -in=
clude
../include-glibc/glibc-bugs.h -I/usr/src/linux-2.4.20/include/ -I../inclu=
de
   -c -o utils.o utils.c
In file included from /usr/include/sys/socket.h:35,
                 from utils.c:22:
../include-glibc/bits/socket.h:33: warning: redefinition of `socklen_t'
/usr/include/unistd.h:247: warning: `socklen_t' previously declared here
In file included from utils.c:26:
/usr/include/arpa/inet.h:35: parse error before `inet_addr'
/usr/include/arpa/inet.h:35: warning: data definition has no type or stor=
age
class
/usr/include/arpa/inet.h:38: parse error before `inet_lnaof'
/usr/include/arpa/inet.h:38: warning: data definition has no type or stor=
age
class
/usr/include/arpa/inet.h:42: parse error before `__net'
/usr/include/arpa/inet.h:46: parse error before `inet_netof'
/usr/include/arpa/inet.h:46: warning: data definition has no type or stor=
age
class
/usr/include/arpa/inet.h:50: parse error before `inet_network'
/usr/include/arpa/inet.h:50: warning: data definition has no type or stor=
age
class
/usr/include/arpa/inet.h:74: parse error before `inet_aton'
/usr/include/arpa/inet.h:74: warning: data definition has no type or stor=
age
class
/usr/include/arpa/inet.h:78: parse error before `__net'
make[1]: *** [utils.o] Error 1
make[1]: Leaving directory `/home/efacchin/iproute2/lib'
make: *** [all] Error 2
I've tryed to gave statically socklen.h but it gave me follow error
[root@localhost iproute2]# make
make[1]: Entering directory `/home/efacchin/iproute2/lib'
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -in=
clude
../include-glibc/glibc-bugs.h -I/usr/src/linux-2.4.20/include -I../includ=
e
   -c -o ll_types.o ll_types.c
In file included from /usr/include/sys/socket.h:35,
                 from ll_types.c:18:
../include-glibc/bits/socket.h:33: warning: redefinition of `socklen_t'
/usr/include/unistd.h:247: warning: `socklen_t' previously declared here


gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -in=
clude
../include-glibc/glibc-bugs.h -I/usr/src/linux-2.4.20/include -I../includ=
e
   -c -o ll_proto.o ll_proto.c
In file included from /usr/include/sys/socket.h:35,
                 from ll_proto.c:18:
../include-glibc/bits/socket.h:33: warning: redefinition of `socklen_t'
/usr/include/unistd.h:247: warning: `socklen_t' previously declared here
ll_proto.c:36: `ETH_P_ECHO' undeclared here (not in a function)
ll_proto.c:36: initializer element is not constant
ll_proto.c:36: (near initialization for `llproto_names[1].id')
make[1]: *** [ll_proto.o] Error 1
make[1]: Leaving directory `/home/efacchin/iproute2/lib'
make: *** [all] Error 2
[root@localhost iproute2]# grep -nr ETH_P_ECHO *
[root@localhost iproute2]# grep -nr ETH_P_ECHO /usr/src/linux-2.4.20/*
[root@localhost iproute2]# kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.

[1]+  Done                    kwrite /usr/include/arpa/inet.h
Can you help me?

__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

Re: [mpls-linux-general] LDP + ZEBRA HELP ! config inside ...

[Nicolas T. <nic...@en...>]

Hi,

I have removed all router-id.

zebra pick the address 192.168.0.2 for comp1 et 192.168.0.3 for comp2 =
which are the address of dummy interfaces ..?!

mplsd is still seeing his ldp neighbor but there is still nothing =
exchanged when i type : show ldp database

when i do :

enable
mpls ldp
trace all

i still have the same output on the daemon console with the same errors =
:

adj delete
ENTER: ldp_event
ENTER: ldp_buf_process
ENTER: ldp_decode_header
OUT: 00 01 00 1e c0 a8 00 03 00 01=20
EXIT: ldp_decode_header
ENTER: ldp_decode_one_mesg
OUT: Found type 100
OUT: 01 00 00 14 00 00 00 01 04 00 00 04 00 0f 00 00=20
OUT: 04 02 00 04 00 00 00 06=20
OUT: decodedSize for Hello msg =3D 24
OUT: LPD Header : protocolVersion =3D 1
OUT:    pduLength =3D 30
OUT:    lsrAddress =3D c0a80003
OUT:    labelSpace =3D 1
OUT: HELLO MSG ***START***:
OUT:    baseMsg : uBit =3D 0
OUT:              msgType =3D 100
OUT:              msgLength =3D 20
OUT:              msgId =3D 1
OUT:     chpTlv:
OUT:     Tlv:
OUT:     BaseTlv: uBit =3D 0
OUT:              fBit =3D 0
OUT:              type =3D 400
OUT:              length =3D 4
OUT:     chpTlv data: holdTime =3D 15
OUT:     chpTlv Flags:  target =3D 0
OUT:                    request =3D 0
OUT:                    res =3D 0
OUT:    Hello msg does not have TrAdr TLV
OUT:     csnTlv:
OUT:     Tlv:
OUT:     BaseTlv: uBit =3D 0
OUT:              fBit =3D 0
OUT:              type =3D 402
OUT:              length =3D 4
OUT:     csnTlv data: value =3D 6
OUT: HELLO MSG ***END***:
OUT: Mesg size: 24 (34)
EXIT: ldp_decode_one_mesg
ENTER: ldp_state_machine
OUT: FSM: state 0, event 0
ENTER: ldp_state_new_adjacency
ENTER: ldp_hello_process
OUT: Hello Recv: entity(1)
OUT: ldp_hello_process: PASSIVE(49)
ENTER: ldp_adj_backoff_stop
EXIT: ldp_adj_backoff_stop
EXIT: ldp_hello_process
ENTER: ldp_adj_startup
EXIT: ldp_adj_startup
EXIT: ldp_state_new_adjacency
EXIT: ldp_state_machine
EXIT: ldp_buf_process
ENTER: ldp_buf_process
OUT: ldp_event: LDP_EVENT_UDP_DATA errno =3D 11
EXIT: ldp_buf_process
EXIT: ldp_event

I have also tried to open another udp and tcp port but when i do that i =
have no ldp neighbor seen by mplsd and also some segmentation faults.

thx

Nicolas

Re: [mpls-linux-general] Some questions for you, pleas answer

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

On Thu, Mar 20, 2003 at 12:30:22PM +0100, e7...@ti... wrote:
<snip "how do I use e-mail question">
>   2)I've downloaded mpls-linux-1.172. In it i've found mplsadm. I've read
>    that many people use mplsadm2. My questions are: which is the difference
>   between mplsadm and mplsadm2? How can i download mplsadm2? Can mplsadm2
>    send MPLS packets to other pc?

mplsadm2 serves the same purpose as mplsadm did.  The reason for
creating mplsadm2 is that the underlying communication mechanism with the
kernel changed between mpls-linux-1.0 and mpls-linux-1.1x  (switched from
netlink to IOCTLs)

>   3)I've read that mplsadm can't send packets and that it is useful only
>    to set lsps between pcs and set networks. Is it right?

The is not the purpose of mplsadm(2).  It is the utility that allows you
to create MPLS LSPs.  After creating an LSP you need to map traffic (FEC) to
the LSP and then use normal means of sending packets to that FEC, the
result will be labeled packets.

> -------------------------------------------------------
> This SF.net email is sponsored by: Tablet PC.  
> Does your code think in ink? You could win a Tablet PC. 
> Get a free Tablet PC hat just for playing. What are you waiting for? 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] UML and MPLS

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

First off, as I've said before I use UML with MPLS for _all_ of my
developement testing.  It works if you know what your doing.

Second, I've never tried running UML from a VFAT or FAT32 partition.
In theory you should be able too, check with the UML mailing list for
more help.

Third, I suggest you start simple.  Work on getting 2 UMLs to boot and
setting up a network between them.  Once you get that far, then work on
compiling a UML kernel from source and use that kernel for your 2 node
UML network.  Then finally patch your UML kernel with the mpls-linux patch
and use that kernel for your 2 node network.

You should be able to get lots of info from the UML web site for howto do
most of the above.  If you have any problems consult the UML mailing list.
Once you get to the point were you need to patch your UML kernel with the
mpls-linux patch you should have learned enough that you can do that step
on your own.

Good luck.

On Thu, Mar 20, 2003 at 11:26:16AM +0100, e7...@ti... wrote:
> Hi everybody
> 	i'm going to use UML Linux to test my pc. My scope is to wiew if my pc
> sends MPLS packets  and works well with MPLS . I'd like to do this before
> setting another pc. Many of you had  advised to me to use UML for this scope.
> Is there anyone that has already done it? Are there any problems? Are the
> instruction that are at http://user-mode-linux.sourceforge.net/dl-sf.html
>  correct? I've a problem: i've 2 hard disks, the first that works under
> Linux is nearly full, the second that works under Windows is nearly empty.
> I've thought to download packs for UML on the second disk and build UML
> there. The problem is that  under Windows i can't make symbolik link. COuld
> you help me?
> Thans in advance
> 
> __________________________________________________________________
> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
> Tiscali ADSL non teme confronti! Abbonati subito.
> http://point.tiscali.it/adsl/index.shtml
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Tablet PC.  
> Does your code think in ink? You could win a Tablet PC. 
> Get a free Tablet PC hat just for playing. What are you waiting for? 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Sending packets between 2 pc. How can i do it?

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

> [root@localhost utils]# mplsadm -A -O 0
> Key: 0x00000007
> Out Segment add: Success
> [root@localhost utils]# mplsadm -O 0x00000007 -o push:gen:16:set:eth0:ipv4:10.0.3.17
> Out Instr: Success
> [root@localhost utils]# ip route add 10.0.3.17 via 10.0.3.100 lsp 0x00000007
> Error: either "to" is duplicate, or "lsp" is a garbage. 

You're not using a patched version of iproute2.
Read mpls-linux/patches/README.iproute2

> What's happened?
> How can i  catch up my scope? 
> Thanks in advance
> 
> __________________________________________________________________
> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
> Tiscali ADSL non teme confronti! Abbonati subito.
> http://point.tiscali.it/adsl/index.shtml
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Tablet PC.  
> Does your code think in ink? You could win a Tablet PC. 
> Get a free Tablet PC hat just for playing. What are you waiting for? 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] Sending packets between 2 pc. How can i do it?

[<e7...@ti...>]

Hi everybody
	i've towo pc:the first  that  has 10.0.3.100 like IP address and has MPL=
S
 (mpls-1.172, linux kernel 2.4.20)., the other  with 10.0.3.17 like IP ad=
dress
that hasn't MPLS. I've read a mail where the sender had a situation like
me.  I' d like to send MPLS packets from 10.0.3.100 to 10.0.3.17 and snif=
fing
them with ethereal to see if  th first pc works well with MPLS, wif it se=
nds
packets  and which kind of packets it sends.  I've tryed to do in this wa=
y:
[root@localhost utils]# mplsadm -A -O 0
Key: 0x00000007
Out Segment add: Success
[root@localhost utils]# mplsadm -O 0x00000007 -o push:gen:16:set:eth0:ipv=
4:10.0.3.17
Out Instr: Success
[root@localhost utils]# ip route add 10.0.3.17 via 10.0.3.100 lsp 0x00000=
007
Error: either "to" is duplicate, or "lsp" is a garbage. 
What's happened?
How can i  catch up my scope? 
Thanks in advance

__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

[mpls-linux-general] Some questions for you, pleas answer

[<e7...@ti...>]

Hi everybody
             i've many questions for you
  1)I've read the mail sent to the mailing list but i don't know how i ca=
n
  answer to the senders and how i can ask them something about their mail=
s.
      Could you help me?Reading mails i've seen that only part of their
email
  addresses are visible.
  2)I've downloaded mpls-linux-1.172. In it i've found mplsadm. I've read=

   that many people use mplsadm2. My questions are: which is the differen=
ce
  between mplsadm and mplsadm2? How can i download mplsadm2? Can mplsadm2=

   send MPLS packets to other pc?
  3)I've read that mplsadm can't send packets and that it is useful only
   to set lsps between pcs and set networks. Is it right?
  4) I'm trying to test my pc seeing if it sends MPLS packets. My scope
for
  now is test it before setting another pc. How can i do? I've seen UML
kernel
   with UML utilities but is there anyone that has already used it? Are
there
   any problem using it for my scope? Which kind of problems? Is there an=
other
  solution to do what i want to do?
  Thanks for all in advance

__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

[mpls-linux-general] UML and MPLS

[<e7...@ti...>]

Hi everybody
	i'm going to use UML Linux to test my pc. My scope is to wiew if my pc
sends MPLS packets  and works well with MPLS . I'd like to do this before=

setting another pc. Many of you had  advised to me to use UML for this sc=
ope.
Is there anyone that has already done it? Are there any problems? Are the=

instruction that are at http://user-mode-linux.sourceforge.net/dl-sf.html=

 correct? I've a problem: i've 2 hard disks, the first that works under
Linux is nearly full, the second that works under Windows is nearly empty=
.
I've thought to download packs for UML on the second disk and build UML
there. The problem is that  under Windows i can't make symbolik link. COu=
ld
you help me?
Thans in advance

__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

Re: [mpls-linux-general] LDP + ZEBRA HELP ! config inside ...

[Nicolas T. <nic...@wa...>]

ok thx !

I will try it tomorrow ...

Do you think static in and out segment are ok ?

----- Original Message -----
From: "James R. Leu" <jl...@mi...>
To: "Nicolas Tempestini" <nic...@en...>
Cc: <mpl...@li...>
Sent: Wednesday, March 19, 2003 6:47 PM
Subject: Re: [mpls-linux-general] LDP + ZEBRA HELP ! config inside ...


> The first thing I would do is remove all of your router-id statments
> (from zebra and ospf).  Let the zebra router-id mechanism pick it.
>
>
> On Wed, Mar 19, 2003 at 03:22:54PM -0000, Nicolas Tempestini wrote:
> > Hello,
> >
> > I now try to set up a very small network between 2 machines and try to
use zebra, mplsd and LDP.
> >
> > Here is my config :
> >
> >
> >          |--------------|                    |--------------|
> > -------- | comp 1  |--------------------| comp2    |--------
> >          |--------------|                    |--------------|
> >
> >
> > comp1 is running eth0 with adr Ip xxx.xxx.214.131
> > comp2 is running eth0 with adr Ip xxx.xxx.214.132
> >
> > All other interfaces are down
> >
> > comp1 is running dummy0 interface on 192.168.0.2/32
> > comp2 is running dummy0 interface on 192.168.0.3/32
> >
> > Zebra and opsfd are running perfectly.
> >
> > xxx.xxx.214.129 is a router running Ospf.
> >
> > here are my zebra daemons files  :
> >
> >
> > zebra.conf
> > --------------
> > ! Zebra configuration saved from vty
> > ! 2003/03/19 12:56:14
> >
> > !
> >
> > hostname Router
> >
> > password zebra
> >
> > enable password zebra
> >
> > log file /usr/local/etc/zebra.log
> >
> > !
> >
> > interface lo
> >
> > !
> >
> > interface eth0
> >
> > !
> >
> > interface eth1
> >
> > shutdown
> >
> > !
> >
> > interface dummy0
> >
> > ip address 192.168.0.2/32
> >
> > !
> >
> > router-id xxx.xxx.214.131
> >
> > !
> >
> > line vty
> >
> > !
> >
> > ospfd.conf
> > --------------
> >
> > ! Zebra configuration saved from vty
> >
> > ! 2003/03/14 14:27:47
> >
> > !
> >
> > hostname ospfd
> >
> > password zebra
> >
> > enable password zebra
> >
> > log stdout
> >
> > !
> >
> > interface lo
> >
> > !
> >
> > interface dummy0
> >
> > !
> >
> > interface eth0
> >
> > !
> >
> > interface eth1
> >
> > !
> >
> > router ospf
> >
> > passive-interface dummy0
> >
> > ospf router-id xxx.xxx.214.131
> >
> > ospf abr-type cisco
> >
> > network xxx.xxx.214.128/26 area 1
> >
> > network 192.168.0.0/24 area 1
> >
> > !
> >
> > line vty
> >
> > !
> >
> > mplsd.conf
> >
> > ! Zebra configuration saved from vty
> >
> > ! 2003/03/17 11:07:20
> >
> > !
> >
> > hostname uml-1
> >
> > password mpls
> >
> > enable password mpls
> >
> > !
> >
> > mpls ldp
> >
> > egress connected
> >
> > !
> >
> > interface lo
> >
> > no mpls labelspace
> >
> > !
> >
> > interface eth0
> >
> > mpls labelspace 1
> >
> > mpls ldp
> >
> > !
> >
> > interface eth1
> >
> > mpls labelspace 2
> >
> > mpls ldp
> >
> > !
> >
> > interface dummy0
> >
> > !
> >
> > line vty
> >
> > Here are the output of some mplsd commands :
> >
> > show ldp neighbor
> >
> > Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1
> >
> > TCP connection: n/a
> >
> > State: discovery; Msgs sent/recv: -/-;
> >
> > Up time: -
> >
> > LDP discovery sources:
> >
> > eth0
> >
> > Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1
> >
> > TCP connection: n/a
> >
> > State: discovery; Msgs sent/recv: -/-;
> >
> > Up time: -
> >
> > LDP discovery sources:
> >
> > eth0
> >
> > Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1
> >
> > TCP connection: n/a
> >
> > State: discovery; Msgs sent/recv: -/-;
> >
> > Up time: -
> >
> > LDP discovery sources:
> >
> > eth0
> >
> >
> >
> > uml-1# show ldp database
> >
> > no labeling info has been exchanged
> >
> > uml-1# show lsr-id
> >
> > lsr-id: xxx.xxx.214.131
> >
> >
> >
> > I try to set up static mpls in-segment and out-segment between those
machines using mplsd , here are /proc/net/mpls_*:
> >
> > mpls_in
> >
> > ::::::::::::::
> >
> > 0x008ae005 0/0/0 gen 2222 1 1 POP PEEK
> >
> > ::::::::::::::
> >
> > mpls_labelspace
> >
> > ::::::::::::::
> >
> > eth0 1 37
> >
> > eth1 2 3
> >
> > dummy0 0 3
> >
> > ::::::::::::::
> >
> > mpls_out
> >
> > ::::::::::::::
> >
> > 0x00000010 0/0/0 1 PUSH(gen 1234) SET(eth0,137.194.214.132)
> >
> > ::::::::::::::
> >
> > mpls_tunnel
> >
> > ::::::::::::::
> >
> > ::::::::::::::
> >
> > mpls_version
> >
> > ::::::::::::::
> >
> > 01010702
> >
> >
> >
> > when i do a 'trace all' in mplsd i see that both lsr are speaking
together but there are errors like:
> >
> > chpTlv Flags: target = 0
> >
> > OUT: request = 0
> >
> > OUT: res = 0
> >
> > OUT: Hello msg does not have TrAdr TLV
> >
> > OUT: csnTlv:
> >
> > OUT: Tlv:
> >
> > OUT: BaseTlv: uBit = 0
> >
> > OUT: fBit = 0
> >
> > OUT: type = 402
> >
> > OUT: length = 4
> >
> > OUT: csnTlv data: value = 6
> >
> > OUT: HELLO MSG ***END***:
> >
> > OUT: Mesg size: 24 (34)
> >
> > EXIT: ldp_decode_one_mesg
> >
> > ENTER: ldp_state_machine
> >
> > OUT: FSM: state 0, event 0
> >
> > ENTER: ldp_state_new_adjacency
> >
> > ENTER: ldp_hello_process
> >
> > OUT: Hello Recv: entity(1)
> >
> > OUT: ldp_hello_process: PASSIVE(27)
> >
> > ENTER: ldp_adj_backoff_stop
> >
> > EXIT: ldp_adj_backoff_stop
> >
> > EXIT: ldp_hello_process
> >
> > ENTER: ldp_adj_startup
> >
> > EXIT: ldp_adj_startup
> >
> > EXIT: ldp_state_new_adjacency
> >
> > EXIT: ldp_state_machine
> >
> > EXIT: ldp_buf_process
> >
> > ENTER: ldp_buf_process
> >
> > OUT: ldp_event: LDP_EVENT_UDP_DATA errno = 11
> >
> > EXIT: ldp_buf_process
> >
> > EXIT: ldp_event
> >
> >
> >
> > Can you tell me why There is no label distribution ? and what to do in
order to make it work .... ????
> >
> >
> >
> > THX a lot !
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> James R. Leu
>

Re: [mpls-linux-general] LDP + ZEBRA HELP ! config inside ...

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

The first thing I would do is remove all of your router-id statments
(from zebra and ospf).  Let the zebra router-id mechanism pick it.


On Wed, Mar 19, 2003 at 03:22:54PM -0000, Nicolas Tempestini wrote:
> Hello,
> 
> I now try to set up a very small network between 2 machines and try to use zebra, mplsd and LDP.
> 
> Here is my config :
> 
> 
>          |--------------|                    |--------------| 
> -------- | comp 1  |--------------------| comp2    |--------
>          |--------------|                    |--------------|
> 
> 
> comp1 is running eth0 with adr Ip xxx.xxx.214.131
> comp2 is running eth0 with adr Ip xxx.xxx.214.132
> 
> All other interfaces are down
> 
> comp1 is running dummy0 interface on 192.168.0.2/32
> comp2 is running dummy0 interface on 192.168.0.3/32
> 
> Zebra and opsfd are running perfectly.
> 
> xxx.xxx.214.129 is a router running Ospf.
> 
> here are my zebra daemons files  :
> 
> 
> zebra.conf
> --------------
> ! Zebra configuration saved from vty
> ! 2003/03/19 12:56:14
> 
> !
> 
> hostname Router
> 
> password zebra
> 
> enable password zebra
> 
> log file /usr/local/etc/zebra.log
> 
> !
> 
> interface lo
> 
> !
> 
> interface eth0
> 
> !
> 
> interface eth1
> 
> shutdown
> 
> !
> 
> interface dummy0
> 
> ip address 192.168.0.2/32
> 
> !
> 
> router-id xxx.xxx.214.131
> 
> !
> 
> line vty
> 
> !
> 
> ospfd.conf
> --------------
> 
> ! Zebra configuration saved from vty
> 
> ! 2003/03/14 14:27:47
> 
> !
> 
> hostname ospfd
> 
> password zebra
> 
> enable password zebra
> 
> log stdout
> 
> !
> 
> interface lo
> 
> !
> 
> interface dummy0
> 
> !
> 
> interface eth0
> 
> !
> 
> interface eth1
> 
> !
> 
> router ospf
> 
> passive-interface dummy0
> 
> ospf router-id xxx.xxx.214.131
> 
> ospf abr-type cisco
> 
> network xxx.xxx.214.128/26 area 1 
> 
> network 192.168.0.0/24 area 1 
> 
> !
> 
> line vty
> 
> !
> 
> mplsd.conf
> 
> ! Zebra configuration saved from vty
> 
> ! 2003/03/17 11:07:20
> 
> !
> 
> hostname uml-1
> 
> password mpls
> 
> enable password mpls
> 
> !
> 
> mpls ldp
> 
> egress connected
> 
> !
> 
> interface lo
> 
> no mpls labelspace
> 
> !
> 
> interface eth0
> 
> mpls labelspace 1
> 
> mpls ldp
> 
> !
> 
> interface eth1
> 
> mpls labelspace 2
> 
> mpls ldp
> 
> !
> 
> interface dummy0
> 
> !
> 
> line vty
> 
> Here are the output of some mplsd commands :
> 
> show ldp neighbor
> 
> Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1
> 
> TCP connection: n/a
> 
> State: discovery; Msgs sent/recv: -/-;
> 
> Up time: -
> 
> LDP discovery sources:
> 
> eth0
> 
> Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1
> 
> TCP connection: n/a
> 
> State: discovery; Msgs sent/recv: -/-;
> 
> Up time: -
> 
> LDP discovery sources:
> 
> eth0
> 
> Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1
> 
> TCP connection: n/a
> 
> State: discovery; Msgs sent/recv: -/-;
> 
> Up time: -
> 
> LDP discovery sources:
> 
> eth0
> 
> 
> 
> uml-1# show ldp database
> 
> no labeling info has been exchanged
> 
> uml-1# show lsr-id
> 
> lsr-id: xxx.xxx.214.131
> 
> 
> 
> I try to set up static mpls in-segment and out-segment between those machines using mplsd , here are /proc/net/mpls_*:
> 
> mpls_in
> 
> ::::::::::::::
> 
> 0x008ae005 0/0/0 gen 2222 1 1 POP PEEK 
> 
> :::::::::::::: 
> 
> mpls_labelspace
> 
> ::::::::::::::
> 
> eth0 1 37
> 
> eth1 2 3
> 
> dummy0 0 3
> 
> :::::::::::::: 
> 
> mpls_out
> 
> ::::::::::::::
> 
> 0x00000010 0/0/0 1 PUSH(gen 1234) SET(eth0,137.194.214.132) 
> 
> :::::::::::::: 
> 
> mpls_tunnel
> 
> ::::::::::::::
> 
> :::::::::::::: 
> 
> mpls_version
> 
> ::::::::::::::
> 
> 01010702
> 
> 
> 
> when i do a 'trace all' in mplsd i see that both lsr are speaking together but there are errors like:
> 
> chpTlv Flags: target = 0
> 
> OUT: request = 0
> 
> OUT: res = 0
> 
> OUT: Hello msg does not have TrAdr TLV
> 
> OUT: csnTlv:
> 
> OUT: Tlv:
> 
> OUT: BaseTlv: uBit = 0
> 
> OUT: fBit = 0
> 
> OUT: type = 402
> 
> OUT: length = 4
> 
> OUT: csnTlv data: value = 6
> 
> OUT: HELLO MSG ***END***:
> 
> OUT: Mesg size: 24 (34)
> 
> EXIT: ldp_decode_one_mesg
> 
> ENTER: ldp_state_machine
> 
> OUT: FSM: state 0, event 0
> 
> ENTER: ldp_state_new_adjacency
> 
> ENTER: ldp_hello_process
> 
> OUT: Hello Recv: entity(1)
> 
> OUT: ldp_hello_process: PASSIVE(27)
> 
> ENTER: ldp_adj_backoff_stop
> 
> EXIT: ldp_adj_backoff_stop
> 
> EXIT: ldp_hello_process
> 
> ENTER: ldp_adj_startup
> 
> EXIT: ldp_adj_startup
> 
> EXIT: ldp_state_new_adjacency
> 
> EXIT: ldp_state_machine
> 
> EXIT: ldp_buf_process
> 
> ENTER: ldp_buf_process
> 
> OUT: ldp_event: LDP_EVENT_UDP_DATA errno = 11
> 
> EXIT: ldp_buf_process
> 
> EXIT: ldp_event
> 
> 
> 
> Can you tell me why There is no label distribution ? and what to do in order to make it work .... ????
> 
> 
> 
> THX a lot !
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

-- 
James R. Leu

[mpls-linux-general] LDP + ZEBRA HELP ! config inside ...

[Nicolas T. <nic...@en...>]

Hello,

I now try to set up a very small network between 2 machines and try to =
use zebra, mplsd and LDP.

Here is my config :


         |--------------|                    |--------------|=20
-------- | comp 1  |--------------------| comp2    |--------
         |--------------|                    |--------------|


comp1 is running eth0 with adr Ip xxx.xxx.214.131
comp2 is running eth0 with adr Ip xxx.xxx.214.132

All other interfaces are down

comp1 is running dummy0 interface on 192.168.0.2/32
comp2 is running dummy0 interface on 192.168.0.3/32

Zebra and opsfd are running perfectly.

xxx.xxx.214.129 is a router running Ospf.

here are my zebra daemons files  :


zebra.conf
--------------
! Zebra configuration saved from vty
! 2003/03/19 12:56:14

!

hostname Router

password zebra

enable password zebra

log file /usr/local/etc/zebra.log

!

interface lo

!

interface eth0

!

interface eth1

shutdown

!

interface dummy0

ip address 192.168.0.2/32

!

router-id xxx.xxx.214.131

!

line vty

!

ospfd.conf
--------------

! Zebra configuration saved from vty

! 2003/03/14 14:27:47

!

hostname ospfd

password zebra

enable password zebra

log stdout

!

interface lo

!

interface dummy0

!

interface eth0

!

interface eth1

!

router ospf

passive-interface dummy0

ospf router-id xxx.xxx.214.131

ospf abr-type cisco

network xxx.xxx.214.128/26 area 1=20

network 192.168.0.0/24 area 1=20

!

line vty

!

mplsd.conf

! Zebra configuration saved from vty

! 2003/03/17 11:07:20

!

hostname uml-1

password mpls

enable password mpls

!

mpls ldp

egress connected

!

interface lo

no mpls labelspace

!

interface eth0

mpls labelspace 1

mpls ldp

!

interface eth1

mpls labelspace 2

mpls ldp

!

interface dummy0

!

line vty

Here are the output of some mplsd commands :

show ldp neighbor

Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1

TCP connection: n/a

State: discovery; Msgs sent/recv: -/-;

Up time: -

LDP discovery sources:

eth0

Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1

TCP connection: n/a

State: discovery; Msgs sent/recv: -/-;

Up time: -

LDP discovery sources:

eth0

Peer LDP Ident: xxx.xxx.214.132:0; Local LDP Ident: xxx.xxx.214.131:1

TCP connection: n/a

State: discovery; Msgs sent/recv: -/-;

Up time: -

LDP discovery sources:

eth0



uml-1# show ldp database

no labeling info has been exchanged

uml-1# show lsr-id

lsr-id: xxx.xxx.214.131



I try to set up static mpls in-segment and out-segment between those =
machines using mplsd , here are /proc/net/mpls_*:

mpls_in

::::::::::::::

0x008ae005 0/0/0 gen 2222 1 1 POP PEEK=20

::::::::::::::=20

mpls_labelspace

::::::::::::::

eth0 1 37

eth1 2 3

dummy0 0 3

::::::::::::::=20

mpls_out

::::::::::::::

0x00000010 0/0/0 1 PUSH(gen 1234) SET(eth0,137.194.214.132)=20

::::::::::::::=20

mpls_tunnel

::::::::::::::

::::::::::::::=20

mpls_version

::::::::::::::

01010702



when i do a 'trace all' in mplsd i see that both lsr are speaking =
together but there are errors like:

chpTlv Flags: target =3D 0

OUT: request =3D 0

OUT: res =3D 0

OUT: Hello msg does not have TrAdr TLV

OUT: csnTlv:

OUT: Tlv:

OUT: BaseTlv: uBit =3D 0

OUT: fBit =3D 0

OUT: type =3D 402

OUT: length =3D 4

OUT: csnTlv data: value =3D 6

OUT: HELLO MSG ***END***:

OUT: Mesg size: 24 (34)

EXIT: ldp_decode_one_mesg

ENTER: ldp_state_machine

OUT: FSM: state 0, event 0

ENTER: ldp_state_new_adjacency

ENTER: ldp_hello_process

OUT: Hello Recv: entity(1)

OUT: ldp_hello_process: PASSIVE(27)

ENTER: ldp_adj_backoff_stop

EXIT: ldp_adj_backoff_stop

EXIT: ldp_hello_process

ENTER: ldp_adj_startup

EXIT: ldp_adj_startup

EXIT: ldp_state_new_adjacency

EXIT: ldp_state_machine

EXIT: ldp_buf_process

ENTER: ldp_buf_process

OUT: ldp_event: LDP_EVENT_UDP_DATA errno =3D 11

EXIT: ldp_buf_process

EXIT: ldp_event



Can you tell me why There is no label distribution ? and what to do in =
order to make it work .... ????



THX a lot !

Re: [mpls-linux-general] Can you help me? (I'm trying to see if my pc works well with MPLS on linux before set another pc)

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

UML is my primary testing environment.  I run a 6 node simulation network
on my laptop. (1Ghz CPU, 512MB RAM, 40GB storage)

On Tue, Mar 18, 2003 at 11:01:26AM +0100, e7...@ti... wrote:
> I' ve looked the URL that you've  indicated to me. Before starting to install
> UML kernel, patching it and try  to use it for my scope (test my pc and
> see if it works well with MPLS on Linux) i would know if you (or someone
> that you know) has just used UML kernel to test networking (in particular
> MPLS), if there are any problems with it and , in this case, which kind
> of problems there are. Could you help me?Thanks in advance
> >-- Messaggio Originale --
> >Date: Tue, 11 Mar 2003 10:36:44 -0600
> >From: "James R. Leu" <jl...@mi...>
> >To: e7...@ti...
> >Subject: Re: [mpls-linux-general] mpls-linux speed test.
> >Reply-To: jl...@mi...
> >
> >
> >Look into using user-mode-linux:
> >http://sf.net/projects/user-mode-linux/
> >
> >
> >On Tue, Mar 11, 2003 at 11:23:28AM +0100, e7...@ti... wrote:
> >> Can i test my pc without use another pc? In which way? I'd like to test
> >> my pc before set another personal computer with mpls features
> >> >-- Messaggio Originale --
> >> >Date: Mon, 10 Mar 2003 12:37:50 -0600
> >> >From: "James R. Leu" <jl...@mi...>
> >> >To: e7...@ti...
> >> >Subject: Re: [mpls-linux-general] mpls-linux speed test.
> >> >Reply-To: jl...@mi...
> >> >
> >> >
> >> >mpls-linux/utils/README
> >> >
> >> >On Mon, Mar 10, 2003 at 05:06:38PM +0100, e7...@ti... wrote:
> >> >> i haven't found the example you say
> >> >> Can you specify better where it is? 
> >> >> Thanks
> >> >> >-- Messaggio Originale --
> >> >> >Date: Mon, 10 Mar 2003 10:28:27 -0600
> >> >> >From: "James R. Leu" <jl...@mi...>
> >> >> >To: e7...@ti...
> >> >> >Subject: Re: [mpls-linux-general] mpls-linux speed test.
> >> >> >Reply-To: jl...@mi...
> >> >> >
> >> >> >
> >> >> >To verify that you have a MPLS kernel look in /proc/net/ you should
> >> >> >see some mpls_* files.  You can follow the examples in the mpls-linux
> >> >> >READMEs to test it out for yourself.
> >> >> >
> >> >> >The RSVP-TE for mpls-linux homepage is:
> >> >> >http://dsmpls.atlantis.rug.ac.be/
> >> >> >
> >> >> >On Mon, Mar 10, 2003 at 01:51:44PM +0100, e7...@ti... wrote:
> >> >> >> Excuse me if i ask always you but how can i see if my  mpls-kernel
> >> work
> >> >> >> correctly? I've downloaded klinux-kernel-2.4.20 with the patch
> mpls
> >> >-linux
> >> >> >> -1.172.tar. I've compiled the new kernel with the patch. I've to
> >choose
> >> >> >> between RSVP-TE and LDP (CR-LDP). I would choose RSVP because,
> from
> >> >the
> >> >> >> documents i've read, it supports Traffic Engineering and QoS (instead
> >> >> LDP
> >> >> >> doesn't support them). I've to test MPLS QoS and then i would do
> >this
> >> >> choice.
> >> >> >> Is it correct?
> >> >> >> Thanks
> >> >> >> 
> >> >> >> >-- Messaggio Originale --
> >> >> >> >From: "James R. Leu" <jl...@mi...>
> >> >> >> >To: Radu Dragos <dr...@ee...>
> >> >> >> >Cc: mpl...@li...
> >> >> >> >Subject: Re: [mpls-linux-general] mpls-linux speed test.
> >> >> >> >Reply-To: jl...@mi...
> >> >> >> >Date: Fri, 7 Mar 2003 12:53:37 -0600
> >> >> >> >
> >> >> >> >
> >> >> >> >These are cool results, I would very interested to see the results
> >> >with
> >> >> >> >GigE interfaces.  I would be nice to see if these same results
> cam
> >> >be
> >> >> >> >achived by others.  Also I think testing with traffic on _many_
> >LSPs
> >> >> >> >would be interesting.
> >> >> >> >
> >> >> >> >At some point I would like to concetrate on LER speed as well
> :-/
> >> >> >> >
> >> >> >> >Laters
> >> >> >> >
> >> >> >> >On Fri, Feb 28, 2003 at 12:26:57PM +0000, Radu Dragos wrote:
> >> >> >> >> Hi all.
> >> >> >> >> 
> >> >> >> >> Read this if you are interestet in some mpls-linux forwarding
> >speed
> >> >> >
> >> >> >> issues.
> >> >> >> >> 
> >> >> >> >> Based on a discution with Jim on the IRC channel: #mp...@ir...
> >> >> >> >> I run the following test using a DataQualityAnalizer(DQA):
> >> >> >> >> 
> >> >> >> >> The idea is to stress a MPLS enabled Linux box (AMD 850MHZ,
> 256M
> >> >RAM,
> >> >> >> RH7.3,
> >> >> >> >
> >> >> >> >> linux-2.4.19) in order to verify the capability of the mpls-linux
> >> >> 
> >> >> >> >> implementation to forward large bandwidths of traffic.
> >> >> >> >> 
> >> >> >> >> This is the framework I used:
> >> >> >> >> 
> >> >> >> >> 			192.168.254.7		192.168.254.25	
> >> >> >> >> 			eth1 ------------------------>	analyzer interface (AI)
> >> >> >> >> 				^
> >> >> >> >> 		mpls-linux  |  fwd					 DQA
> >> >> >> >> 				|		 			   
> >> >> >> >> 			eth0 <------------------------	traffic generator interface
> >(TGI)
> >> >> >> >> 			192.168.100.2		192.168.100.1	
> >> >> >> >> 
> >> >> >> >> All the interfaces are 100Mbps Ethernet.
> >> >> >> >> 
> >> >> >> >> 1. Small packets (IP only no MPLS labels)
> >> >> >> >>  TGI sends TCP/IP traffic src=192.168.100.1 dst=192.168.254.25
> >> >> >> >>      packet size 64 Bytes
> >> >> >> >>      transmitted data rate: 76Mbps
> >> >> >> >> At this rate, ~150000 packets/s the linux machine is flooded
> and
> >> >CPU
> >> >> >> 
> >> >> >> >> overloaded  	
> >> >> >> >>     AI gets only ~174 packets/s
> >> >> >> >> 2. Large packets  (IP only no MPLS labels)
> >> >> >> >> TGI sends TCP/IP traffic src=192.168.100.1 dst=192.168.254.25
> >> >> >> >>      packet size 1500 Bytes
> >> >> >> >>      transmitted data rate: ~98Mbps
> >> >> >> >>  At this rate ~8200 packets/s the linux machine behaves well
> 
> >> >> >> >> AI gets all the packets at the same rate TGI is transmitting.
> >> >> >> >> 
> >> >> >> >> 3. Large packets MPLS enabled
> >> >> >> >>  TGI sends TCP/IP traffic src=192.168.100.1 dst=192.168.254.25(MPLS
> >> >> >label
> >> >> >> >16)
> >> >> >> >>      packet size 1500 Bytes
> >> >> >> >>      transmitted data rate: ~98Mbps
> >> >> >> >> All the MPLS packets received at eth0 were forwarded to AI.
> No
> >> packet
> >> >> >> was
> >> >> >> >lost 
> >> >> >> >> as you can see from /proc/net/mpls*  :
> >> >> >> >> 
> >> >> >> >> 0x40004000 718224/1064407968/0 gen 16 0 1 POP FWD(0x00000002)
> >> >> >> >> eth0    0       6
> >> >> >> >> eth1    0       28
> >> >> >> >> 0x00000002 718224/1061535072/0 2 PUSH(gen 16) SET(eth1,192.168.254.25)
> >> >> >> >> 
> >> >> >> >> No significant CPU load was observed.
> >> >> >> >> The mpls for linux implementation is able to forward packets
> at
> >> FastEthernet
> >> >> >> >
> >> >> >> >> speeds.
> >> >> >> >> 
> >> >> >> >> I poses Gbit Ethernet interfaces for PS. Unfortunately I only
> >have
> >> >> one
> >> >> >> >Gbit 
> >> >> >> >> interface on DQA. Therefore, for the moment I can not run tests
> >> at
> >> >> Gbit
> >> >> >> >
> >> >> >> >> speed.
> >> >> >> >> 
> >> >> >> >> It remains now to analise the results in order to establish
> the
> >> delay
> >> >> >> 
> >> >> >> >> introduced by the MPLS forwarding plane.
> >> >> >> >> 
> >> >> >> >> Also, it remains the issue of variable size packets. 
> >> >> >> >> 
> >> >> >> >> All the comments or suggestions are wellcome.
> >> >> >> >> 
> >> >> >> >> Radu
> >> >> >> >> 
> >> >> >> >> 
> >> >> >> >> -------------------------------------------------------
> >> >> >> >> This sf.net email is sponsored by:ThinkGeek
> >> >> >> >> Welcome to geek heaven.
> >> >> >> >> http://thinkgeek.com/sf
> >> >> >> >> _______________________________________________
> >> >> >> >> mpls-linux-general mailing list
> >> >> >> >> mpl...@li...
> >> >> >> >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >> >> >> >
> >> >> >> >-- 
> >> >> >> >James R. Leu
> >> >> >> >
> >> >> >> >
> >> >> >> >-------------------------------------------------------
> >> >> >> >This SF.net email is sponsored by: Etnus, makers of TotalView,
> The
> >> >debugger
> >> >> >> >
> >> >> >> >for complex code. Debugging C/C++ programs can leave you feeling
> >> lost
> >> >> >and
> >> >> >> >
> >> >> >> >disoriented. TotalView can help you find your way. Available on
> >major
> >> >> >UNIX
> >> >> >> >
> >> >> >> >and Linux platforms. Try it free. www.etnus.com
> >> >> >> >_______________________________________________
> >> >> >> >mpls-linux-general mailing list
> >> >> >> >mpl...@li...
> >> >> >> >https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >> >> >> 
> >> >> >> 
> >> >> >> __________________________________________________________________
> >> >> >> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light
> >> Mega!
> >> >> >> Tiscali ADSL non teme confronti! Abbonati subito.
> >> >> >> http://point.tiscali.it/adsl/index.shtml
> >> >> >> 
> >> >> >> 
> >> >> >
> >> >> >-- 
> >> >> >James R. Leu
> >> >> 
> >> >> 
> >> >> __________________________________________________________________
> >> >> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light
> Mega!
> >> >> Tiscali ADSL non teme confronti! Abbonati subito.
> >> >> http://point.tiscali.it/adsl/index.shtml
> >> >> 
> >> >> 
> >> >
> >> >-- 
> >> >James R. Leu
> >> 
> >> 
> >> __________________________________________________________________
> >> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
> >> Tiscali ADSL non teme confronti! Abbonati subito.
> >> http://point.tiscali.it/adsl/index.shtml
> >> 
> >> 
> >
> >-- 
> >James R. Leu
> 
> 
> __________________________________________________________________
> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
> Tiscali ADSL non teme confronti! Abbonati subito.
> http://point.tiscali.it/adsl/index.shtml
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink? 
> You could win a Tablet PC. Get a free Tablet PC hat just for playing. 
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] Help me please

[<e7...@ti...>]

Hi everybody
	i've many questions for you
1)I've read the mail sent to the mailing list but i don't know how i can
answer to the senders and how i can ask them something about their mails.=

Could you help me?Reading mails i've seen that only part of their email
addresses are visible.
2)I've downloaded mpls-linux-1.172. In it i've found mplsadm. I've read
that many people use mplsadm2. My questions are: which is the difference
between mplsadm and mplsadm2? How can i download mplsadm2? Can mplsadm2
send MPLS packets to other pc?
3)I've read that mplsadm can't  send packets and that it is useful only
to set lsps between pcs and set networks. Is it right?
4) I'm trying to test my pc seeing if it sends MPLS packets. My scope for=

now is test it before setting another pc. How can i do? I've seen UML ker=
nel
with UML utilities but is there anyone that has already used it? Are ther=
e
any problem using it for my scope? Which kind of problems? Is there anoth=
er
solution to do what i want to do?
Thanks for all in advance

__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

[mpls-linux-general] Can you help me? (I'm trying to see if my pc works well with MPLS on linux before set another pc)

[<e7...@ti...>]

I' ve looked the URL that you've  indicated to me. Before starting to ins=
tall
UML kernel, patching it and try  to use it for my scope (test my pc and
see if it works well with MPLS on Linux) i would know if you (or someone
that you know) has just used UML kernel to test networking (in particular=

MPLS), if there are any problems with it and , in this case, which kind
of problems there are. Could you help me?Thanks in advance
>-- Messaggio Originale --
>Date: Tue, 11 Mar 2003 10:36:44 -0600
>From: "James R. Leu" <jl...@mi...>
>To: e7...@ti...
>Subject: Re: [mpls-linux-general] mpls-linux speed test.
>Reply-To: jl...@mi...
>
>
>Look into using user-mode-linux:
>http://sf.net/projects/user-mode-linux/
>
>
>On Tue, Mar 11, 2003 at 11:23:28AM +0100, e7...@ti... wrote:
>> Can i test my pc without use another pc? In which way? I'd like to tes=
t
>> my pc before set another personal computer with mpls features
>> >-- Messaggio Originale --
>> >Date: Mon, 10 Mar 2003 12:37:50 -0600
>> >From: "James R. Leu" <jl...@mi...>
>> >To: e7...@ti...
>> >Subject: Re: [mpls-linux-general] mpls-linux speed test.
>> >Reply-To: jl...@mi...
>> >
>> >
>> >mpls-linux/utils/README
>> >
>> >On Mon, Mar 10, 2003 at 05:06:38PM +0100, e7...@ti... wrote:
>> >> i haven't found the example you say
>> >> Can you specify better where it is? 
>> >> Thanks
>> >> >-- Messaggio Originale --
>> >> >Date: Mon, 10 Mar 2003 10:28:27 -0600
>> >> >From: "James R. Leu" <jl...@mi...>
>> >> >To: e7...@ti...
>> >> >Subject: Re: [mpls-linux-general] mpls-linux speed test.
>> >> >Reply-To: jl...@mi...
>> >> >
>> >> >
>> >> >To verify that you have a MPLS kernel look in /proc/net/ you shoul=
d
>> >> >see some mpls_* files.  You can follow the examples in the mpls-li=
nux
>> >> >READMEs to test it out for yourself.
>> >> >
>> >> >The RSVP-TE for mpls-linux homepage is:
>> >> >http://dsmpls.atlantis.rug.ac.be/
>> >> >
>> >> >On Mon, Mar 10, 2003 at 01:51:44PM +0100, e7...@ti... wrote:
>> >> >> Excuse me if i ask always you but how can i see if my  mpls-kern=
el
>> work
>> >> >> correctly? I've downloaded klinux-kernel-2.4.20 with the patch
mpls
>> >-linux
>> >> >> -1.172.tar. I've compiled the new kernel with the patch. I've to=

>choose
>> >> >> between RSVP-TE and LDP (CR-LDP). I would choose RSVP because,
from
>> >the
>> >> >> documents i've read, it supports Traffic Engineering and QoS (in=
stead
>> >> LDP
>> >> >> doesn't support them). I've to test MPLS QoS and then i would do=

>this
>> >> choice.
>> >> >> Is it correct?
>> >> >> Thanks
>> >> >> 
>> >> >> >-- Messaggio Originale --
>> >> >> >From: "James R. Leu" <jl...@mi...>
>> >> >> >To: Radu Dragos <dr...@ee...>
>> >> >> >Cc: mpl...@li...
>> >> >> >Subject: Re: [mpls-linux-general] mpls-linux speed test.
>> >> >> >Reply-To: jl...@mi...
>> >> >> >Date: Fri, 7 Mar 2003 12:53:37 -0600
>> >> >> >
>> >> >> >
>> >> >> >These are cool results, I would very interested to see the resu=
lts
>> >with
>> >> >> >GigE interfaces.  I would be nice to see if these same results
cam
>> >be
>> >> >> >achived by others.  Also I think testing with traffic on _many_=

>LSPs
>> >> >> >would be interesting.
>> >> >> >
>> >> >> >At some point I would like to concetrate on LER speed as well
:-/
>> >> >> >
>> >> >> >Laters
>> >> >> >
>> >> >> >On Fri, Feb 28, 2003 at 12:26:57PM +0000, Radu Dragos wrote:
>> >> >> >> Hi all.
>> >> >> >> 
>> >> >> >> Read this if you are interestet in some mpls-linux forwarding=

>speed
>> >> >
>> >> >> issues.
>> >> >> >> 
>> >> >> >> Based on a discution with Jim on the IRC channel: #mpls@irc.f=
reenode.net
>> >> >> >> I run the following test using a DataQualityAnalizer(DQA):
>> >> >> >> 
>> >> >> >> The idea is to stress a MPLS enabled Linux box (AMD 850MHZ,
256M
>> >RAM,
>> >> >> RH7.3,
>> >> >> >
>> >> >> >> linux-2.4.19) in order to verify the capability of the mpls-l=
inux
>> >> 
>> >> >> >> implementation to forward large bandwidths of traffic.
>> >> >> >> 
>> >> >> >> This is the framework I used:
>> >> >> >> 
>> >> >> >> 			192.168.254.7		192.168.254.25	
>> >> >> >> 			eth1 ------------------------>	analyzer interface (AI)
>> >> >> >> 				^
>> >> >> >> 		mpls-linux  |  fwd					 DQA
>> >> >> >> 				|		 			   
>> >> >> >> 			eth0 <------------------------	traffic generator interface=

>(TGI)
>> >> >> >> 			192.168.100.2		192.168.100.1	
>> >> >> >> 
>> >> >> >> All the interfaces are 100Mbps Ethernet.
>> >> >> >> 
>> >> >> >> 1. Small packets (IP only no MPLS labels)
>> >> >> >>  TGI sends TCP/IP traffic src=3D192.168.100.1 dst=3D192.168.2=
54.25
>> >> >> >>      packet size 64 Bytes
>> >> >> >>      transmitted data rate: 76Mbps
>> >> >> >> At this rate, ~150000 packets/s the linux machine is flooded
and
>> >CPU
>> >> >> 
>> >> >> >> overloaded  	
>> >> >> >>     AI gets only ~174 packets/s
>> >> >> >> 2. Large packets  (IP only no MPLS labels)
>> >> >> >> TGI sends TCP/IP traffic src=3D192.168.100.1 dst=3D192.168.25=
4.25
>> >> >> >>      packet size 1500 Bytes
>> >> >> >>      transmitted data rate: ~98Mbps
>> >> >> >>  At this rate ~8200 packets/s the linux machine behaves well

>> >> >> >> AI gets all the packets at the same rate TGI is transmitting.=

>> >> >> >> 
>> >> >> >> 3. Large packets MPLS enabled
>> >> >> >>  TGI sends TCP/IP traffic src=3D192.168.100.1 dst=3D192.168.2=
54.25(MPLS
>> >> >label
>> >> >> >16)
>> >> >> >>      packet size 1500 Bytes
>> >> >> >>      transmitted data rate: ~98Mbps
>> >> >> >> All the MPLS packets received at eth0 were forwarded to AI.
No
>> packet
>> >> >> was
>> >> >> >lost 
>> >> >> >> as you can see from /proc/net/mpls*  :
>> >> >> >> 
>> >> >> >> 0x40004000 718224/1064407968/0 gen 16 0 1 POP FWD(0x00000002)=

>> >> >> >> eth0    0       6
>> >> >> >> eth1    0       28
>> >> >> >> 0x00000002 718224/1061535072/0 2 PUSH(gen 16) SET(eth1,192.16=
8.254.25)
>> >> >> >> 
>> >> >> >> No significant CPU load was observed.
>> >> >> >> The mpls for linux implementation is able to forward packets
at
>> FastEthernet
>> >> >> >
>> >> >> >> speeds.
>> >> >> >> 
>> >> >> >> I poses Gbit Ethernet interfaces for PS. Unfortunately I only=

>have
>> >> one
>> >> >> >Gbit 
>> >> >> >> interface on DQA. Therefore, for the moment I can not run tes=
ts
>> at
>> >> Gbit
>> >> >> >
>> >> >> >> speed.
>> >> >> >> 
>> >> >> >> It remains now to analise the results in order to establish
the
>> delay
>> >> >> 
>> >> >> >> introduced by the MPLS forwarding plane.
>> >> >> >> 
>> >> >> >> Also, it remains the issue of variable size packets. 
>> >> >> >> 
>> >> >> >> All the comments or suggestions are wellcome.
>> >> >> >> 
>> >> >> >> Radu
>> >> >> >> 
>> >> >> >> 
>> >> >> >> -------------------------------------------------------
>> >> >> >> This sf.net email is sponsored by:ThinkGeek
>> >> >> >> Welcome to geek heaven.
>> >> >> >> http://thinkgeek.com/sf
>> >> >> >> _______________________________________________
>> >> >> >> mpls-linux-general mailing list
>> >> >> >> mpl...@li...
>> >> >> >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-gener=
al
>> >> >> >
>> >> >> >-- 
>> >> >> >James R. Leu
>> >> >> >
>> >> >> >
>> >> >> >-------------------------------------------------------
>> >> >> >This SF.net email is sponsored by: Etnus, makers of TotalView,
The
>> >debugger
>> >> >> >
>> >> >> >for complex code. Debugging C/C++ programs can leave you feelin=
g
>> lost
>> >> >and
>> >> >> >
>> >> >> >disoriented. TotalView can help you find your way. Available on=

>major
>> >> >UNIX
>> >> >> >
>> >> >> >and Linux platforms. Try it free. www.etnus.com
>> >> >> >_______________________________________________
>> >> >> >mpls-linux-general mailing list
>> >> >> >mpl...@li...
>> >> >> >https://lists.sourceforge.net/lists/listinfo/mpls-linux-general=

>> >> >> 
>> >> >> 
>> >> >> ________________________________________________________________=
__
>> >> >> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Lig=
ht
>> Mega!
>> >> >> Tiscali ADSL non teme confronti! Abbonati subito.
>> >> >> http://point.tiscali.it/adsl/index.shtml
>> >> >> 
>> >> >> 
>> >> >
>> >> >-- 
>> >> >James R. Leu
>> >> 
>> >> 
>> >> __________________________________________________________________
>> >> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light
Mega!
>> >> Tiscali ADSL non teme confronti! Abbonati subito.
>> >> http://point.tiscali.it/adsl/index.shtml
>> >> 
>> >> 
>> >
>> >-- 
>> >James R. Leu
>> 
>> 
>> __________________________________________________________________
>> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Meg=
a!
>> Tiscali ADSL non teme confronti! Abbonati subito.
>> http://point.tiscali.it/adsl/index.shtml
>> 
>> 
>
>-- 
>James R. Leu


__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

Re: [mpls-linux-general] Mpls tunnel / Zebra / Ospf

[Nicolas T. <nic...@wa...>]

No i am not really using RSVP-TE. I used it to test the Rsvp implementation.

Today,  i just tried to see how a mpls tunnel can be viewed by OSPF.

In fact, i found a README telling that MPLS tunnel are a way to represent an
LSP to traditional routing protocols in a way which the understand as an
interface ?

If I try to set up an mpls tunnel manually , to create an MPLS tunnel
interface , to assign an Ip address to this tunnel , to bind the outgoing
label to the tunnel and to create a route to forward traffic to the
interface , what will ospfd see ? Perhaps, i am wrong but i want to
understand the relation between mpls tunnel and OSPF...

Furthermore, do u know any doc for mplsd commands ?

Thx

(i changed my adress email ... nic...@en... or @wanadoo.fr are
both valid addresses)




> Are you trying to create a 'RSVP-TE tunnel' which shows up as a
> real interface?  Or are you just try to create an LSP and bind a route
> to it?
>
> Since you previous messages were using RSVP I'm assuming the
aforementioned.
> In which case you should head over to the maling list for RSVP-TE and they
> can help you.  Start by looking at:
>
> http://dsmpls.atlantis.rug.ac.be/
>
> If you are looking for 'OSPF short cuts' they haven't been implemented.
> So far the only protocol related interaction is that routes that area
learned
> by other protocols can be bound to a LSP created by LDP.  Indirect BGP
routes
> can utilize routes which LDP has bound to a LSP as well.
>
> On Fri, Mar 14, 2003 at 05:34:32PM -0000, Nicolas Tempestini wrote:
> > Hello,
> >
> > I have set up a little OSPF network with zebra between some linux boxes
and it is worling fine.
> >
> > I also managed to set up MPLS lsp between those machines.
> >
> > my config is :
> >
> > LInux 2.4.20
> > iptables 1.27a
> > zebra 0.93a patched for mpls
> >
> > Lets say there is only 2 machines running the same config (simple test
...) : machine 1 and machine 2
> >
> >
> > Now i'd like to create a mpls tunnel on a machine 1 with an ip address
given to it , to map the outgoing traffic from for ex. eth0 to machine 2 on
it and to see how ospf understand this tunnel ...
> >
> > What can i do ...
> >
> > i saw we can use mplsadm to create a tunnel but there seems to be errors
...
> >
> > Thx
> >
> > Nicolas
> >
> >
> >
>
> --
> James R. Leu
>

Re: [mpls-linux-general] /proc/net/mpls_out bug with Zebra and LDP (mplsd)

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

I've been trying to 'get my hands around' this problem.  My suggestion is
to add some debugging statments to impl_mpls.c in mpls_mpls_outsegment_add()
and near that places that call that function.  You will be able to see how
info gets copied from zebra structures to LDP structures to the IOCTL
structures.  Hopefully this will point out where the incorrect index
is coming from.

On Fri, Mar 14, 2003 at 05:11:34PM +0100, Markus Hennig wrote:
> Hi all,
> 
> is there someone how can help me with the wrong interface in /proc/net/mpls_out?
> 
> This is my small testseup (UML) - everything latest CVS release,
> all networks are /24 and starting with '10.', 
> all MAC-Addrs='00:00:IP'
> 
>        eth0  eth1    eth1  eth2     eth1  eth2
> HOST------LSR1----------LSR3-----------LSR6---------next LSR not started
>      0.30.2  1.2.1  1.2.3  3.6.3   3.6.6  6.10.6
> 
> LSR3 and LSR6 have also a tuntap interface to the host system (10.0.23/24 and 10.0.26/24)
> 
> i add a additional debug line in mpls_utils.c on LSR3 for a further 
> test, and found:
> 
> Mar  9 12:41:15 LSR-3 kernel: : push label Label GEN 10003
> Mar  9 12:41:16 LSR-3 kernel: mpls_make_dst: enter
> !! -> Mar  9 12:41:16 LSR-3 kernel: mpls_make_dst: dev_get_by_index(ifi) = 3
> Mar  9 12:41:16 LSR-3 kernel: mpls_dst_hold: enter
> Mar  9 12:41:16 LSR-3 kernel: mpls_dst_hold: new count 1
> Mar  9 12:41:16 LSR-3 kernel: mpls_dst_hold: exit
> Mar  9 12:41:16 LSR-3 kernel: mpls_make_dst: exit(a3a5c8a0)
> 
> and a small test program found:
> 
> LSR-3:/var/log$ cat /proc/net/mpls_out
> 0x00000002 0/0/0 2 PUSH(gen 10003) SET(eth1,10.3.6.6)
> 
> LSR-3:/var/log$ /tmp/getifi eth1
> index: 3  name: eth1
> 
> so, the parameter ifi to
> static struct mpls_dst *mpls_make_dst(unsigned int ifi,struct sockaddr *nh,
> 
> from
> 
>          /* NOTE: mpls_make_dst holds the dev,
>           * so release the hold from dev lookup*/
>          md = mpls_make_dst(mir->mir_instruction[i].mir_data.set.mni_if,
>            &mir->mir_instruction[i].mir_data.set.mni_addr,moi);
>          dev_put(dev);
> 
> in mpls_utils.c is wrong...
> 
> why?
> 
> in the trace-all dump from a test before i found on LSR3:
> 
>  > ldp_label_mapping_with_xc: exit
>  > OUT: Processing: 0a060a00/24 via eth2/0a030606
>  > EXIT: ldp_label_mapping_initial_callback
> 
> which is a correct setting:
> 
>    10.6.10.0/24 via eth2 of LSR3 to 10.3.6.6 (this is eth1 of LSR6)
> 
> but mpls_out says eth1 of LSR3 ...? 
> who is modifying the interface between mplsd and the kenel?
> 
> 
> thx in advance,
> markus
> 
> btw, is there a /proc interface to the 'dev_get_by_index(ifi)' function?
> 
> #include <unistd.h>
> #include <stdio.h>
> #include <fcntl.h>
> #include <errno.h>
> #include <string.h>
> #include <sys/types.h>
> #include <sys/ioctl.h>
> #include <sys/stat.h>
> #include <sys/socket.h>
> #include <linux/if_arp.h>
> #include <arpa/inet.h>
> #include <netinet/in.h>
> #include "support.h"
> /* get_ifindex - find out ifindex of interface
>   * ifname: name of the interface
>   *
>   * returns ifindex, -1 on error
>   */
> int get_ifindex(char *ifname)
> {
>          int probe_fd;
>          struct ifreq ifr;
>          memset(&ifr, 0, sizeof(ifr));
>          strncpy((char *)&ifr.ifr_name, ifname, IFNAMSIZ-1);
>          probe_fd = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);
>          if (!probe_fd) {
>                  perror("socket");
>                  return -1;
>          }
>          /* according to netdevice(7) */
>          if (ioctl(probe_fd, SIOCGIFINDEX, &ifr) < 0) {
>                  fprintf(stderr, "unknown interface %s\n", ifname);
>                  close(probe_fd);
>                  return -1;
>          }
>          close(probe_fd);
>          return ifr.ifr_ifindex;
> }
> int main(argc,argv)
> int argc;
> char *argv[];
> {
> int i;
>   i=get_ifindex(argv[1]);
>   printf("index: %d  name: %s\n", i, argv[1]);
>   return 0;
> }
> 
> 
> 
> Markus Hennig wrote:
> > Markus Hennig wrote:
> >  > James R. Leu wrote:
> >  >  > Make sure there is not ECMP (equal cost multipath) in your network.
> >  >
> >  > there are not multipaths, here is my very simple testsetup:
> >  >
> >  > all networks are /24 and starting with '10.', all MAC-addrs=00:00:IP
> >  >
> >  >
> >  >
> >  > HOST-----lsr1-------------lsr3----------------lsr6---------next LSR not started
> >  >     0.30.2  1.2.1     1.2.3  3.6.3        3.6.6  6.10.6
> >  >
> >  >  > Other then that, try turning on all mplsd tracing (mpls ldp trace all)
> >  >  > and send it to the list.
> >  >
> >  > really 'trace all', is there no quieter option ?
> >  >
> > 
> > ok, back with the trace output:
> > 
> > 
> > LSR1
> > ----
> > 
> > LER-1:~$ cat /proc/net/mpls_in
> > 0x02710001 0/0/0 gen 10000 0 1 POP PEEK
> > 0x02711001 0/0/0 gen 10001 0 1 POP PEEK
> > 0x02712001 0/0/0 gen 10002 0 1 POP PEEK
> > 0x02713001 0/0/0 gen 10003 0 1 POP PEEK
> > 0x02714001 0/0/0 gen 10004 0 1 POP PEEK
> > 0x02715001 0/0/0 gen 10005 0 1 POP PEEK
> > 0x02716001 0/0/0 gen 10006 0 1 POP PEEK
> > 0x02717001 0/0/0 gen 10007 0 1 POP PEEK
> > 0x02718001 0/0/0 gen 10008 0 1 POP FWD(0x00000002)
> > 0x02719001 0/0/0 gen 10009 0 1 POP FWD(0x00000003)
> > 0x0271a001 0/0/0 gen 10010 0 1 POP FWD(0x00000003)
> > 0x0271b001 0/0/0 gen 10011 0 1 POP FWD(0x00000003)
> > 0x0271c001 0/0/0 gen 10012 0 1 POP PEEK
> > 0x0271d001 0/0/0 gen 10013 0 1 POP PEEK
> > 0x0271e001 0/0/0 gen 10014 0 1 POP PEEK
> > 0x0271f001 0/0/0 gen 10015 0 1 POP PEEK
> > 0x02720001 0/0/0 gen 10016 0 1 POP FWD(0x00000002)
> > 0x02721001 0/0/0 gen 10017 0 1 POP PEEK
> > 0x02722001 0/0/0 gen 10018 0 1 POP PEEK
> > 0x02723001 0/0/0 gen 10019 0 1 POP PEEK
> > 0x02724001 0/0/0 gen 10020 0 1 POP PEEK
> > 0x02725001 0/0/0 gen 10021 0 1 POP FWD(0x00000002)
> > 
> > LER-1:~$ cat /proc/net/mpls_out
> > 0x00000002 112/7408/0 7 PUSH(gen 10007) SET(eth2,10.1.2.3)
> > 0x00000003 0/0/0 5 PUSH(gen 10017) SET(eth2,10.1.2.3)
> > 
> > LER-1:~$ ifconfig eth1
> > eth1      Link encap:Ethernet  HWaddr FE:FD:00:00:00:00
> >            inet addr:10.0.30.2  Bcast:10.0.30.255  Mask:255.255.255.0
> >            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >            TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
> >            collisions:0 txqueuelen:100
> >            RX bytes:0 (0.0 b)  TX bytes:3626 (3.5 Kb)
> >            Interrupt:5
> > 
> > 
> > LER-1:~$ ifconfig eth2
> > eth2      Link encap:Ethernet  HWaddr 00:00:0A:01:02:01
> >            inet addr:10.1.2.1  Bcast:10.1.2.255  Mask:255.255.255.0
> >            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >            RX packets:954 errors:0 dropped:0 overruns:0 frame:0
> >            TX packets:464 errors:0 dropped:0 overruns:0 carrier:0
> >            collisions:0 txqueuelen:100
> >            RX bytes:66452 (64.8 Kb)  TX bytes:38390 (37.4 Kb)
> >            Interrupt:5
> > 
> > -> looks ok
> > 
> > ldp_if_new:
> > 2003/03/09 10:16:10 MPLS: MPLSd (0.93a) starts
> > 2003/03/09 10:16:10 MPLS: interface add lo index 1 flags 73 metric 1 mtu
> > 16436
> > 2003/03/09 10:16:10 MPLS: address add 127.0.0.1 to interface lo
> > 2003/03/09 10:16:10 MPLS: interface add dummy0 index 2 flags 195 metric 1
> > mtu 1500
> > 2003/03/09 10:16:10 MPLS: address add 10.0.21.2 to interface dummy0
> > 2003/03/09 10:16:10 MPLS: interface add eth2 index 3 flags 4163 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:10 MPLS: address add 10.1.2.1 to interface eth2
> > 2003/03/09 10:16:10 MPLS: interface add eth0 index 4 flags 4675 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:10 MPLS: address add 10.0.21.2 to interface eth0
> > 2003/03/09 10:16:10 MPLS: interface add eth1 index 5 flags 4163 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:10 MPLS: address add 10.0.30.2 to interface eth1
> > 2003/03/09 10:16:10 MPLS: router-id change 10.0.21.2
> > 2003/03/09 10:16:10 MPLS: router-id update 10.0.21.2
> > 2003/03/09 10:16:10 MPLS: router add 10.0.21.0/24
> > 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> > 2003/03/09 10:16:10 MPLS:       ifindex 4
> > 2003/03/09 10:16:10 MPLS: router add 10.0.21.2/32
> > 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> > 2003/03/09 10:16:10 MPLS:       ifindex 2
> > 2003/03/09 10:16:10 MPLS: router add 10.0.30.0/24
> > 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> > 2003/03/09 10:16:10 MPLS:       ifindex 5
> > 2003/03/09 10:16:10 MPLS: router add 10.1.2.0/24
> > 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> > 2003/03/09 10:16:10 MPLS:       ifindex 3
> > 2003/03/09 10:16:10 MPLS: router add 10.3.6.0/24
> > 2003/03/09 10:16:10 MPLS:       nexthop 10.1.2.3
> > 2003/03/09 10:16:10 MPLS:       ifindex 3
> > 2003/03/09 10:16:10 MPLS: router add 10.6.10.0/24
> > 2003/03/09 10:16:10 MPLS:       nexthop 10.1.2.3
> > 2003/03/09 10:16:10 MPLS:       ifindex 3
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > _ldp_global_add_outlabel
> > ldp_label_mapping_with_xc: enter
> > mpls_mpls_xconnect_add: 10008 <-> 10007
> > ldp_label_mapping_with_xc: exit
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > _ldp_global_add_outlabel
> > ldp_label_mapping_with_xc: enter
> > mpls_mpls_xconnect_add: 10009 <-> 10017
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > mpls_mpls_xconnect_add: 10010 <-> 10017
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > mpls_mpls_xconnect_add: 10011 <-> 10017
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > ldp_label_mapping_with_xc: exit
> > ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> > ldp_get_next_hop_session_for_fec: 0x80cb598
> > ldp_label_mapping_with_xc: enter
> > mpls_mpls_xconnect_add: 10016 <-> 10007
> > ldp_label_mapping_with_xc: exit
> > ldp_label_mapping_with_xc: enter
> > 
> > 
> > LSR-3
> > -----
> > 
> > LSR-3:~$ cat /proc/net/mpls_in
> > 0x02710001 0/0/0 gen 10000 0 1 POP PEEK
> > 0x02711001 0/0/0 gen 10001 0 1 POP PEEK
> > 0x02712001 0/0/0 gen 10002 0 1 POP PEEK
> > 0x02713001 0/0/0 gen 10003 0 1 POP PEEK
> > 0x02714001 0/0/0 gen 10004 0 1 POP PEEK
> > 0x02715001 0/0/0 gen 10005 0 1 POP PEEK
> > 0x02716001 0/0/0 gen 10006 0 1 POP PEEK
> > 0x02717001 145/10028/0 gen 10007 0 1 POP PEEK
> > 0x02718001 0/0/0 gen 10008 0 1 POP PEEK
> > 0x02719001 0/0/0 gen 10009 0 1 POP PEEK
> > 0x0271a001 0/0/0 gen 10010 0 1 POP PEEK
> > 0x0271b001 0/0/0 gen 10011 0 1 POP PEEK
> > 0x0271c001 0/0/0 gen 10012 0 1 POP PEEK
> > 0x0271d001 0/0/0 gen 10013 0 1 POP PEEK
> > 0x0271e001 0/0/0 gen 10014 0 1 POP PEEK
> > 0x0271f001 0/0/0 gen 10015 0 1 POP PEEK
> > 0x02720001 0/0/0 gen 10016 0 1 POP FWD(0x00000002)
> > 0x02721001 0/0/0 gen 10017 0 1 POP FWD(0x00000002)
> > 0x02722001 0/0/0 gen 10018 0 1 POP FWD(0x00000002)
> > 
> > LSR-3:~$ cat /proc/net/mpls_out
> > 0x00000002 0/0/0 4 PUSH(gen 10007) SET(eth1,10.3.6.6)
> > 
> > LSR-3:~$ ifconfig eth1
> > eth1      Link encap:Ethernet  HWaddr 00:00:0A:01:02:03
> >            inet addr:10.1.2.3  Bcast:10.1.2.255  Mask:255.255.255.0
> >            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >            RX packets:1516 errors:0 dropped:0 overruns:0 frame:0
> >            TX packets:696 errors:0 dropped:0 overruns:0 carrier:0
> >            collisions:0 txqueuelen:100
> >            RX bytes:103654 (101.2 Kb)  TX bytes:58776 (57.3 Kb)
> >            Interrupt:5
> > 
> > LSR-3:/tmp$ ifconfig eth2
> > eth2      Link encap:Ethernet  HWaddr 00:00:0A:03:06:03
> >            inet addr:10.3.6.3  Bcast:10.3.6.255  Mask:255.255.255.0
> >            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >            RX packets:6971 errors:0 dropped:0 overruns:0 frame:0
> >            TX packets:2990 errors:0 dropped:0 overruns:0 carrier:0
> >            collisions:0 txqueuelen:100
> >            RX bytes:507953 (496.0 Kb)  TX bytes:259521 (253.4 Kb)
> >            Interrupt:5
> > 
> > 
> > -> outgoing interface wrong, IP correct
> > 
> > ldp_if_new:
> > ENTER: ldp_cfg_if_set
> > EXIT: ldp_cfg_if_set
> > ENTER: ldp_cfg_entity_set
> > PRT: ldp_cfg_entity_set: entity not ready
> > 
> > EXIT: ldp_cfg_entity_set
> > ENTER: ldp_cfg_entity_get
> > EXIT: ldp_cfg_entity_get
> > ENTER: ldp_cfg_if_get
> > EXIT: ldp_cfg_if_get
> > ldp_if_new:
> > ENTER: ldp_cfg_if_set
> > EXIT: ldp_cfg_if_set
> > ENTER: ldp_cfg_entity_set
> > PRT: ldp_cfg_entity_set: entity not ready
> > 
> > EXIT: ldp_cfg_entity_set
> > ENTER: ldp_cfg_entity_get
> > EXIT: ldp_cfg_entity_get
> > ENTER: ldp_cfg_if_get
> > EXIT: ldp_cfg_if_get
> > 2003/03/09 10:16:20 MPLS: MPLSd (0.93a) starts
> > 2003/03/09 10:16:20 MPLS: interface add lo index 1 flags 73 metric 1 mtu
> > 16436
> > 2003/03/09 10:16:20 MPLS: address add 127.0.0.1 to interface lo
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:20 MPLS: interface add dummy0 index 2 flags 195 metric 1
> > mtu 1500
> > 2003/03/09 10:16:20 MPLS: address add 10.0.23.2 to interface dummy0
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:20 MPLS: interface add eth1 index 3 flags 4163 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:20 MPLS: address add 10.1.2.3 to interface eth1
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:20 MPLS: interface add eth2 index 4 flags 4163 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:20 MPLS: address add 10.3.6.3 to interface eth2
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:20 MPLS: interface add eth0 index 5 flags 4675 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:20 MPLS: address add 10.0.23.2 to interface eth0
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:20 MPLS: router-id change 10.0.23.2
> > 2003/03/09 10:16:20 MPLS: router-id update 10.0.23.2
> > ENTER: ldp_cfg_global_set
> > ENTER: ldp_global_shutdown
> > ENTER: ldp_entity_shutdown
> > ENTER: ldp_if_shutdown
> > EXIT: ldp_if_shutdown
> > EXIT: ldp_entity_shutdown
> > ENTER: ldp_entity_shutdown
> > ENTER: ldp_if_shutdown
> > EXIT: ldp_if_shutdown
> > EXIT: ldp_entity_shutdown
> > EXIT: ldp_global_shutdown
> > EXIT: ldp_cfg_global_set
> > ENTER: ldp_cfg_global_set
> > EXIT: ldp_cfg_global_set
> > ENTER: ldp_cfg_global_set
> > ENTER: ldp_global_startup
> > ENTER: ldp_entity_startup
> > ENTER: ldp_if_startup
> > OUT: Hello Send: entity(1)
> > OUT: LPD Header : protocolVersion = 1
> > OUT:    pduLength = 30
> > OUT:    lsrAddress = a001702
> > OUT:    labelSpace = 0
> > OUT: HELLO MSG ***START***:
> > OUT:    baseMsg : uBit = 0
> > OUT:              msgType = 100
> > OUT:              msgLength = 20
> > OUT:              msgId = 1
> > OUT:     chpTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 400
> > OUT:              length = 4
> > OUT:     chpTlv data: holdTime = 15
> > OUT:     chpTlv Flags:  target = 0
> > OUT:                    request = 0
> > OUT:                    res = 0
> > OUT:    Hello msg does not have TrAdr TLV
> > OUT:     csnTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 402
> > OUT:              length = 4
> > OUT:     csnTlv data: value = 6
> > OUT: HELLO MSG ***END***:
> > 
> > ...
> > 
> > ENTER: ldp_label_mapping_send
> > ENTER: lsr_cfg_insegment_set
> > EXIT: lsr_cfg_insegment_set
> > OUT: In Label Added
> > OUT: LPD Header : protocolVersion = 1
> > OUT:    pduLength = 33
> > OUT:    lsrAddress = a001702
> > OUT:    labelSpace = 0
> > OUT: LABEL MAPPING MSG ***START***:
> > OUT:    baseMsg : uBit = 0
> > OUT:              msgType = 400
> > OUT:              msgLength = 23
> > OUT:              msgId = 22
> > OUT:     fecTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 100
> > OUT:              length = 7
> > OUT:            fecTlv->numberFecElements = 1
> > OUT:            elem 0 type is 2
> > OUT:            Fec Element : type = 2, addFam = 1, preLen = 24, address =
> > a030600
> > OUT:
> > OUT:    fecTlv.wcElemExists = 0
> > OUT:     genLblTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 200
> > OUT:              length = 4
> > OUT:     genLbl data: label = 10007
> > OUT:    Label mapping msg does not have atm label Tlv
> > OUT:    Label mapping msg does not have fr label Tlv
> > OUT:    Label mapping msg does not have hop count Tlv
> > OUT:    Label mapping msg does not have path vector Tlv
> > OUT:    Label mapping msg does not have label messageId Tlv
> > OUT:    Label mapping msg does not have LSPID Tlv
> > OUT:    Label mapping msg does not have traffic Tlv
> > OUT: LABEL MAPPING MSG ***END***:
> > OUT: Label Mapping Sent to 0a001502:0 for 0a030600/24
> > EXIT: ldp_label_mapping_send
> > ldp_label_mapping_with_xc: exit
> > OUT: Processing: 0a060a00/24 via eth2/0a030606
> > EXIT: ldp_label_mapping_initial_callback
> > ENTER: ldp_event
> > ENTER: ldp_buf_process
> > 
> > 
> > mode trace output necessary ?
> > 
> > 
> > 
> > 
> > 
> > LSR-6
> > -----
> > 
> > LSR-6:/tmp$ cat /proc/net/mpls_in
> > 0x02710001 0/0/0 gen 10000 0 1 POP PEEK
> > 0x02711001 0/0/0 gen 10001 0 1 POP PEEK
> > 0x02712001 0/0/0 gen 10002 0 1 POP PEEK
> > 0x02713001 0/0/0 gen 10003 0 1 POP PEEK
> > 0x02714001 0/0/0 gen 10004 0 1 POP PEEK
> > 0x02715001 0/0/0 gen 10005 0 1 POP PEEK
> > 0x02716001 0/0/0 gen 10006 0 1 POP PEEK
> > 0x02717001 0/0/0 gen 10007 0 1 POP PEEK
> > 0x02718001 0/0/0 gen 10008 0 1 POP FWD(0x00000002)
> > 0x02719001 0/0/0 gen 10009 0 1 POP FWD(0x00000002)
> > 0x0271a001 0/0/0 gen 10010 0 1 POP FWD(0x00000002)
> > 0x0271b001 0/0/0 gen 10011 0 1 POP PEEK
> > 0x0271c001 0/0/0 gen 10012 0 1 POP PEEK
> > 0x0271d001 0/0/0 gen 10013 0 1 POP PEEK
> > 0x0271e001 0/0/0 gen 10014 0 1 POP PEEK
> > 0x0271f001 0/0/0 gen 10015 0 1 POP PEEK
> > 0x02720001 0/0/0 gen 10016 0 1 POP PEEK
> > 0x02721001 0/0/0 gen 10017 0 1 POP PEEK
> > 0x02722001 0/0/0 gen 10018 0 1 POP PEEK
> > 
> > LSR-6:/tmp$ cat /proc/net/mpls_out
> > 0x00000002 0/0/0 4 PUSH(gen 10014) SET(eth2,10.3.6.3)
> > 
> > LSR-6:/tmp$ ifconfig eth1
> > eth1      Link encap:Ethernet  HWaddr 00:00:0A:03:06:06
> >            inet addr:10.3.6.6  Bcast:10.3.6.255  Mask:255.255.255.0
> >            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >            RX packets:836 errors:0 dropped:0 overruns:0 frame:0
> >            TX packets:401 errors:0 dropped:0 overruns:0 carrier:0
> >            collisions:0 txqueuelen:100
> >            RX bytes:58211 (56.8 Kb)  TX bytes:33901 (33.1 Kb)
> >            Interrupt:5
> > 
> > eth2      Link encap:Ethernet  HWaddr 00:00:0A:06:0A:06
> >            inet addr:10.6.10.6  Bcast:10.6.10.255  Mask:255.255.255.0
> >            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >            RX packets:601 errors:0 dropped:0 overruns:0 frame:0
> >            TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
> >            collisions:0 txqueuelen:100
> >            RX bytes:41900 (40.9 Kb)  TX bytes:11922 (11.6 Kb)
> >            Interrupt:5
> > 
> > -> ougoing interface wrong, IP correct
> > 
> > ldp_if_new:
> > ENTER: ldp_cfg_if_set
> > EXIT: ldp_cfg_if_set
> > ENTER: ldp_cfg_entity_set
> > PRT: ldp_cfg_entity_set: entity not ready
> > 
> > EXIT: ldp_cfg_entity_set
> > ENTER: ldp_cfg_entity_get
> > EXIT: ldp_cfg_entity_get
> > ENTER: ldp_cfg_if_get
> > EXIT: ldp_cfg_if_get
> > ldp_if_new:
> > ENTER: ldp_cfg_if_set
> > EXIT: ldp_cfg_if_set
> > ENTER: ldp_cfg_entity_set
> > PRT: ldp_cfg_entity_set: entity not ready
> > 
> > EXIT: ldp_cfg_entity_set
> > ENTER: ldp_cfg_entity_get
> > EXIT: ldp_cfg_entity_get
> > ENTER: ldp_cfg_if_get
> > EXIT: ldp_cfg_if_get
> > 2003/03/09 10:16:28 MPLS: MPLSd (0.93a) starts
> > 2003/03/09 10:16:28 MPLS: interface add lo index 1 flags 73 metric 1 mtu
> > 16436
> > 2003/03/09 10:16:28 MPLS: address add 127.0.0.1 to interface lo
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:28 MPLS: interface add dummy0 index 2 flags 195 metric 1
> > mtu 1500
> > 2003/03/09 10:16:28 MPLS: address add 10.0.26.2 to interface dummy0
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:28 MPLS: interface add eth1 index 3 flags 4163 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:28 MPLS: address add 10.3.6.6 to interface eth1
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:28 MPLS: interface add eth2 index 4 flags 4163 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:28 MPLS: address add 10.6.10.6 to interface eth2
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:28 MPLS: interface add eth0 index 5 flags 4675 metric 1 mtu
> > 1500
> > 2003/03/09 10:16:28 MPLS: address add 10.0.26.2 to interface eth0
> > ENTER: _ldp_global_ifmgr_callback
> > EXIT: _ldp_global_ifmgr_callback
> > 2003/03/09 10:16:28 MPLS: router-id change 10.0.26.2
> > 2003/03/09 10:16:28 MPLS: router-id update 10.0.26.2
> > ENTER: ldp_cfg_global_set
> > ENTER: ldp_global_shutdown
> > ENTER: ldp_entity_shutdown
> > ENTER: ldp_if_shutdown
> > EXIT: ldp_if_shutdown
> > EXIT: ldp_entity_shutdown
> > ENTER: ldp_entity_shutdown
> > ENTER: ldp_if_shutdown
> > EXIT: ldp_if_shutdown
> > EXIT: ldp_entity_shutdown
> > EXIT: ldp_global_shutdown
> > EXIT: ldp_cfg_global_set
> > ENTER: ldp_cfg_global_set
> > EXIT: ldp_cfg_global_set
> > ENTER: ldp_cfg_global_set
> > ENTER: ldp_global_startup
> > ENTER: ldp_entity_startup
> > ENTER: ldp_if_startup
> > OUT: Hello Send: entity(1)
> > OUT: LPD Header : protocolVersion = 1
> > OUT:    pduLength = 30
> > OUT:    lsrAddress = a001a02
> > OUT:    labelSpace = 0
> > OUT: HELLO MSG ***START***:
> > OUT:    baseMsg : uBit = 0
> > OUT:              msgType = 100
> > OUT:              msgLength = 20
> > OUT:              msgId = 1
> > OUT:     chpTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 400
> > OUT:              length = 4
> > OUT:     chpTlv data: holdTime = 15
> > OUT:     chpTlv Flags:  target = 0
> > OUT:                    request = 0
> > OUT:                    res = 0
> > OUT:    Hello msg does not have TrAdr TLV
> > OUT:     csnTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 402
> > OUT:              length = 4
> > OUT:     csnTlv data: value = 6
> > OUT: HELLO MSG ***END***:
> > 
> > ...
> > 
> > ENTER: Prepare_Label_Mapping_Attributes
> > EXIT: Prepare_Label_Mapping_Attributes
> > ENTER: ldp_label_mapping_send
> > ENTER: lsr_cfg_insegment_set
> > EXIT: lsr_cfg_insegment_set
> > OUT: In Label Added
> > OUT: LPD Header : protocolVersion = 1
> > OUT:    pduLength = 33
> > OUT:    lsrAddress = a001a02
> > OUT:    labelSpace = 0
> > OUT: LABEL MAPPING MSG ***START***:
> > OUT:    baseMsg : uBit = 0
> > OUT:              msgType = 400
> > OUT:              msgLength = 23
> > OUT:              msgId = 41
> > OUT:     fecTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 100
> > OUT:              length = 7
> > OUT:            fecTlv->numberFecElements = 1
> > OUT:            elem 0 type is 2
> > OUT:            Fec Element : type = 2, addFam = 1, preLen = 24, address =
> > a060a00
> > OUT:
> > OUT:    fecTlv.wcElemExists = 0
> > OUT:     genLblTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 200
> > OUT:              length = 4
> > OUT:     genLbl data: label = 10014
> > OUT:    Label mapping msg does not have atm label Tlv
> > OUT:    Label mapping msg does not have fr label Tlv
> > OUT:    Label mapping msg does not have hop count Tlv
> > OUT:    Label mapping msg does not have path vector Tlv
> > OUT:    Label mapping msg does not have label messageId Tlv
> > OUT:    Label mapping msg does not have LSPID Tlv
> > OUT:    Label mapping msg does not have traffic Tlv
> > OUT: LABEL MAPPING MSG ***END***:
> > OUT: Label Mapping Sent to 0a001502:0 for 0a060a00/24
> > EXIT: ldp_label_mapping_send
> > ldp_label_mapping_with_xc: exit
> > EXIT: ldp_label_mapping_initial_callback
> > ENTER: ldp_label_mapping_initial_callback
> > OUT: Initial Label Mapping fired: session(4)
> > OUT: Processing: 0a001a00/24 via (not an LDP interface)
> > 
> > ldp_label_mapping_with_xc: enter
> > ENTER: Prepare_Label_Mapping_Attributes
> > EXIT: Prepare_Label_Mapping_Attributes
> > ENTER: ldp_label_mapping_send
> > ENTER: lsr_cfg_insegment_set
> > EXIT: lsr_cfg_insegment_set
> > OUT: In Label Added
> > OUT: LPD Header : protocolVersion = 1
> > OUT:    pduLength = 33
> > OUT:    lsrAddress = a001a02
> > OUT:    labelSpace = 0
> > OUT: LABEL MAPPING MSG ***START***:
> > OUT:    baseMsg : uBit = 0
> > OUT:              msgType = 400
> > OUT:              msgLength = 23
> > OUT:              msgId = 42
> > OUT:     fecTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 100
> > OUT:              length = 7
> > OUT:            fecTlv->numberFecElements = 1
> > OUT:            elem 0 type is 2
> > OUT:            Fec Element : type = 2, addFam = 1, preLen = 24, address = a001a00
> > OUT:
> > OUT:    fecTlv.wcElemExists = 0
> > OUT:     genLblTlv:
> > OUT:     Tlv:
> > OUT:     BaseTlv: uBit = 0
> > OUT:              fBit = 0
> > OUT:              type = 200
> > OUT:              length = 4
> > OUT:     genLbl data: label = 10015
> > OUT:    Label mapping msg does not have atm label Tlv
> > OUT:    Label mapping msg does not have fr label Tlv
> > OUT:    Label mapping msg does not have hop count Tlv
> > OUT:    Label mapping msg does not have path vector Tlv
> > 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open! 
> Get cracking and register here for some mind boggling fun and 
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Mpls tunnel / Zebra / Ospf

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

Are you trying to create a 'RSVP-TE tunnel' which shows up as a
real interface?  Or are you just try to create an LSP and bind a route
to it?

Since you previous messages were using RSVP I'm assuming the aforementioned.
In which case you should head over to the maling list for RSVP-TE and they
can help you.  Start by looking at:

http://dsmpls.atlantis.rug.ac.be/

If you are looking for 'OSPF short cuts' they haven't been implemented.
So far the only protocol related interaction is that routes that area learned
by other protocols can be bound to a LSP created by LDP.  Indirect BGP routes
can utilize routes which LDP has bound to a LSP as well.

On Fri, Mar 14, 2003 at 05:34:32PM -0000, Nicolas Tempestini wrote:
> Hello,
> 
> I have set up a little OSPF network with zebra between some linux boxes and it is worling fine.
> 
> I also managed to set up MPLS lsp between those machines.
> 
> my config is :
> 
> LInux 2.4.20
> iptables 1.27a
> zebra 0.93a patched for mpls
> 
> Lets say there is only 2 machines running the same config (simple test ...) : machine 1 and machine 2
> 
> 
> Now i'd like to create a mpls tunnel on a machine 1 with an ip address given to it , to map the outgoing traffic from for ex. eth0 to machine 2 on it and to see how ospf understand this tunnel ...
> 
> What can i do ...
> 
> i saw we can use mplsadm to create a tunnel but there seems to be errors ...
> 
> Thx
> 
> Nicolas
> 
> 
> 

-- 
James R. Leu

[mpls-linux-general] /proc/net/mpls_out bug with Zebra and LDP (mplsd)

[Markus H. <mh...@as...>]

Hi all,

is there someone how can help me with the wrong interface in =
/proc/net/mpls_out?

This is my small testseup (UML) - everything latest CVS release,
all networks are /24 and starting with '10.',=20
all MAC-Addrs=3D'00:00:IP'

       eth0  eth1    eth1  eth2     eth1  eth2
HOST------LSR1----------LSR3-----------LSR6---------next LSR not started
     0.30.2  1.2.1  1.2.3  3.6.3   3.6.6  6.10.6

LSR3 and LSR6 have also a tuntap interface to the host system =
(10.0.23/24 and 10.0.26/24)

i add a additional debug line in mpls_utils.c on LSR3 for a further=20
test, and found:

Mar  9 12:41:15 LSR-3 kernel: : push label Label GEN 10003
Mar  9 12:41:16 LSR-3 kernel: mpls_make_dst: enter
!! -> Mar  9 12:41:16 LSR-3 kernel: mpls_make_dst: dev_get_by_index(ifi) =
=3D 3
Mar  9 12:41:16 LSR-3 kernel: mpls_dst_hold: enter
Mar  9 12:41:16 LSR-3 kernel: mpls_dst_hold: new count 1
Mar  9 12:41:16 LSR-3 kernel: mpls_dst_hold: exit
Mar  9 12:41:16 LSR-3 kernel: mpls_make_dst: exit(a3a5c8a0)

and a small test program found:

LSR-3:/var/log$ cat /proc/net/mpls_out
0x00000002 0/0/0 2 PUSH(gen 10003) SET(eth1,10.3.6.6)

LSR-3:/var/log$ /tmp/getifi eth1
index: 3  name: eth1

so, the parameter ifi to
static struct mpls_dst *mpls_make_dst(unsigned int ifi,struct sockaddr =
*nh,

from

         /* NOTE: mpls_make_dst holds the dev,
          * so release the hold from dev lookup*/
         md =3D =
mpls_make_dst(mir->mir_instruction[i].mir_data.set.mni_if,
           &mir->mir_instruction[i].mir_data.set.mni_addr,moi);
         dev_put(dev);

in mpls_utils.c is wrong...

why?

in the trace-all dump from a test before i found on LSR3:

 > ldp_label_mapping_with_xc: exit
 > OUT: Processing: 0a060a00/24 via eth2/0a030606
 > EXIT: ldp_label_mapping_initial_callback

which is a correct setting:

   10.6.10.0/24 via eth2 of LSR3 to 10.3.6.6 (this is eth1 of LSR6)

but mpls_out says eth1 of LSR3 ...?=20
who is modifying the interface between mplsd and the kenel?


thx in advance,
markus

btw, is there a /proc interface to the 'dev_get_by_index(ifi)' function?

#include <unistd.h>
#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
#include <string.h>
#include <sys/types.h>
#include <sys/ioctl.h>
#include <sys/stat.h>
#include <sys/socket.h>
#include <linux/if_arp.h>
#include <arpa/inet.h>
#include <netinet/in.h>
#include "support.h"
/* get_ifindex - find out ifindex of interface
  * ifname: name of the interface
  *
  * returns ifindex, -1 on error
  */
int get_ifindex(char *ifname)
{
         int probe_fd;
         struct ifreq ifr;
         memset(&ifr, 0, sizeof(ifr));
         strncpy((char *)&ifr.ifr_name, ifname, IFNAMSIZ-1);
         probe_fd =3D socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);
         if (!probe_fd) {
                 perror("socket");
                 return -1;
         }
         /* according to netdevice(7) */
         if (ioctl(probe_fd, SIOCGIFINDEX, &ifr) < 0) {
                 fprintf(stderr, "unknown interface %s\n", ifname);
                 close(probe_fd);
                 return -1;
         }
         close(probe_fd);
         return ifr.ifr_ifindex;
}
int main(argc,argv)
int argc;
char *argv[];
{
int i;
  i=3Dget_ifindex(argv[1]);
  printf("index: %d  name: %s\n", i, argv[1]);
  return 0;
}



Markus Hennig wrote:
> Markus Hennig wrote:
>  > James R. Leu wrote:
>  >  > Make sure there is not ECMP (equal cost multipath) in your =
network.
>  >
>  > there are not multipaths, here is my very simple testsetup:
>  >
>  > all networks are /24 and starting with '10.', all =
MAC-addrs=3D00:00:IP
>  >
>  >
>  >
>  > HOST-----lsr1-------------lsr3----------------lsr6---------next LSR =
not started
>  >     0.30.2  1.2.1     1.2.3  3.6.3        3.6.6  6.10.6
>  >
>  >  > Other then that, try turning on all mplsd tracing (mpls ldp =
trace all)
>  >  > and send it to the list.
>  >
>  > really 'trace all', is there no quieter option ?
>  >
>=20
> ok, back with the trace output:
>=20
>=20
> LSR1
> ----
>=20
> LER-1:~$ cat /proc/net/mpls_in
> 0x02710001 0/0/0 gen 10000 0 1 POP PEEK
> 0x02711001 0/0/0 gen 10001 0 1 POP PEEK
> 0x02712001 0/0/0 gen 10002 0 1 POP PEEK
> 0x02713001 0/0/0 gen 10003 0 1 POP PEEK
> 0x02714001 0/0/0 gen 10004 0 1 POP PEEK
> 0x02715001 0/0/0 gen 10005 0 1 POP PEEK
> 0x02716001 0/0/0 gen 10006 0 1 POP PEEK
> 0x02717001 0/0/0 gen 10007 0 1 POP PEEK
> 0x02718001 0/0/0 gen 10008 0 1 POP FWD(0x00000002)
> 0x02719001 0/0/0 gen 10009 0 1 POP FWD(0x00000003)
> 0x0271a001 0/0/0 gen 10010 0 1 POP FWD(0x00000003)
> 0x0271b001 0/0/0 gen 10011 0 1 POP FWD(0x00000003)
> 0x0271c001 0/0/0 gen 10012 0 1 POP PEEK
> 0x0271d001 0/0/0 gen 10013 0 1 POP PEEK
> 0x0271e001 0/0/0 gen 10014 0 1 POP PEEK
> 0x0271f001 0/0/0 gen 10015 0 1 POP PEEK
> 0x02720001 0/0/0 gen 10016 0 1 POP FWD(0x00000002)
> 0x02721001 0/0/0 gen 10017 0 1 POP PEEK
> 0x02722001 0/0/0 gen 10018 0 1 POP PEEK
> 0x02723001 0/0/0 gen 10019 0 1 POP PEEK
> 0x02724001 0/0/0 gen 10020 0 1 POP PEEK
> 0x02725001 0/0/0 gen 10021 0 1 POP FWD(0x00000002)
>=20
> LER-1:~$ cat /proc/net/mpls_out
> 0x00000002 112/7408/0 7 PUSH(gen 10007) SET(eth2,10.1.2.3)
> 0x00000003 0/0/0 5 PUSH(gen 10017) SET(eth2,10.1.2.3)
>=20
> LER-1:~$ ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr FE:FD:00:00:00:00
>            inet addr:10.0.30.2  Bcast:10.0.30.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            RX bytes:0 (0.0 b)  TX bytes:3626 (3.5 Kb)
>            Interrupt:5
>=20
>=20
> LER-1:~$ ifconfig eth2
> eth2      Link encap:Ethernet  HWaddr 00:00:0A:01:02:01
>            inet addr:10.1.2.1  Bcast:10.1.2.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:954 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:464 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            RX bytes:66452 (64.8 Kb)  TX bytes:38390 (37.4 Kb)
>            Interrupt:5
>=20
> -> looks ok
>=20
> ldp_if_new:
> 2003/03/09 10:16:10 MPLS: MPLSd (0.93a) starts
> 2003/03/09 10:16:10 MPLS: interface add lo index 1 flags 73 metric 1 =
mtu
> 16436
> 2003/03/09 10:16:10 MPLS: address add 127.0.0.1 to interface lo
> 2003/03/09 10:16:10 MPLS: interface add dummy0 index 2 flags 195 =
metric 1
> mtu 1500
> 2003/03/09 10:16:10 MPLS: address add 10.0.21.2 to interface dummy0
> 2003/03/09 10:16:10 MPLS: interface add eth2 index 3 flags 4163 metric =
1 mtu
> 1500
> 2003/03/09 10:16:10 MPLS: address add 10.1.2.1 to interface eth2
> 2003/03/09 10:16:10 MPLS: interface add eth0 index 4 flags 4675 metric =
1 mtu
> 1500
> 2003/03/09 10:16:10 MPLS: address add 10.0.21.2 to interface eth0
> 2003/03/09 10:16:10 MPLS: interface add eth1 index 5 flags 4163 metric =
1 mtu
> 1500
> 2003/03/09 10:16:10 MPLS: address add 10.0.30.2 to interface eth1
> 2003/03/09 10:16:10 MPLS: router-id change 10.0.21.2
> 2003/03/09 10:16:10 MPLS: router-id update 10.0.21.2
> 2003/03/09 10:16:10 MPLS: router add 10.0.21.0/24
> 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> 2003/03/09 10:16:10 MPLS:       ifindex 4
> 2003/03/09 10:16:10 MPLS: router add 10.0.21.2/32
> 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> 2003/03/09 10:16:10 MPLS:       ifindex 2
> 2003/03/09 10:16:10 MPLS: router add 10.0.30.0/24
> 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> 2003/03/09 10:16:10 MPLS:       ifindex 5
> 2003/03/09 10:16:10 MPLS: router add 10.1.2.0/24
> 2003/03/09 10:16:10 MPLS:       nexthop 0.0.0.0
> 2003/03/09 10:16:10 MPLS:       ifindex 3
> 2003/03/09 10:16:10 MPLS: router add 10.3.6.0/24
> 2003/03/09 10:16:10 MPLS:       nexthop 10.1.2.3
> 2003/03/09 10:16:10 MPLS:       ifindex 3
> 2003/03/09 10:16:10 MPLS: router add 10.6.10.0/24
> 2003/03/09 10:16:10 MPLS:       nexthop 10.1.2.3
> 2003/03/09 10:16:10 MPLS:       ifindex 3
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> _ldp_global_add_outlabel
> ldp_label_mapping_with_xc: enter
> mpls_mpls_xconnect_add: 10008 <-> 10007
> ldp_label_mapping_with_xc: exit
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> _ldp_global_add_outlabel
> ldp_label_mapping_with_xc: enter
> mpls_mpls_xconnect_add: 10009 <-> 10017
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> mpls_mpls_xconnect_add: 10010 <-> 10017
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> mpls_mpls_xconnect_add: 10011 <-> 10017
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
> ldp_label_mapping_with_xc: exit
> ldp_get_session_by_next_hop: NH_OTHER 0x80cb598
> ldp_get_next_hop_session_for_fec: 0x80cb598
> ldp_label_mapping_with_xc: enter
> mpls_mpls_xconnect_add: 10016 <-> 10007
> ldp_label_mapping_with_xc: exit
> ldp_label_mapping_with_xc: enter
>=20
>=20
> LSR-3
> -----
>=20
> LSR-3:~$ cat /proc/net/mpls_in
> 0x02710001 0/0/0 gen 10000 0 1 POP PEEK
> 0x02711001 0/0/0 gen 10001 0 1 POP PEEK
> 0x02712001 0/0/0 gen 10002 0 1 POP PEEK
> 0x02713001 0/0/0 gen 10003 0 1 POP PEEK
> 0x02714001 0/0/0 gen 10004 0 1 POP PEEK
> 0x02715001 0/0/0 gen 10005 0 1 POP PEEK
> 0x02716001 0/0/0 gen 10006 0 1 POP PEEK
> 0x02717001 145/10028/0 gen 10007 0 1 POP PEEK
> 0x02718001 0/0/0 gen 10008 0 1 POP PEEK
> 0x02719001 0/0/0 gen 10009 0 1 POP PEEK
> 0x0271a001 0/0/0 gen 10010 0 1 POP PEEK
> 0x0271b001 0/0/0 gen 10011 0 1 POP PEEK
> 0x0271c001 0/0/0 gen 10012 0 1 POP PEEK
> 0x0271d001 0/0/0 gen 10013 0 1 POP PEEK
> 0x0271e001 0/0/0 gen 10014 0 1 POP PEEK
> 0x0271f001 0/0/0 gen 10015 0 1 POP PEEK
> 0x02720001 0/0/0 gen 10016 0 1 POP FWD(0x00000002)
> 0x02721001 0/0/0 gen 10017 0 1 POP FWD(0x00000002)
> 0x02722001 0/0/0 gen 10018 0 1 POP FWD(0x00000002)
>=20
> LSR-3:~$ cat /proc/net/mpls_out
> 0x00000002 0/0/0 4 PUSH(gen 10007) SET(eth1,10.3.6.6)
>=20
> LSR-3:~$ ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:00:0A:01:02:03
>            inet addr:10.1.2.3  Bcast:10.1.2.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:1516 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:696 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            RX bytes:103654 (101.2 Kb)  TX bytes:58776 (57.3 Kb)
>            Interrupt:5
>=20
> LSR-3:/tmp$ ifconfig eth2
> eth2      Link encap:Ethernet  HWaddr 00:00:0A:03:06:03
>            inet addr:10.3.6.3  Bcast:10.3.6.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:6971 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:2990 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            RX bytes:507953 (496.0 Kb)  TX bytes:259521 (253.4 Kb)
>            Interrupt:5
>=20
>=20
> -> outgoing interface wrong, IP correct
>=20
> ldp_if_new:
> ENTER: ldp_cfg_if_set
> EXIT: ldp_cfg_if_set
> ENTER: ldp_cfg_entity_set
> PRT: ldp_cfg_entity_set: entity not ready
>=20
> EXIT: ldp_cfg_entity_set
> ENTER: ldp_cfg_entity_get
> EXIT: ldp_cfg_entity_get
> ENTER: ldp_cfg_if_get
> EXIT: ldp_cfg_if_get
> ldp_if_new:
> ENTER: ldp_cfg_if_set
> EXIT: ldp_cfg_if_set
> ENTER: ldp_cfg_entity_set
> PRT: ldp_cfg_entity_set: entity not ready
>=20
> EXIT: ldp_cfg_entity_set
> ENTER: ldp_cfg_entity_get
> EXIT: ldp_cfg_entity_get
> ENTER: ldp_cfg_if_get
> EXIT: ldp_cfg_if_get
> 2003/03/09 10:16:20 MPLS: MPLSd (0.93a) starts
> 2003/03/09 10:16:20 MPLS: interface add lo index 1 flags 73 metric 1 =
mtu
> 16436
> 2003/03/09 10:16:20 MPLS: address add 127.0.0.1 to interface lo
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:20 MPLS: interface add dummy0 index 2 flags 195 =
metric 1
> mtu 1500
> 2003/03/09 10:16:20 MPLS: address add 10.0.23.2 to interface dummy0
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:20 MPLS: interface add eth1 index 3 flags 4163 metric =
1 mtu
> 1500
> 2003/03/09 10:16:20 MPLS: address add 10.1.2.3 to interface eth1
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:20 MPLS: interface add eth2 index 4 flags 4163 metric =
1 mtu
> 1500
> 2003/03/09 10:16:20 MPLS: address add 10.3.6.3 to interface eth2
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:20 MPLS: interface add eth0 index 5 flags 4675 metric =
1 mtu
> 1500
> 2003/03/09 10:16:20 MPLS: address add 10.0.23.2 to interface eth0
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:20 MPLS: router-id change 10.0.23.2
> 2003/03/09 10:16:20 MPLS: router-id update 10.0.23.2
> ENTER: ldp_cfg_global_set
> ENTER: ldp_global_shutdown
> ENTER: ldp_entity_shutdown
> ENTER: ldp_if_shutdown
> EXIT: ldp_if_shutdown
> EXIT: ldp_entity_shutdown
> ENTER: ldp_entity_shutdown
> ENTER: ldp_if_shutdown
> EXIT: ldp_if_shutdown
> EXIT: ldp_entity_shutdown
> EXIT: ldp_global_shutdown
> EXIT: ldp_cfg_global_set
> ENTER: ldp_cfg_global_set
> EXIT: ldp_cfg_global_set
> ENTER: ldp_cfg_global_set
> ENTER: ldp_global_startup
> ENTER: ldp_entity_startup
> ENTER: ldp_if_startup
> OUT: Hello Send: entity(1)
> OUT: LPD Header : protocolVersion =3D 1
> OUT:    pduLength =3D 30
> OUT:    lsrAddress =3D a001702
> OUT:    labelSpace =3D 0
> OUT: HELLO MSG ***START***:
> OUT:    baseMsg : uBit =3D 0
> OUT:              msgType =3D 100
> OUT:              msgLength =3D 20
> OUT:              msgId =3D 1
> OUT:     chpTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 400
> OUT:              length =3D 4
> OUT:     chpTlv data: holdTime =3D 15
> OUT:     chpTlv Flags:  target =3D 0
> OUT:                    request =3D 0
> OUT:                    res =3D 0
> OUT:    Hello msg does not have TrAdr TLV
> OUT:     csnTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 402
> OUT:              length =3D 4
> OUT:     csnTlv data: value =3D 6
> OUT: HELLO MSG ***END***:
>=20
> ...
>=20
> ENTER: ldp_label_mapping_send
> ENTER: lsr_cfg_insegment_set
> EXIT: lsr_cfg_insegment_set
> OUT: In Label Added
> OUT: LPD Header : protocolVersion =3D 1
> OUT:    pduLength =3D 33
> OUT:    lsrAddress =3D a001702
> OUT:    labelSpace =3D 0
> OUT: LABEL MAPPING MSG ***START***:
> OUT:    baseMsg : uBit =3D 0
> OUT:              msgType =3D 400
> OUT:              msgLength =3D 23
> OUT:              msgId =3D 22
> OUT:     fecTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 100
> OUT:              length =3D 7
> OUT:            fecTlv->numberFecElements =3D 1
> OUT:            elem 0 type is 2
> OUT:            Fec Element : type =3D 2, addFam =3D 1, preLen =3D 24, =
address =3D
> a030600
> OUT:
> OUT:    fecTlv.wcElemExists =3D 0
> OUT:     genLblTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 200
> OUT:              length =3D 4
> OUT:     genLbl data: label =3D 10007
> OUT:    Label mapping msg does not have atm label Tlv
> OUT:    Label mapping msg does not have fr label Tlv
> OUT:    Label mapping msg does not have hop count Tlv
> OUT:    Label mapping msg does not have path vector Tlv
> OUT:    Label mapping msg does not have label messageId Tlv
> OUT:    Label mapping msg does not have LSPID Tlv
> OUT:    Label mapping msg does not have traffic Tlv
> OUT: LABEL MAPPING MSG ***END***:
> OUT: Label Mapping Sent to 0a001502:0 for 0a030600/24
> EXIT: ldp_label_mapping_send
> ldp_label_mapping_with_xc: exit
> OUT: Processing: 0a060a00/24 via eth2/0a030606
> EXIT: ldp_label_mapping_initial_callback
> ENTER: ldp_event
> ENTER: ldp_buf_process
>=20
>=20
> mode trace output necessary ?
>=20
>=20
>=20
>=20
>=20
> LSR-6
> -----
>=20
> LSR-6:/tmp$ cat /proc/net/mpls_in
> 0x02710001 0/0/0 gen 10000 0 1 POP PEEK
> 0x02711001 0/0/0 gen 10001 0 1 POP PEEK
> 0x02712001 0/0/0 gen 10002 0 1 POP PEEK
> 0x02713001 0/0/0 gen 10003 0 1 POP PEEK
> 0x02714001 0/0/0 gen 10004 0 1 POP PEEK
> 0x02715001 0/0/0 gen 10005 0 1 POP PEEK
> 0x02716001 0/0/0 gen 10006 0 1 POP PEEK
> 0x02717001 0/0/0 gen 10007 0 1 POP PEEK
> 0x02718001 0/0/0 gen 10008 0 1 POP FWD(0x00000002)
> 0x02719001 0/0/0 gen 10009 0 1 POP FWD(0x00000002)
> 0x0271a001 0/0/0 gen 10010 0 1 POP FWD(0x00000002)
> 0x0271b001 0/0/0 gen 10011 0 1 POP PEEK
> 0x0271c001 0/0/0 gen 10012 0 1 POP PEEK
> 0x0271d001 0/0/0 gen 10013 0 1 POP PEEK
> 0x0271e001 0/0/0 gen 10014 0 1 POP PEEK
> 0x0271f001 0/0/0 gen 10015 0 1 POP PEEK
> 0x02720001 0/0/0 gen 10016 0 1 POP PEEK
> 0x02721001 0/0/0 gen 10017 0 1 POP PEEK
> 0x02722001 0/0/0 gen 10018 0 1 POP PEEK
>=20
> LSR-6:/tmp$ cat /proc/net/mpls_out
> 0x00000002 0/0/0 4 PUSH(gen 10014) SET(eth2,10.3.6.3)
>=20
> LSR-6:/tmp$ ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:00:0A:03:06:06
>            inet addr:10.3.6.6  Bcast:10.3.6.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:836 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:401 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            RX bytes:58211 (56.8 Kb)  TX bytes:33901 (33.1 Kb)
>            Interrupt:5
>=20
> eth2      Link encap:Ethernet  HWaddr 00:00:0A:06:0A:06
>            inet addr:10.6.10.6  Bcast:10.6.10.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:601 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            RX bytes:41900 (40.9 Kb)  TX bytes:11922 (11.6 Kb)
>            Interrupt:5
>=20
> -> ougoing interface wrong, IP correct
>=20
> ldp_if_new:
> ENTER: ldp_cfg_if_set
> EXIT: ldp_cfg_if_set
> ENTER: ldp_cfg_entity_set
> PRT: ldp_cfg_entity_set: entity not ready
>=20
> EXIT: ldp_cfg_entity_set
> ENTER: ldp_cfg_entity_get
> EXIT: ldp_cfg_entity_get
> ENTER: ldp_cfg_if_get
> EXIT: ldp_cfg_if_get
> ldp_if_new:
> ENTER: ldp_cfg_if_set
> EXIT: ldp_cfg_if_set
> ENTER: ldp_cfg_entity_set
> PRT: ldp_cfg_entity_set: entity not ready
>=20
> EXIT: ldp_cfg_entity_set
> ENTER: ldp_cfg_entity_get
> EXIT: ldp_cfg_entity_get
> ENTER: ldp_cfg_if_get
> EXIT: ldp_cfg_if_get
> 2003/03/09 10:16:28 MPLS: MPLSd (0.93a) starts
> 2003/03/09 10:16:28 MPLS: interface add lo index 1 flags 73 metric 1 =
mtu
> 16436
> 2003/03/09 10:16:28 MPLS: address add 127.0.0.1 to interface lo
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:28 MPLS: interface add dummy0 index 2 flags 195 =
metric 1
> mtu 1500
> 2003/03/09 10:16:28 MPLS: address add 10.0.26.2 to interface dummy0
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:28 MPLS: interface add eth1 index 3 flags 4163 metric =
1 mtu
> 1500
> 2003/03/09 10:16:28 MPLS: address add 10.3.6.6 to interface eth1
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:28 MPLS: interface add eth2 index 4 flags 4163 metric =
1 mtu
> 1500
> 2003/03/09 10:16:28 MPLS: address add 10.6.10.6 to interface eth2
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:28 MPLS: interface add eth0 index 5 flags 4675 metric =
1 mtu
> 1500
> 2003/03/09 10:16:28 MPLS: address add 10.0.26.2 to interface eth0
> ENTER: _ldp_global_ifmgr_callback
> EXIT: _ldp_global_ifmgr_callback
> 2003/03/09 10:16:28 MPLS: router-id change 10.0.26.2
> 2003/03/09 10:16:28 MPLS: router-id update 10.0.26.2
> ENTER: ldp_cfg_global_set
> ENTER: ldp_global_shutdown
> ENTER: ldp_entity_shutdown
> ENTER: ldp_if_shutdown
> EXIT: ldp_if_shutdown
> EXIT: ldp_entity_shutdown
> ENTER: ldp_entity_shutdown
> ENTER: ldp_if_shutdown
> EXIT: ldp_if_shutdown
> EXIT: ldp_entity_shutdown
> EXIT: ldp_global_shutdown
> EXIT: ldp_cfg_global_set
> ENTER: ldp_cfg_global_set
> EXIT: ldp_cfg_global_set
> ENTER: ldp_cfg_global_set
> ENTER: ldp_global_startup
> ENTER: ldp_entity_startup
> ENTER: ldp_if_startup
> OUT: Hello Send: entity(1)
> OUT: LPD Header : protocolVersion =3D 1
> OUT:    pduLength =3D 30
> OUT:    lsrAddress =3D a001a02
> OUT:    labelSpace =3D 0
> OUT: HELLO MSG ***START***:
> OUT:    baseMsg : uBit =3D 0
> OUT:              msgType =3D 100
> OUT:              msgLength =3D 20
> OUT:              msgId =3D 1
> OUT:     chpTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 400
> OUT:              length =3D 4
> OUT:     chpTlv data: holdTime =3D 15
> OUT:     chpTlv Flags:  target =3D 0
> OUT:                    request =3D 0
> OUT:                    res =3D 0
> OUT:    Hello msg does not have TrAdr TLV
> OUT:     csnTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 402
> OUT:              length =3D 4
> OUT:     csnTlv data: value =3D 6
> OUT: HELLO MSG ***END***:
>=20
> ...
>=20
> ENTER: Prepare_Label_Mapping_Attributes
> EXIT: Prepare_Label_Mapping_Attributes
> ENTER: ldp_label_mapping_send
> ENTER: lsr_cfg_insegment_set
> EXIT: lsr_cfg_insegment_set
> OUT: In Label Added
> OUT: LPD Header : protocolVersion =3D 1
> OUT:    pduLength =3D 33
> OUT:    lsrAddress =3D a001a02
> OUT:    labelSpace =3D 0
> OUT: LABEL MAPPING MSG ***START***:
> OUT:    baseMsg : uBit =3D 0
> OUT:              msgType =3D 400
> OUT:              msgLength =3D 23
> OUT:              msgId =3D 41
> OUT:     fecTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 100
> OUT:              length =3D 7
> OUT:            fecTlv->numberFecElements =3D 1
> OUT:            elem 0 type is 2
> OUT:            Fec Element : type =3D 2, addFam =3D 1, preLen =3D 24, =
address =3D
> a060a00
> OUT:
> OUT:    fecTlv.wcElemExists =3D 0
> OUT:     genLblTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 200
> OUT:              length =3D 4
> OUT:     genLbl data: label =3D 10014
> OUT:    Label mapping msg does not have atm label Tlv
> OUT:    Label mapping msg does not have fr label Tlv
> OUT:    Label mapping msg does not have hop count Tlv
> OUT:    Label mapping msg does not have path vector Tlv
> OUT:    Label mapping msg does not have label messageId Tlv
> OUT:    Label mapping msg does not have LSPID Tlv
> OUT:    Label mapping msg does not have traffic Tlv
> OUT: LABEL MAPPING MSG ***END***:
> OUT: Label Mapping Sent to 0a001502:0 for 0a060a00/24
> EXIT: ldp_label_mapping_send
> ldp_label_mapping_with_xc: exit
> EXIT: ldp_label_mapping_initial_callback
> ENTER: ldp_label_mapping_initial_callback
> OUT: Initial Label Mapping fired: session(4)
> OUT: Processing: 0a001a00/24 via (not an LDP interface)
>=20
> ldp_label_mapping_with_xc: enter
> ENTER: Prepare_Label_Mapping_Attributes
> EXIT: Prepare_Label_Mapping_Attributes
> ENTER: ldp_label_mapping_send
> ENTER: lsr_cfg_insegment_set
> EXIT: lsr_cfg_insegment_set
> OUT: In Label Added
> OUT: LPD Header : protocolVersion =3D 1
> OUT:    pduLength =3D 33
> OUT:    lsrAddress =3D a001a02
> OUT:    labelSpace =3D 0
> OUT: LABEL MAPPING MSG ***START***:
> OUT:    baseMsg : uBit =3D 0
> OUT:              msgType =3D 400
> OUT:              msgLength =3D 23
> OUT:              msgId =3D 42
> OUT:     fecTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 100
> OUT:              length =3D 7
> OUT:            fecTlv->numberFecElements =3D 1
> OUT:            elem 0 type is 2
> OUT:            Fec Element : type =3D 2, addFam =3D 1, preLen =3D 24, =
address =3D a001a00
> OUT:
> OUT:    fecTlv.wcElemExists =3D 0
> OUT:     genLblTlv:
> OUT:     Tlv:
> OUT:     BaseTlv: uBit =3D 0
> OUT:              fBit =3D 0
> OUT:              type =3D 200
> OUT:              length =3D 4
> OUT:     genLbl data: label =3D 10015
> OUT:    Label mapping msg does not have atm label Tlv
> OUT:    Label mapping msg does not have fr label Tlv
> OUT:    Label mapping msg does not have hop count Tlv
> OUT:    Label mapping msg does not have path vector Tlv
>=20

[mpls-linux-general] Mpls tunnel / Zebra / Ospf

[Nicolas T. <nic...@en...>]

Hello,

I have set up a little OSPF network with zebra between some linux boxes =
and it is worling fine.

I also managed to set up MPLS lsp between those machines.

my config is :

LInux 2.4.20
iptables 1.27a
zebra 0.93a patched for mpls

Lets say there is only 2 machines running the same config (simple test =
...) : machine 1 and machine 2


Now i'd like to create a mpls tunnel on a machine 1 with an ip address =
given to it , to map the outgoing traffic from for ex. eth0 to machine 2 =
on it and to see how ospf understand this tunnel ...

What can i do ...

i saw we can use mplsadm to create a tunnel but there seems to be errors =
...

Thx

Nicolas

Re: [mpls-linux-general] Mpls-linux/RSVPd and iptables-1.2.7a

[Nicolas T. <nic...@en...>]

Hello all !
Thx a lot
It is working fine ...

----- Original Message -----
From: "James R. Leu" <jl...@mi...>
To: "Nicolas Tempestini" <nic...@en...>
Cc: <mpl...@li...>
Sent: Monday, March 10, 2003 5:24 PM
Subject: Re: [mpls-linux-general] Mpls-linux/RSVPd and iptables-1.2.7a


> I'm assuming you applied the iptables patch to iptable.
>
> Make sure you enabled:
> Networking options  --->
> [*] Multi Protocol Label Switching - MPLS
>
> _then_
>
> Networking options  --->
> [*] Network packet filtering (replaces ipchains)
>
> _then_
>
> Networking options  --->
> IP: Netfilter Configuration  --->
> <*> IP tables support (required for filtering/masq/NAT)
> <*>   Packet mangling
> <*>     MPLS target support
>
> I know it's convoluted, but the Linux kernel Config specification is
> pretty primitive.
>
> Make sure you are running the modified version of iptables:
> either 'which iptables' should list your compiled version of iptables
> or you need to run iptables which a full path and point it at the correct
> modules.
>
> On Mon, Mar 10, 2003 at 04:12:49PM -0000, Nicolas Tempestini wrote:
> > Hi all,
> >
> > I am trying to set up lsp with a Red Hat 8.0 and a custom kernel 2.4.20.
> >
> > I have followed the instructions on the project Atlantis web site but i
have
> > used iptables-1.2.7a.
> >
> > Errors are :
> >
> > mplsadm ........
> > OK
> > it returns me a key : 0x2 ....
> >
> > whern i try to do : iptables -A OUTPUT ......   -j MPLS --set-key 0x2 ,
it
> > says "unknown args --set-key"
> >
> > I hope i have activated all the options required ( MPLS support , IP
> > filtering ....) on the kernel.
> >
> > Could you help me ?
> >
> > Thx
> >
> > Nicolas
> >
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
> --
> James R. Leu
>

RE: [mpls-linux-general] How can i test my pc without set another pc?

[Markus H. <mh...@as...>]

take a look on user-mode linux (http://user-mode-linux.sourceforge.net)

markus

> -----Original Message-----
> From: e7...@ti... [mailto:e7...@ti...]
> Sent: Friday, March 14, 2003 3:44 PM
> To: mpl...@li...
> Subject: [mpls-linux-general] How can i test my pc without set another
> pc?
>=20
>=20
> Can i test my pc  (i would like to see if my pc do the=20
> feature of MPLS )
> without  set another pc? How can i do it? I'm trying to do it=20
> but, till
> now, i can't do it
> Thanks
>=20
>=20
> __________________________________________________________________
> Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL=20
> Light Mega!
> Tiscali ADSL non teme confronti! Abbonati subito.
> http://point.tiscali.it/adsl/index.shtml
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open!=20
> Get cracking and register here for some mind boggling fun and=20
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>=20

[mpls-linux-general] How can i test my pc without set another pc?

[<e7...@ti...>]

Can i test my pc  (i would like to see if my pc do the feature of MPLS )
without  set another pc? How can i do it? I'm trying to do it but, till
now, i can't do it
Thanks


__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

RE: AW: AW: AW: AW: AW: AW: AW: [mpls-linux-general] iproute

[<e7...@ti...>]

HI
i'm trying to use mplsadm to simulate the forwarding of MPLS packets to
other pcs. Til now i can't do it with this program. My impression is that=

mplsadm is useful only to set the structure, to bind label to FEC but not=

to send packets (or FEC) to the other pc. Isn't it?
How can i send packets with this program?
Thanks in advance
>-- Messaggio Originale --
>From: "Georg Klug" <gk...@gi...>
>To: <e7...@ti...>
>Subject: AW: AW: AW: AW: AW: AW: AW: [mpls-linux-general] iproute
>Date: Mon, 10 Mar 2003 14:23:43 +0100
>
>
>
>Allegato: smime.p7m
>


__________________________________________________________________
Tiscali ADSL, fino a 9 MESI GRATIS sull'offerta Tiscali ADSL Light Mega!
Tiscali ADSL non teme confronti! Abbonati subito.
http://point.tiscali.it/adsl/index.shtml

Re: [mpls-linux-general] In Label add: Invalid argument?

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

On Fri, Mar 14, 2003 at 10:29:29AM +0800, reclusewood wrote:
> Hi, 
>  	I've redhat linux with 2.4.18 kernel and mpls-linux-1.172
> 
> The README tell me that:
> 
> Establish label 34 in label space 0
> -----------------------------------
> 
> mplsadm -A -I gen:34:0
>          |  | |   |  |
>          |  | |   |  label space
>        add  | |   |
>             | |   label
>             | |
>             | generic label
>             |
>             incoming label
> 
> (if you change the -A to -D you will delete the entry)
> 
> but I've got the error information
> 
> "In Label add: Invalid argument"
> 
> what is the reason? thanks a lot.

Blue.

That is the only answer I can give you with the amount of information
you have given me.

Command line?  Contents of /proc/net/mpls_*?  Results from MPLS kernel
debugging?

-- 
James R. Leu