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

[mpls-linux-general] making the ldp_zebra port

[Kauder T. <Tho...@ic...>]

Hi, my name is Thorsten Kauder and I'm doing an internship at Siemens-Germany.
My Job is to make a Linux-machine MPLS-Ready to test routing equipment.

So far I made the mpls run and am able to manually add LSPs.
I'm working with zebra and so I'm trying to get the Zebra-port compiled.

I Have the latest (I think ) version of zebra 0.92a.
and downloaded mpls_linux and ldp_portable from the cvs-tree.

I also changed the ZHOME-variable to the location of my zebra installation.

Now when I try to make the zebra_port I get the following output:

---------------------------------------------------------------------------------------------

linux:/usr/src/cvs/ldp-portable #
linux:/usr/src/cvs/ldp-portable # make ldp_zebra
cd zebra-port ; make libldpport.a CC=gcc CFLAGS="-g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../lib -I/usr/src/zebra-0.90/lib -DSYSCONFDIR=\\\"/tmp/\\\""
make[1]: Entering directory `/usr/src/cvs/ldp-portable/zebra-port'
gcc -g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../lib -I/usr/src/zebra-0.90/lib -DSYSCONFDIR=\"/tmp/\"   -c -o zldp_cli.o zldp_cli.c
In file included from zldp_cli.c:26:
/usr/src/zebra-0.90/lib/sockunion.h:124: conflicting types for `inet_aton'
/usr/include/arpa/inet.h:69: previous declaration of `inet_aton'
make[1]: *** [zldp_cli.o] Error 1
make[1]: Leaving directory `/usr/src/cvs/ldp-portable/zebra-port'
make: *** [ldp_zebra_port] Error 2
linux:/usr/src/cvs/ldp-portable #

------------------------------------------------------------------------------------------------

I would really apreciate it If someone could help me with this problem.

another question to ldp:

If I use : `add global' at the ldp-prompt, the argument behind that is the LSR-ID , right ?!

Thanks in advance.

 

[mpls-linux-general] TC <-> MPLS

[Jens K. <jen...@gm...>]

Hi my name is Jens,

I have install RedHat 7.1 (Kernel 2.4.0) and mpls-patch 0.990.
Now, I will use TC(Traffic Control) and mpls together.

Where can I help me? 
Have someone Information about mpls and QOS for Linux.

How work TC und mpls together. 

Scenario:

|-------------|               |-------------|              |------------|   
          
|  Router1     | <=MPLS=> |  Router2     | <=MPLS=>|  Router3    |
|-------------|               |-------------|              |------------|
        |                                                                   
   |        
       IP                                                                   
   IP      
        |                                                                   
   |        
|-------------|                                                  
|-------------|          
|  Host1         |                                                   |     
Host2     |
|-------------|                                                   
|-------------|



     





-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

Re: Re: [mpls-linux-general] I need some help to read the codes related with MPLS patches

[<jj...@dr...>]

Thanks for your comment, first.
And thanks for you and other peoples that=20
make the great job about the MPLS-Linux.

Before I ask some questions, I must apology about
my lack of English.  Actually I read the RFCs related=20
with MPLS and LDP. But when I looked at the code, MPLS-Linux,=20
I can't figure out the implementation of LIB tables such like
ILM, NHLFE, FTN as descirbed in RFC 3031.
I think that the problem I've been had is not just for
my case. Ofcourse I read the codes.=20

Anyway, I wonder the meaning of the res->proto_data[AUX_PROTO_DATA_MPLS]=20
in route.c as I posted the prevoius mail. It is hard to
follow the code with this because the location of set the
information of code is hard to find.
Is there anybody explain me about that?=20



-------------------------------------------------------
Ki Young Jung (jj...@ic...)
Information and Communications University(ICU)
Broadband Network Laboratory(http://bnlab.icu.ac.kr)
58-4 Hwaam-dong, Yusong-gu, Taejon, 305-732, KOREA
Tel)+82-42-866-6182, 016-370-1751 Fax)+82-42-866-6110=20
-------------------------------------------------------

----- Original Message -----=20
From: James R. Leu=20
To: Á=A2=B4=A1=BEâ=A2=AFµ=20
Cc: mpl...@li...=20
Sent: Tuesday, November 20, 2001 1:21 AM
Subject: Re: [mpls-linux-general] I need some help to read the codes rela=
ted with MPLS patches


You're already using the best document there is, the code.  Keep digging
through it, you'll figure it out.

If you run into a road block, and have specific questions feel free to
e-mail that list with it.  I or someone else will answer.

Jim

On Mon, Nov 19, 2001 at 11:58:51PM +0900, Á=A2=B4=A1=BEâ=A2=AF=
µ wrote:
> I've looked at the code, and i think that the binding point of mpls_out=
put() is in route.c
>=20
> After patching mpls codes, in ./net/ipv4/route.c
>=20
> void rt_set_nexthop(struct rtable *rt, struct fib_result *res, u32 itag=
)
> {
>       struct fib_info *fi =3D res->fi;
> =20
> =A2=AE¦
> =20
> #ifdef CONFIG_MPLS
>       /*  JLEU: we need to do this here because both
>       * ip_route_output_slow() and ip_route_output_slow()
>       * us this to finish the next hop calculations
>       */
>       if(res->proto_data[AUX_PROTO_DATA_MPLS]) {
>           struct mpls_out_info *moi;
>           int i;
> =20
>           MPLS_DEBUG(("rt_set_nexthop: adding label to dst\n"));
>           MPLS_DEBUG(("rt_set_nexthop: before - mtu =3D %d\n",
>             rt->u.dst.pmtu));
>           rt->u.dst.output =3D mpls_output;    /* HERE */
>           rt->u.dst.dst_proto_data[AUX_PROTO_DATA_MPLS] =3D=20
>             res->proto_data[AUX_PROTO_DATA_MPLS];
>           moi =3D res->proto_data[AUX_PROTO_DATA_MPLS];
> mpls_again:
>           for(i=3D0;i<moi->moi_instruction_length;i++) {
>             switch(moi->moi_instruction[i].mi_opcode) {
>                 case MPLS_OP_FWD:
>                   moi =3D (struct mpls_out_info*)
>                     moi->moi_instruction[i].mi_data;
>                   goto mpls_again;
>                   break;
>                 case MPLS_OP_PUSH:
>                   rt->u.dst.pmtu -=3D 4;
>                   break;
>             }
>           }
>           MPLS_DEBUG(("rt_set_nexthop: after - mtu =3D %d\n",
>             rt->u.dst.pmtu));
>       }
> =20
> =A2=AE&brvbar;
> =20
> }
> =20
> If res->proto_data[AUX_PROTO_DATA_MPLS] have a value (not zero)
> then the output related function is binded with mpls_output()
> so the function is invoked.
> =20
> But I still try to find work that describes the structures or methods o=
f MPLS in Linux .=20
> Is there anyone who know this? I hope to learn from him or her.
> =20
> Especially, I want to know the semantics of proto_data[AUX_PROTO_DATA_M=
PLS].
> =20
> Thanks, in advance.
> =20
> B.E.
> =20
> Kiyoung Jung
> -------------------------------------------------------
> Ki Young Jung (jj...@ic...)
> Information and Communications University(ICU)
> Broadband Network Laboratory(http://bnlab.icu.ac.kr)
> 58-4 Hwaam-dong, Yusong-gu, Taejon, 305-732, KOREA
> Tel)+82-42-866-6182, 016-370-1751 Fax)+82-42-866-6110=20
> -------------------------------------------------------
> -------------------------------------------------
> DreamWiz Free Mail @ http://www.dreamwiz.com/
> DreamSearch Click the world!!! http://search.dreamwiz.com/
>=20

--=20
James R. Leu



-------------------------------------------------
DreamWiz Free Mail @ http://www.dreamwiz.com/
DreamSearch Click the world!!! http://search.dreamwiz.com/

[mpls-linux-general] Re: your mail

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

On Mon, Nov 19, 2001 at 10:57:11AM -0500, Hanxi Zhang wrote:
> 
> Hello Mr. Leu:
> 
> I'm a beginner of mpls-linux. I posted
> on the mailing list a couple general questions
> which are not answered yet. I wonder if
> you could give me some ideas about
> the following two questions, thank you
> very much.
> 
> 1. mplsadm is a manual tool to setup LSP paths
> right? So does it mean that it takes care of
> the setting up of layer 2 connections such
> as a ATM or FR connection, or just map

It can handle handle all of the setup for ethernet (building all
of the correct structires so the networking stack will ARP for the
MAC address) and for ATM (build the correct ATM structures that represent
a uni-directional VC), but does not work on frame relay yet.  I do not have
a means to test FR, so I never finished development on it.

> a FEC to a layer 2 connection that is already
> on?

I does this as well.  Is places a peice of info in the IPv4 routing entries
tha point to the the outgoing MPLS structures.

> 2. When LSP(s) are setup by mplsadm,
> is there any label request/mapping or
> hello messages between those machines
> running mplsadm? In other words, is mplsadm
> a REAL emulation tool for MPLS?

No.  mplsadm only "programs" the mpls forwarding plan. (you can think of it
like the 'route' command which can setup static routes).  You can create
static LSPs with it. If you many dynamic LSP setup you will need to use a 
signaling protocol like LDP or RSVP-TE ( to keep with my analogy, it like
running OSPF via zebra which give you dynamic route setup). The system calls
used by mplsadm would also used by a MPLS signaling protocol to build an LSP
from the info it learns via signalling. (just as zebra uses that same system
calls to add dynamic routing info as does the 'route' command)

> Hanxi
> 
> 
> 
> 
> ----------------------------------------------------------
> Hanxi Zhang
> Research Engineer
> Broadband and Optical Networking
> Communications Research Center
> 
> Tel: (613)991-2960 Fax: (613)998-2753
> 3701 Carling Ave, Ottawa, ON K2H 8S2
> ----------------------------------------------------------
> 
> 
> 
> 

-- 
James R. Leu

Re: [mpls-linux-general] I need some help to read the codes related with MPLS patches

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

You're already using the best document there is, the code.  Keep digging
through it, you'll figure it out.

If you run into a road block, and have specific questions feel free to
e-mail that list with it.  I or someone else will answer.

Jim

On Mon, Nov 19, 2001 at 11:58:51PM +0900, =C1=A4=B1=E2=BF=B5 wrote:
> I've looked at the code, and i think that the binding point of mpls_out=
put() is in route.c
>=20
> After patching mpls codes, in ./net/ipv4/route.c
>=20
> void rt_set_nexthop(struct rtable *rt, struct fib_result *res, u32 itag=
)
> {
>       struct fib_info *fi =3D res->fi;
> =20
> =A1=A6
> =20
> #ifdef CONFIG_MPLS
>       /*  JLEU: we need to do this here because both
>       * ip_route_output_slow() and ip_route_output_slow()
>       * us this to finish the next hop calculations
>       */
>       if(res->proto_data[AUX_PROTO_DATA_MPLS]) {
>           struct mpls_out_info *moi;
>           int i;
> =20
>           MPLS_DEBUG(("rt_set_nexthop: adding label to dst\n"));
>           MPLS_DEBUG(("rt_set_nexthop: before - mtu =3D %d\n",
>             rt->u.dst.pmtu));
>           rt->u.dst.output =3D mpls_output;    /* HERE */
>           rt->u.dst.dst_proto_data[AUX_PROTO_DATA_MPLS] =3D=20
>             res->proto_data[AUX_PROTO_DATA_MPLS];
>           moi =3D res->proto_data[AUX_PROTO_DATA_MPLS];
> mpls_again:
>           for(i=3D0;i<moi->moi_instruction_length;i++) {
>             switch(moi->moi_instruction[i].mi_opcode) {
>                 case MPLS_OP_FWD:
>                   moi =3D (struct mpls_out_info*)
>                     moi->moi_instruction[i].mi_data;
>                   goto mpls_again;
>                   break;
>                 case MPLS_OP_PUSH:
>                   rt->u.dst.pmtu -=3D 4;
>                   break;
>             }
>           }
>           MPLS_DEBUG(("rt_set_nexthop: after - mtu =3D %d\n",
>             rt->u.dst.pmtu));
>       }
> =20
> =A1=A6
> =20
> }
> =20
> If res->proto_data[AUX_PROTO_DATA_MPLS] have a value (not zero)
> then the output related function is binded with mpls_output()
> so the function is invoked.
> =20
> But I still try to find work that describes the structures or methods o=
f MPLS in Linux .=20
> Is there anyone who know this? I hope to learn from him or her.
> =20
> Especially, I want to know the semantics of proto_data[AUX_PROTO_DATA_M=
PLS].
> =20
> Thanks, in advance.
> =20
> B.E.
> =20
> Kiyoung Jung
> -------------------------------------------------------
> Ki Young Jung (jj...@ic...)
> Information and Communications University(ICU)
> Broadband Network Laboratory(http://bnlab.icu.ac.kr)
> 58-4 Hwaam-dong, Yusong-gu, Taejon, 305-732, KOREA
> Tel)+82-42-866-6182, 016-370-1751 Fax)+82-42-866-6110=20
> -------------------------------------------------------
> -------------------------------------------------
> DreamWiz Free Mail @ http://www.dreamwiz.com/
> DreamSearch Click the world!!! http://search.dreamwiz.com/
>=20

--=20
James R. Leu

[mpls-linux-general] I need some help to read the codes related with MPLS patches

[<jj...@dr...>]

I've looked at the code, and i think that the binding point of mpls_outpu=
t() is in route.c

After patching mpls codes, in ./net/ipv4/route.c

void rt_set_nexthop(struct rtable *rt, struct fib_result *res, u32 itag)
{
      struct fib_info *fi =3D res->fi;
=20
=A1=A6
=20
#ifdef CONFIG_MPLS
      /*  JLEU: we need to do this here because both
      * ip_route_output_slow() and ip_route_output_slow()
      * us this to finish the next hop calculations
      */
      if(res->proto_data[AUX_PROTO_DATA_MPLS]) {
          struct mpls_out_info *moi;
          int i;
=20
          MPLS_DEBUG(("rt_set_nexthop: adding label to dst\n"));
          MPLS_DEBUG(("rt_set_nexthop: before - mtu =3D %d\n",
            rt->u.dst.pmtu));
          rt->u.dst.output =3D mpls_output;    /* HERE */
          rt->u.dst.dst_proto_data[AUX_PROTO_DATA_MPLS] =3D=20
            res->proto_data[AUX_PROTO_DATA_MPLS];
          moi =3D res->proto_data[AUX_PROTO_DATA_MPLS];
mpls_again:
          for(i=3D0;i<moi->moi_instruction_length;i++) {
            switch(moi->moi_instruction[i].mi_opcode) {
                case MPLS_OP_FWD:
                  moi =3D (struct mpls_out_info*)
                    moi->moi_instruction[i].mi_data;
                  goto mpls_again;
                  break;
                case MPLS_OP_PUSH:
                  rt->u.dst.pmtu -=3D 4;
                  break;
            }
          }
          MPLS_DEBUG(("rt_set_nexthop: after - mtu =3D %d\n",
            rt->u.dst.pmtu));
      }
=20
=A1=A6
=20
}
=20
If res->proto_data[AUX_PROTO_DATA_MPLS] have a value (not zero)
then the output related function is binded with mpls_output()
so the function is invoked.
=20
But I still try to find work that describes the structures or methods of =
MPLS in Linux .=20
Is there anyone who know this? I hope to learn from him or her.
=20
Especially, I want to know the semantics of proto_data[AUX_PROTO_DATA_MPL=
S].
=20
Thanks, in advance.
=20
B.E.
=20
Kiyoung Jung
-------------------------------------------------------
Ki Young Jung (jj...@ic...)
Information and Communications University(ICU)
Broadband Network Laboratory(http://bnlab.icu.ac.kr)
58-4 Hwaam-dong, Yusong-gu, Taejon, 305-732, KOREA
Tel)+82-42-866-6182, 016-370-1751 Fax)+82-42-866-6110=20
-------------------------------------------------------
-------------------------------------------------
DreamWiz Free Mail @ http://www.dreamwiz.com/
DreamSearch Click the world!!! http://search.dreamwiz.com/

[mpls-linux-general] General Questions About mplsadm for linux

[Hanxi Z. <han...@cr...>]

Hi All:

I've installed mpls-linux 0.993, and I've a few
general questions regarding it:

1. mplsadm is a manual tool to setup LSP paths
     right? So does it mean that it takes care of
     the setting up of layer 2 connections such
     as a ATM or FR connection, or just map
     a FEC to a layer 2 connection that is already
     on?

2. When LSP(s) are setup by mplsadm,
     is there any label request/mapping or
     hello messages between those machines
     running mplsadm? In other words, is mplsadm
     a REAL emulation tool for MPLS?

3. For those folks who are playing intensively
     with mplsadm (and portable ldp), what do
     you have in mind about any possible research
     potentials, by customizing the source codes?

A lot of thanks in advance.

[mpls-linux-general] MPLS tunnels OOPsing kernel [Follow Up]

[<igb...@ya...>]

Ok,

We have gone through and turned debugging on when
setting up a tunnel.


Here are the commands we used, the debug output from
mplsadm and the output of /proc/net/mpls_tunnel



Commands:


mplsadm -d
mplsadm -L eth1:0
mplsadm -AO gen:100:eth1:ipv4:10.0.1.1
mplsadm -AT mpls0
ifconfig mpls0 10.0.1.1 netmask 255.255.255.252
mplsadm -BO gen:100:eth1 -T mpls0
route add -host 10.0.1.2/32 mpls0


Output from debug messages:

MPLS: debug is now on
mpls_set_labelspace: enter
mpls_set_labelspace: labelspace(0)
mpls_set_labelspace: exit
mpls_add_out_label: enter
mpls_make_dst: enter
mpls_make_dst: before bind neighbor
mpls_make_dst: bind neighbor succeeded
mpls_make_dst: exit(c3816be0)
mpls_info_default_moi_instruction: enter
mpls_info_default_moi_instruction: exit
Label GEN 100
Key GEN 100 5
mpls_add_out_label: exit
mpls_tunnel_add_out: enter
mpls_tunnel_add_out: error getting node in radix tree



and the output of /proc/net/mpls_tunnel

mpls0 00000000


An ifconfig on the mpls0 interface shows that the link
encapsulation as UNSPEC and that the addr of the
tunnel and the point to point address are the same. Is
this correct ???

As soon as any traffic is sent down the tunnel the
machine OOPS's with the output we sent yesterday.

The last line of the mplsadm output seems to be most
interesting. Any idea why it should say that ??


Thanks





__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

Re: [mpls-linux-general] MPLS tunnels OOPsing kernel

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

On Thu, Nov 15, 2001 at 04:38:04PM +0000, iain barnes wrote:
> Hi James,
> 
> Thanks for the quick reply. 
> 
> 
> Here are the commands that we have used (just to make
> sure we are doing it right)
> 
> 
> mplsadm -AT mpls0
> ifconfig mpls0 <ip address> netmask <netmask>
> mplsadm -BO gen:200:eth3 -T mpls0
> route add -host <ip address>/32 mpls0
> 
> 
> That all works OK.
> 
> 
> The output of mpls_tunnel is
> 
> mpls0 00000000

        ^^^^^^^^ that ain't good :-)

Looks like your 'mplsadm -BO gen:200:eth3 -T mpls0' didn't succeed.
Try turning on MPLS kernel debugging before executing that command
by doing a 'mplsadm -d'

I think your missing a 'mplsadm -AO gen:200:eth3:ipv4:<nh ip>'
before doing the 'mplsadm -BO ...'

You need to create the outgoing label before trying to bind it to a
tunnel.

No matter what I need to fix tunnel code not to crash when sending packets
without a valid outgoing label.  I think I have a fix, I will try it out
tonight and let you know my results.

Jim

> Then, when try and ping the host everything goes belly
> up, this time the ping process segfaulted and errors
> were printed to the system log.
> 
> Attached is a copy of the  message that we took out of
> the syslog.
> 
> We can get simple packet marking working and have had
> MPLS traffic moving between hosts, it's just when we
> start trying to create tunnels.
> 
> 
> Again, anymore information we can provide to help with
> this, then let me know.
> 
> 
> Thanks
> 
> 
> 
> --- "James R. Leu" <jl...@mi...> wrote: > I've
> seen this as well.  If the tunnel doesn't have
> > a valid outgoing
> > label it tries to free the packet.  The opps occurs
> > when freeing the packet.
> > 
> > To make sure this is the bug your getting hit with,
> > check the contents of
> > /proc/net/mpls_tunnel after creating the tunnel and
> > binding a label to it.
> > If you do not see a hex key (for the outgoing label)
> > then the
> > tunnel <-> outgoing label binding didn't work.  Let
> > me know what you see.
> > 
> > Jim
> > 
> > On Thu, Nov 15, 2001 at 02:19:51PM +0000, iain
> > barnes wrote:
> > > Hi,
> > > 
> > > 
> > > We are using the latest DSMPLS patch against 2.4.9
> > to
> > > test MPLS and are having trouble creating tunnels.
> > 
> > > 
> > > I was wondering what the status of the tunnel code
> > > currently is.
> > > 
> > > 
> > > The problem occurs when we try to send data down
> > the
> > > tunnel. We can set it up correctly but at the
> > moment
> > > we try and send data down it, the kernel OOPS's.We
> > > haven't tried using any of the DiffServ mapping
> > yet,
> > > just played with the examples from the standard
> > MPLS
> > > code.
> > > 
> > > Is this a known problem/limitation, or are we
> > probably
> > > doing something wrong.
> > > 
> > > If tunnels work for other people, then let us know
> > > what information we can provide so that we can get
> > > this sorted.
> > > 
> > > Thanks
> > > 
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Everything you'll ever need on one web page from
> > News and Sport to Email and Music Charts
> > > http://uk.my.yahoo.com
> > > 
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > 
> > -- 
> > James R. Leu
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general 
> 
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
Content-Description: capture.txt
> Nov 15 16:18:15 localhost kernel: Warning: kfree_skb passed an skb still on a list (from c0192ee5).
> Nov 15 16:18:15 localhost kernel: kernel BUG at skbuff.c:328!
> Nov 15 16:18:15 localhost kernel: invalid operand: 0000
> Nov 15 16:18:15 localhost kernel: CPU:    0
> Nov 15 16:18:15 localhost kernel: EIP:    0010:[__kfree_skb+49/320]
> Nov 15 16:18:15 localhost kernel: EIP:    0010:[<c018f431>]
> Nov 15 16:18:15 localhost kernel: EFLAGS: 00010286
> Nov 15 16:18:15 localhost kernel: eax: 0000001c   ebx: c7ec9800   ecx: c0576000   edx: c020df08
> Nov 15 16:18:15 localhost kernel: esi: c01f8780   edi: c01f77c0   ebp: c5ca85b0   esp: c46bdccc
> Nov 15 16:18:15 localhost kernel: ds: 0018   es: 0018   ss: 0018
> Nov 15 16:18:15 localhost kernel: Process ping (pid: 3538, stackpage=c46bd000)
> Nov 15 16:18:15 localhost kernel: Stack: c01f7546 c01f7720 00000148 c7ec9800 c0192ee5 c7ec9800 40001db0 c7ec9800 
> Nov 15 16:18:15 localhost kernel:        000000f0 00000040 c7ec9800 00000000 c01a2d9b c7ec9800 0804e720 00000040 
> Nov 15 16:18:15 localhost kernel:        00000000 c5ca85b4 c5ca85b0 c7ec9800 c5ca85b0 c01a3ab5 c5ca85b4 c5ca85b0 
> Nov 15 16:18:15 localhost kernel: Call Trace: [dev_queue_xmit+517/608] [ip_output+203/288] [ip_build_xmit+709/912] [ip_build_xmit+749/912] [raw_sendmsg+720/848] 
> Nov 15 16:18:15 localhost kernel: Call Trace: [<c0192ee5>] [<c01a2d9b>] [<c01a3ab5>] [<c01a3add>] [<c01b9aa0>] 
> Nov 15 16:18:15 localhost kernel:    [raw_getfrag+0/32] [n_tty_receive_buf+2745/2800] [inet_sendmsg+53/64] [sock_sendmsg+108/144] [move_addr_to_kernel+50/80] [sys_sendmsg+383/480] 
> Nov 15 16:18:15 localhost kernel:    [<c01b96f0>] [<c01598f9>] [<c01c03a5>] [<c018c37c>] [<c018bec2>] [<c018d54f>] 
> Nov 15 16:18:15 localhost kernel:    [do_no_page+77/192] [opost+446/464] [tty_write+334/448] [sys_rt_sigaction+147/240] [sys_socketcall+476/512] [system_call+51/56] 
> Nov 15 16:18:15 localhost kernel:    [<c011f0cd>] [<c015886e>] [<c015667e>] [<c011a973>] [<c018d9cc>] [<c0106ce7>] 
> Nov 15 16:18:15 localhost kernel: 
> Nov 15 16:18:15 localhost kernel: Code: 0f 0b 83 c4 0c 8b 54 24 08 8b 42 28 85 c0 74 07 ff 48 04 8b 
> Nov 15 16:18:22 localhost kernel: Warning: kfree_skb passed an skb still on a list (from c0192ee5).
> Nov 15 16:18:22 localhost kernel: kernel BUG at skbuff.c:328!
> Nov 15 16:18:22 localhost kernel: invalid operand: 0000
> Nov 15 16:18:22 localhost kernel: CPU:    0
> Nov 15 16:18:22 localhost kernel: EIP:    0010:[__kfree_skb+49/320]
> Nov 15 16:18:22 localhost kernel: EIP:    0010:[<c018f431>]
> Nov 15 16:18:22 localhost kernel: EFLAGS: 00010286
> Nov 15 16:18:22 localhost kernel: eax: 0000001c   ebx: c7ec9800   ecx: c0576000   edx: c020df08
> Nov 15 16:18:22 localhost kernel: esi: c01f8780   edi: c01f77c0   ebp: c5ca85b0   esp: c46bdccc
> Nov 15 16:18:22 localhost kernel: ds: 0018   es: 0018   ss: 0018
> Nov 15 16:18:22 localhost kernel: Process ping (pid: 3539, stackpage=c46bd000)
> Nov 15 16:18:22 localhost kernel: Stack: c01f7546 c01f7720 00000148 c7ec9800 c0192ee5 c7ec9800 40001db0 c7ec9800 
> Nov 15 16:18:22 localhost kernel:        000000f0 00000040 c7ec9800 00000000 c01a2d9b c7ec9800 0804e720 00000040 
> Nov 15 16:18:22 localhost kernel:        00000000 c5ca85b4 c5ca85b0 c7ec9800 c5ca85b0 c01a3ab5 c5ca85b4 c5ca85b0 
> Nov 15 16:18:22 localhost kernel: Call Trace: [dev_queue_xmit+517/608] [ip_output+203/288] [ip_build_xmit+709/912] [ip_build_xmit+749/912] [raw_sendmsg+720/848] 
> Nov 15 16:18:22 localhost kernel: Call Trace: [<c0192ee5>] [<c01a2d9b>] [<c01a3ab5>] [<c01a3add>] [<c01b9aa0>] 
> Nov 15 16:18:22 localhost kernel:    [raw_getfrag+0/32] [n_tty_receive_buf+2745/2800] [inet_sendmsg+53/64] [sock_sendmsg+108/144] [move_addr_to_kernel+50/80] [sys_sendmsg+383/480] 
> Nov 15 16:18:22 localhost kernel:    [<c01b96f0>] [<c01598f9>] [<c01c03a5>] [<c018c37c>] [<c018bec2>] [<c018d54f>] 
> Nov 15 16:18:22 localhost kernel:    [do_no_page+77/192] [opost+446/464] [tty_write+334/448] [sys_rt_sigaction+147/240] [sys_socketcall+476/512] [system_call+51/56] 
> Nov 15 16:18:22 localhost kernel:    [<c011f0cd>] [<c015886e>] [<c015667e>] [<c011a973>] [<c018d9cc>] [<c0106ce7>] 
> Nov 15 16:18:22 localhost kernel: 
> Nov 15 16:18:22 localhost kernel: Code: 0f 0b 83 c4 0c 8b 54 24 08 8b 42 28 85 c0 74 07 ff 48 04 8b 
> Nov 15 16:18:24 localhost kernel: Warning: kfree_skb passed an skb still on a list (from c0192ee5).
> Nov 15 16:18:24 localhost kernel: kernel BUG at skbuff.c:328!
> Nov 15 16:18:24 localhost kernel: invalid operand: 0000
> Nov 15 16:18:24 localhost kernel: CPU:    0
> Nov 15 16:18:24 localhost kernel: EIP:    0010:[__kfree_skb+49/320]
> Nov 15 16:18:24 localhost kernel: EIP:    0010:[<c018f431>]
> Nov 15 16:18:24 localhost kernel: EFLAGS: 00010286
> Nov 15 16:18:24 localhost kernel: eax: 0000001c   ebx: c08e0760   ecx: c0576000   edx: c020df08
> Nov 15 16:18:24 localhost kernel: esi: c01f8780   edi: c01f77c0   ebp: c5ca85b0   esp: c46bdccc
> Nov 15 16:18:24 localhost kernel: ds: 0018   es: 0018   ss: 0018
> Nov 15 16:18:24 localhost kernel: Process ping (pid: 3540, stackpage=c46bd000)
> Nov 15 16:18:24 localhost kernel: Stack: c01f7546 c01f7720 00000148 c08e0760 c0192ee5 c08e0760 40001db0 c08e0760 
> Nov 15 16:18:24 localhost kernel:        000000f0 00000040 c08e0760 00000000 c01a2d9b c08e0760 0804e720 00000040 
> Nov 15 16:18:24 localhost kernel:        00000000 c5ca85b4 c5ca85b0 c08e0760 c5ca85b0 c01a3ab5 c5ca85b4 c5ca85b0 
> Nov 15 16:18:24 localhost kernel: Call Trace: [dev_queue_xmit+517/608] [ip_output+203/288] [ip_build_xmit+709/912] [ip_build_xmit+749/912] [raw_sendmsg+720/848] 
> Nov 15 16:18:24 localhost kernel: Call Trace: [<c0192ee5>] [<c01a2d9b>] [<c01a3ab5>] [<c01a3add>] [<c01b9aa0>] 
> Nov 15 16:18:24 localhost kernel:    [raw_getfrag+0/32] [n_tty_receive_buf+2745/2800] [inet_sendmsg+53/64] [sock_sendmsg+108/144] [move_addr_to_kernel+50/80] [sys_sendmsg+383/480] 
> Nov 15 16:18:24 localhost kernel:    [<c01b96f0>] [<c01598f9>] [<c01c03a5>] [<c018c37c>] [<c018bec2>] [<c018d54f>] 
> Nov 15 16:18:24 localhost kernel:    [do_no_page+77/192] [opost+446/464] [tty_write+334/448] [sys_rt_sigaction+147/240] [sys_socketcall+476/512] [system_call+51/56] 
> Nov 15 16:18:24 localhost kernel:    [<c011f0cd>] [<c015886e>] [<c015667e>] [<c011a973>] [<c018d9cc>] [<c0106ce7>] 
> Nov 15 16:18:24 localhost kernel: 
> Nov 15 16:18:24 localhost kernel: Code: 0f 0b 83 c4 0c 8b 54 24 08 8b 42 28 85 c0 74 07 ff 48 04 8b 
> Nov 15 16:18:24 localhost kernel: Warning: kfree_skb passed an skb still on a list (from c0192ee5).
> Nov 15 16:18:24 localhost kernel: kernel BUG at skbuff.c:328!
> Nov 15 16:18:24 localhost kernel: invalid operand: 0000
> Nov 15 16:18:24 localhost kernel: CPU:    0
> Nov 15 16:18:24 localhost kernel: EIP:    0010:[__kfree_skb+49/320]
> Nov 15 16:18:24 localhost kernel: EIP:    0010:[<c018f431>]
> Nov 15 16:18:24 localhost kernel: EFLAGS: 00010286
> Nov 15 16:18:24 localhost kernel: eax: 0000001c   ebx: c0731e20   ecx: c0576000   edx: c020df08
> Nov 15 16:18:24 localhost kernel: esi: c01f8780   edi: c01f77c0   ebp: c5ca8eb0   esp: c46bdccc
> Nov 15 16:18:24 localhost kernel: ds: 0018   es: 0018   ss: 0018
> Nov 15 16:18:24 localhost kernel: Process ping (pid: 3541, stackpage=c46bd000)
> Nov 15 16:18:24 localhost kernel: Stack: c01f7546 c01f7720 00000148 c0731e20 c0192ee5 c0731e20 40001db0 c0731e20 
> Nov 15 16:18:24 localhost kernel:        000000f0 00000040 c0731e20 00000000 c01a2d9b c0731e20 0804e720 00000040 
> Nov 15 16:18:24 localhost kernel:        00000000 c5ca8eb4 c5ca8eb0 c0731e20 c5ca8eb0 c01a3ab5 c5ca8eb4 c5ca8eb0 
> Nov 15 16:18:24 localhost kernel: Call Trace: [dev_queue_xmit+517/608] [ip_output+203/288] [ip_build_xmit+709/912] [ip_build_xmit+749/912] [raw_sendmsg+720/848] 
> Nov 15 16:18:24 localhost kernel: Call Trace: [<c0192ee5>] [<c01a2d9b>] [<c01a3ab5>] [<c01a3add>] [<c01b9aa0>] 
> Nov 15 16:18:24 localhost kernel:    [raw_getfrag+0/32] [n_tty_receive_buf+2745/2800] [inet_sendmsg+53/64] [sock_sendmsg+108/144] [move_addr_to_kernel+50/80] [sys_sendmsg+383/480] 
> Nov 15 16:18:24 localhost kernel:    [<c01b96f0>] [<c01598f9>] [<c01c03a5>] [<c018c37c>] [<c018bec2>] [<c018d54f>] 
> Nov 15 16:18:24 localhost kernel:    [do_no_page+77/192] [opost+446/464] [tty_write+334/448] [sys_rt_sigaction+147/240] [sys_socketcall+476/512] [system_call+51/56] 
> Nov 15 16:18:24 localhost kernel:    [<c011f0cd>] [<c015886e>] [<c015667e>] [<c011a973>] [<c018d9cc>] [<c0106ce7>] 
> Nov 15 16:18:24 localhost kernel: 
> Nov 15 16:18:24 localhost kernel: Code: 0f 0b 83 c4 0c 8b 54 24 08 8b 42 28 85 c0 74 07 ff 48 04 8b 


-- 
James R. Leu

Re: [mpls-linux-general] MPLS tunnels OOPsing kernel

[<igb...@ya...>]

Hi James,

Thanks for the quick reply. 


Here are the commands that we have used (just to make
sure we are doing it right)


mplsadm -AT mpls0
ifconfig mpls0 <ip address> netmask <netmask>
mplsadm -BO gen:200:eth3 -T mpls0
route add -host <ip address>/32 mpls0


That all works OK.


The output of mpls_tunnel is

mpls0 00000000

Then, when try and ping the host everything goes belly
up, this time the ping process segfaulted and errors
were printed to the system log.

Attached is a copy of the  message that we took out of
the syslog.

We can get simple packet marking working and have had
MPLS traffic moving between hosts, it's just when we
start trying to create tunnels.


Again, anymore information we can provide to help with
this, then let me know.


Thanks



--- "James R. Leu" <jl...@mi...> wrote: > I've
seen this as well.  If the tunnel doesn't have
> a valid outgoing
> label it tries to free the packet.  The opps occurs
> when freeing the packet.
> 
> To make sure this is the bug your getting hit with,
> check the contents of
> /proc/net/mpls_tunnel after creating the tunnel and
> binding a label to it.
> If you do not see a hex key (for the outgoing label)
> then the
> tunnel <-> outgoing label binding didn't work.  Let
> me know what you see.
> 
> Jim
> 
> On Thu, Nov 15, 2001 at 02:19:51PM +0000, iain
> barnes wrote:
> > Hi,
> > 
> > 
> > We are using the latest DSMPLS patch against 2.4.9
> to
> > test MPLS and are having trouble creating tunnels.
> 
> > 
> > I was wondering what the status of the tunnel code
> > currently is.
> > 
> > 
> > The problem occurs when we try to send data down
> the
> > tunnel. We can set it up correctly but at the
> moment
> > we try and send data down it, the kernel OOPS's.We
> > haven't tried using any of the DiffServ mapping
> yet,
> > just played with the examples from the standard
> MPLS
> > code.
> > 
> > Is this a known problem/limitation, or are we
> probably
> > doing something wrong.
> > 
> > If tunnels work for other people, then let us know
> > what information we can provide so that we can get
> > this sorted.
> > 
> > Thanks
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Everything you'll ever need on one web page from
> News and Sport to Email and Music Charts
> > http://uk.my.yahoo.com
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general 

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

Re: [mpls-linux-general] MPLS tunnels OOPsing kernel

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

I've seen this as well.  If the tunnel doesn't have a valid outgoing
label it tries to free the packet.  The opps occurs when freeing the packet.

To make sure this is the bug your getting hit with, check the contents of
/proc/net/mpls_tunnel after creating the tunnel and binding a label to it.
If you do not see a hex key (for the outgoing label) then the
tunnel <-> outgoing label binding didn't work.  Let me know what you see.

Jim

On Thu, Nov 15, 2001 at 02:19:51PM +0000, iain barnes wrote:
> Hi,
> 
> 
> We are using the latest DSMPLS patch against 2.4.9 to
> test MPLS and are having trouble creating tunnels. 
> 
> I was wondering what the status of the tunnel code
> currently is.
> 
> 
> The problem occurs when we try to send data down the
> tunnel. We can set it up correctly but at the moment
> we try and send data down it, the kernel OOPS's.We
> haven't tried using any of the DiffServ mapping yet,
> just played with the examples from the standard MPLS
> code.
> 
> Is this a known problem/limitation, or are we probably
> doing something wrong.
> 
> If tunnels work for other people, then let us know
> what information we can provide so that we can get
> this sorted.
> 
> Thanks
> 
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] MPLS tunnels OOPsing kernel

[<igb...@ya...>]

Hi,


We are using the latest DSMPLS patch against 2.4.9 to
test MPLS and are having trouble creating tunnels. 

I was wondering what the status of the tunnel code
currently is.


The problem occurs when we try to send data down the
tunnel. We can set it up correctly but at the moment
we try and send data down it, the kernel OOPS's.We
haven't tried using any of the DiffServ mapping yet,
just played with the examples from the standard MPLS
code.

Is this a known problem/limitation, or are we probably
doing something wrong.

If tunnels work for other people, then let us know
what information we can provide so that we can get
this sorted.

Thanks

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

[mpls-linux-general] Configuration dumps as asked (MPLS testing problem).

[Mouli T <mou...@ya...>]

Hi,
I'm having problems in setting up LSP between two
LERs. We r trying the README.example given in
mpls-linux-0.993/utils.

When we are trying to ping or telnet the other system
the data is not going thru MPLS. Instead it is using
ip_output. This, we observed by putting some 
additional printks in route.c and fib_hash.c

We are sending the configuration and some important
dumps in the attached file. Please help me.





BTW where is the code in ipv4 which is responsible for
picking up mpls_output. Actually this should happen
thru moi->moi_dst->u.dst.output. In our case though 
fib_hash_lookup is returning proper res (with correct
moi) for our destination, in ip_route_output_slow()
code is going to "make_route:" and finally I fear the
destination prepared there (i.e. rth with output
function as ip_output) is being registered with
skb->dst. I guess thats the reason why ip_output is
being called instead of mpls_output.

Also we observed that the code responsible for picking
up mpls_output() is there in route.c.rej.
Now where has this gone?

To sumup our question how and where ip code is using
dst prepared by mpls?

Thanks in advance.

Mouli.

__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com

Re: [mpls-linux-general] Problem Installing mplsadm on redhat

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

The patch had a conflict in linux/include/linux/if_arp.h
make it look something like this:

#define ARPHRD_IEEE80211 801            /* IEEE 802.11                  */
#define ARPHRD_MPLS_TUNNEL 899          /* MPLS Tunnel Interface        */

#define ARPHRD_VOID       0xFFFF        /* Void type, nothing is known */

It should compile fine for you then.

Jim


On Wed, Nov 14, 2001 at 10:48:01AM -0500, Hanxi Zhang wrote:
> 
> Hi All:
> 
> I came across a problem when trying to install mplsadm on
> my redhat linux system. I have gone through the following
> steps:
> 
> 1.      Made the mpls-linux patch to my kernel 2.4.7-10
> 2.      Run 'make menuconfig', and turn on all the required options
>            such as 'MPLS', 'netlink socket', etc.
> 3.      make dep; make clean;
> 
> 4.      make bzImage, which was not successful. The error message
>            looks like this:
> 
>          in directory net/mpls,
> 
>          mpls_tunnel.c: in function mpls_tunnel_init_gen( ),
>          ARPHRD_MPLS_TUNNEL undeclared.
> 
> 
> Your comments and suggestions are highly appreciated.
> 
> Hanxi
> 
> 
> 
> 
> 
> ----------------------------------------------------------
> Hanxi Zhang
> Research Engineer
> Broadband and Optical Networking
> Communications Research Center
> 
> Tel: (613)991-2960 Fax: (613)998-2753
> 3701 Carling Ave, Ottawa, ON K2H 8S2
> ----------------------------------------------------------
> 
> 
> 
> 
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] Problem Installing mplsadm on redhat

[Hanxi Z. <han...@cr...>]

Hi All:

I came across a problem when trying to install mplsadm on
my redhat linux system. I have gone through the following
steps:

1.      Made the mpls-linux patch to my kernel 2.4.7-10
2.      Run 'make menuconfig', and turn on all the required options
           such as 'MPLS', 'netlink socket', etc.
3.      make dep; make clean;

4.      make bzImage, which was not successful. The error message
           looks like this:

         in directory net/mpls,

         mpls_tunnel.c: in function mpls_tunnel_init_gen( ),
         ARPHRD_MPLS_TUNNEL undeclared.


Your comments and suggestions are highly appreciated.

Hanxi





----------------------------------------------------------
Hanxi Zhang
Research Engineer
Broadband and Optical Networking
Communications Research Center

Tel: (613)991-2960 Fax: (613)998-2753
3701 Carling Ave, Ottawa, ON K2H 8S2
----------------------------------------------------------

[mpls-linux-general] downloading from cvs

[<t.k...@we...>]

Hi my name is Thorsten Kauder,
I've got my kernel patched and MPLS-forwarding works 
on a static LSP.
Now I'm trying to make the ldp-portable.
Here's my problem:

I'm in the /usr/src/ldp-portable-0.060/ directory and type make.
In the (I guess) final step (gcc *.a) of the compilation I'm getting a 
segmentation fault. If anyone knows what's the reason for this please let me know.

Thanks in advance

Thorsten
________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! 
Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

Re: [mpls-linux-general] probelm on MPLS testing

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

As Vino and Aditya have said, the setup should work.  We need more info from
you for us to help debug your setup.

A good start is the exact commands you typed in to setup the LSP and FEC
binding.  A dump of your routing table and interface table is also useful.
After you have setup the LSP, dump the contents of /proc/net/mpls_*

Ship all of that info in a e-mail to the list, we should be able to figure
it out from there.

Jim

On Mon, Nov 12, 2001 at 09:42:32PM -0800, Mouli T wrote:
> hello,
> 
>    We have checked /var/log/messages by doing
>    mplsadm -d, but "mpls_out()" was not at all called.
>    
>     Adding of Out,In labels and binding to OUT to FEC
> is  fine. We observed them in /proc/net/mpls_* and in
> /var/log/messages
> 
>     But  traffic is not routing throgh mpls. We have
> by
> putting printk messages in /ipv4/ip_output. Always
> ip route(dst) was calling (dst->output) .Out
> mpls_output was not called.
>     
>    Can any one has got this type of probelm? 
>    Please help us How to solve this?
>   
> With Thanks,
> regards,
> Venu
>        
> 
> 
> 		
> 
> --- "James R. Leu" <jl...@mi...> wrote:
> > On Mon, Nov 12, 2001 at 05:36:29AM -0800, Mouli T
> > wrote:
> > > Hello,
> > > 
> > >    We are trying to test MPLS Forwarding.
> > >    The configuration we are using is
> > 
> > I think your problem is with the FEC binding.  Make
> > sure you have a /32 route
> > to B in As routing table.
> > 
> > Next time, do a 'mplsadm -d' before doing these
> > commands then look at
> > the output from 'dmesg' and look in /proc/net/mpls_*
> > 
> > > On A:
> > >   route add -host B gw B
> > >   mplsadm -A -B -O gen:16:eth0:ipv4:B -f B/32
> > >   mplsadm -A -I gen:17:0
> > > 
> > > On B:
> > >   route add -host A gw A
> > >   mplsadm -A -B -O gen:17:eth0:ipv4:A -f A/32
> > >   mplsadm -A -I gen:16:0
> > > 
> > >     But any trafiic from A <-> B is not using MPLS
> > > LSP.
> > > We think trafic is going throgh ordinary IP
> > routing.
> > > [The function mpls_output() was not at all called]
> > > To watch packets we have used "ethereal" and
> > "tcpdump"
> > > 
> > > Can any body please help, How to route packets to
> > the
> > > MPLS?
> > > 
> > > With Thanks,
> > > regards,
> > > Mouli
> > > 
> > > 
> > > 
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Find a job, post your resume.
> > > http://careers.yahoo.com
> > > 
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > 
> > -- 
> > James R. Leu
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Find the one for you at Yahoo! Personals
> http://personals.yahoo.com

-- 
James R. Leu

[mpls-linux-general] Re: probelm on MPLS testing

[Aditya M T. <ad...@sa...>]

hi mouli,

AFAIK the configuration you are using _should_ work.

Have you checked through proc/net/mpls_* whether the labels and fec
mappings are being added correctly?

regards,
aditya.

-- 
Aditya Thomas,
Software Engineer,
Sasken Communication Technologies Ltd.,
Bangalore,India.
Tel:080-5355501 ext:8249

Howe's Law:
	Everyone has a scheme that will not work.

Re: [mpls-linux-general] probelm on MPLS testing

[Vino T. <jv...@te...>]

Hello,

Try using the latest code/patch namely,
	'mpls-linux 0.996 vs 2.4.13 (BETA)'
it has got counters to see whether packets are passing through the
MPLS path. 
----------------------- Cut from here -------------------------
$ cat /proc/net/mpls_in
40004000 2875/155556/0 gen 16 0 POP DLV
$
------------------------- Till here ----------------------------

BTW, what are the IP addresses (Host/Gw etc) and the MPLS configurations
that you are using.

Regards,
Vino.

On Mon, 12 Nov 2001, Mouli T wrote:

> Hello,
> 
>    We are trying to test MPLS Forwarding.
>    The configuration we are using is
> README.example(given in the mpls forwarding utils)
> 
> Configuration:
> 
> Setup
> -----
>  ---------             ---------
>  |   A   |             |   B   |
>  ---------             ---------
>      |eth0                 |eth0
>      |17.130               |18.114
> -----------------------------------
>          128.104.16.0/22
> 
> Config
> ------
> On A:
>   route add -host B gw B
>   mplsadm -A -B -O gen:16:eth0:ipv4:B -f B/32
>   mplsadm -A -I gen:17:0
> 
> On B:
>   route add -host A gw A
>   mplsadm -A -B -O gen:17:eth0:ipv4:A -f A/32
>   mplsadm -A -I gen:16:0
> 
> Now you need to set a label space on eth0 on both A
> and B.  Watch out!
> if you do this remotely you could saw your leg off!
> 
> On both:
>   mplsadm -L eth0:0
> 
> 
>     But any trafiic from A <-> B is not using MPLS
> LSP.
> We think trafic is going throgh ordinary IP routing.
> [The function mpls_output() was not at all called]
> To watch packets we have used "ethereal" and "tcpdump"
> 
> Can any body please help, How to route packets to the
> MPLS?
> 
> With Thanks,
> regards,
> Mouli
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Find a job, post your resume.
> http://careers.yahoo.com
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 

[mpls-linux-general] I hate GNU mailman somtimes ... (mpls-linux 0.996-2.3.13 patch)

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

I looks like the gziped patch I tried to post last week got thrown away by
mailman (the sourceforge mailing list program).  I'll just release a new
mpls-linux package.  Some how it seems wrong that I have to relase a
new package to get some testing done on some beta code .....

Jim
-- 
James R. Leu

[mpls-linux-general] probelm on MPLS testing

[Mouli T <mou...@ya...>]

Hello,

   We are trying to test MPLS Forwarding.
   The configuration we are using is
README.example(given in the mpls forwarding utils)

Configuration:

Setup
-----
 ---------             ---------
 |   A   |             |   B   |
 ---------             ---------
     |eth0                 |eth0
     |17.130               |18.114
-----------------------------------
         128.104.16.0/22

Config
------
On A:
  route add -host B gw B
  mplsadm -A -B -O gen:16:eth0:ipv4:B -f B/32
  mplsadm -A -I gen:17:0

On B:
  route add -host A gw A
  mplsadm -A -B -O gen:17:eth0:ipv4:A -f A/32
  mplsadm -A -I gen:16:0

Now you need to set a label space on eth0 on both A
and B.  Watch out!
if you do this remotely you could saw your leg off!

On both:
  mplsadm -L eth0:0


    But any trafiic from A <-> B is not using MPLS
LSP.
We think trafic is going throgh ordinary IP routing.
[The function mpls_output() was not at all called]
To watch packets we have used "ethereal" and "tcpdump"

Can any body please help, How to route packets to the
MPLS?

With Thanks,
regards,
Mouli



__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com

[mpls-linux-general] Re: reg : GRE tunnels .

[Steven V. d. B. <sv...@in...>]

Nothing needs to be changed in ip_gre. De/Encapsulation is done using
the virutal interface. Actually it looks like any other ethernet device
(or more correct general device needing shim header) to the mpls code.

On Sun, 2001-11-11 at 22:26, Sandeep Subramaniam wrote:
> Hi,
> 
> Thanx a lot for the information.
> 
> So , will GRE tunnels work with mpls-0.993 itself or only with the latest
> patch supplied by Mr.James Lieu ?
> 
> This is because I was going thru some kernel code after patching 
> the 0.993 version , especially ip_gre.c and
> it doesn't seem to contain MPLS specific code.
> 
> and also the latest patch doesn't seem to have made it to the
> mailing-list.
> 
> Am I right?
> 
> Cheers,
> Sandeep.
> 
> 
> Sandeep Subramaniam
> Graduate Research Assistant
> ITTC, Raymond Nichols Hall,
> University of Kansas
> 
> 
> 
> On 10 Nov 2001, Steven Van den Berghe wrote:
> 
> > I don't have a pointer at hand right now, but from the top of my hat you
> > need to do something like:
> > 
> > endpoint A: 
> > 	ip tunnel add mode gre remote <address B> local <address A>
> > endpoint B: 
> > 	ip tunnel add mode gre remote <address A> local <address B>
> > 
> > This will create a new (virtual) point-to-point interface on both ends,
> > which can be used as any other (ethernet-type) interface. This should
> > work both with our extensions (including RSVP-TE) as the original
> > version of Jim (including LDP).
> > 
> > If you need more help, just let me know. For more information on the
> > "advanced" linux networking stuff (like GRE, policy routing, ...) i
> > would suggest to have a look at 
> > 
> > http://www.linuxdoc.org/HOWTO/Adv-Routing-HOWTO.html
> > 
> > Best regards,
> > Steven
> > 
> > On Sat, 2001-11-10 at 01:27, Sandeep Subramaniam wrote:
> > > Hi,
> > > 
> > > As I had mentioned in my previous email , I need to do MPLS in IP
> > > encapsulation at the ingress and decapsulation at the egress.
> > > 
> > > You suggested that I use GRE tunnels for this purpose .Thanks for the
> > > idea.
> > > 
> > > If I am not wrong, the delivery header shall be IPv4 header and the
> > > payload packet a MPLS pkt with the GRE header in-between.
> > > 
> > > Since I am new to using your MPLS implemenation , can u tell me how to set
> > > up GRE tunnels to do MPLS in IP encapsulation .
> > > 
> > > or can u give me a pointer to some documents explaning that ?
> > > 
> > > Thank you very much
> > > Sandeep. 
> > > 
> > > Sandeep Subramaniam
> > > Graduate Research Assistant
> > > ITTC, Raymond Nichols Hall,
> > > University of Kansas
> > > 
> > > 
> > > 
> > > On Tue, 30 Oct 2001, Steven Van den Berghe wrote:
> > > 
> > > > You can use GRE tunnels to accomplish that. I think the latest
> > > > mpls-linux shouldn't have a problem with that.
> > > > Just create the tunnel over the IP network, and use the created
> > > > pseudo-device as a normal device.
> > > > 
> > > > bye,
> > > > Steven
> > > > 
> > > > Sandeep Subramaniam wrote:
> > > > 
> > > > > Hi,
> > > > >
> > > > > Has anyone tried to implement MPLS in IP encapsulation in the kernel?
> > > > >
> > > > > ie wrapping the MPLS pkt created at the ingress with an IP hdr.
> > > > >
> > > > > Any ideas ?
> > > > >
> > > > > Thanx.
> > > > > Sandeep.
> > > > >
> > > > > Sandeep Subramaniam
> > > > > Graduate Research Assistant
> > > > > ITTC, Raymond Nichols Hall,
> > > > > University of Kansas
> > > > >
> > > > > _______________________________________________
> > > > > mpls-linux-general mailing list
> > > > > mpl...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > 
> > > > --
> > > > Steven Van den Berghe
> > > > ste...@in...
> > > > Workgroup Broadband Communication Networks
> > > > Department Information Technology
> > > > Ghent University - Belgium
> > > > Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> > > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > > > DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
> > > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > > > If engineers built buildings the way programmers wrote
> > > > programs, the first woodpecker to come along would
> > > > destroy civilization.
> > > > 
> > > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > -- 
> > --
> > Steven Van den Berghe
> > ste...@in...
> > Workgroup Broadband Communication Networks
> > Department Information Technology
> > Ghent University - Belgium
> > Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > A computer is like an Old Testament god, with a lot of
> > rules and no mercy. - Joseph Campbell
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > 
> 
> 
-- 
--
Steven Van den Berghe
ste...@in...
Workgroup Broadband Communication Networks
Department Information Technology
Ghent University - Belgium
Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
A computer is like an Old Testament god, with a lot of
rules and no mercy. - Joseph Campbell
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

[mpls-linux-general] reg : GRE tunnels .

[Sandeep S. <san...@it...>]

Hi,

Thanx a lot for the information.

So , will GRE tunnels work with mpls-0.993 itself or only with the latest
patch supplied by Mr.James Lieu ?

This is because I was going thru some kernel code after patching 
the 0.993 version , especially ip_gre.c and
it doesn't seem to contain MPLS specific code.

and also the latest patch doesn't seem to have made it to the
mailing-list.

Am I right?

Cheers,
Sandeep.


Sandeep Subramaniam
Graduate Research Assistant
ITTC, Raymond Nichols Hall,
University of Kansas



On 10 Nov 2001, Steven Van den Berghe wrote:

> I don't have a pointer at hand right now, but from the top of my hat you
> need to do something like:
> 
> endpoint A: 
> 	ip tunnel add mode gre remote <address B> local <address A>
> endpoint B: 
> 	ip tunnel add mode gre remote <address A> local <address B>
> 
> This will create a new (virtual) point-to-point interface on both ends,
> which can be used as any other (ethernet-type) interface. This should
> work both with our extensions (including RSVP-TE) as the original
> version of Jim (including LDP).
> 
> If you need more help, just let me know. For more information on the
> "advanced" linux networking stuff (like GRE, policy routing, ...) i
> would suggest to have a look at 
> 
> http://www.linuxdoc.org/HOWTO/Adv-Routing-HOWTO.html
> 
> Best regards,
> Steven
> 
> On Sat, 2001-11-10 at 01:27, Sandeep Subramaniam wrote:
> > Hi,
> > 
> > As I had mentioned in my previous email , I need to do MPLS in IP
> > encapsulation at the ingress and decapsulation at the egress.
> > 
> > You suggested that I use GRE tunnels for this purpose .Thanks for the
> > idea.
> > 
> > If I am not wrong, the delivery header shall be IPv4 header and the
> > payload packet a MPLS pkt with the GRE header in-between.
> > 
> > Since I am new to using your MPLS implemenation , can u tell me how to set
> > up GRE tunnels to do MPLS in IP encapsulation .
> > 
> > or can u give me a pointer to some documents explaning that ?
> > 
> > Thank you very much
> > Sandeep. 
> > 
> > Sandeep Subramaniam
> > Graduate Research Assistant
> > ITTC, Raymond Nichols Hall,
> > University of Kansas
> > 
> > 
> > 
> > On Tue, 30 Oct 2001, Steven Van den Berghe wrote:
> > 
> > > You can use GRE tunnels to accomplish that. I think the latest
> > > mpls-linux shouldn't have a problem with that.
> > > Just create the tunnel over the IP network, and use the created
> > > pseudo-device as a normal device.
> > > 
> > > bye,
> > > Steven
> > > 
> > > Sandeep Subramaniam wrote:
> > > 
> > > > Hi,
> > > >
> > > > Has anyone tried to implement MPLS in IP encapsulation in the kernel?
> > > >
> > > > ie wrapping the MPLS pkt created at the ingress with an IP hdr.
> > > >
> > > > Any ideas ?
> > > >
> > > > Thanx.
> > > > Sandeep.
> > > >
> > > > Sandeep Subramaniam
> > > > Graduate Research Assistant
> > > > ITTC, Raymond Nichols Hall,
> > > > University of Kansas
> > > >
> > > > _______________________________________________
> > > > mpls-linux-general mailing list
> > > > mpl...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > 
> > > --
> > > Steven Van den Berghe
> > > ste...@in...
> > > Workgroup Broadband Communication Networks
> > > Department Information Technology
> > > Ghent University - Belgium
> > > Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > > DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
> > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > > If engineers built buildings the way programmers wrote
> > > programs, the first woodpecker to come along would
> > > destroy civilization.
> > > 
> > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > > 
> > > 
> > > 
> > 
> > 
> -- 
> --
> Steven Van den Berghe
> ste...@in...
> Workgroup Broadband Communication Networks
> Department Information Technology
> Ghent University - Belgium
> Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> A computer is like an Old Testament god, with a lot of
> rules and no mercy. - Joseph Campbell
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> 

[mpls-linux-general] mpls-linux 0.996 vs 2.4.13 (BETA)

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

(This note was originally for 2.4.10-0.995 but I guess that post never made
it to the list... damn moderator ... hey wait a sec ... :-)

Hey folks,

I know it's been WAY too long since I've released a patch.  It's not like
I'm not add bug fixes or features, I just haven't had a chance to test them
all.  So with that in mind, here is a diff against my development tree
that is untested.  It compiles, it runs, I just haven't regression tested the
the MPLS code.

What's different?

-packet and bytes counters on incoming and outgoing structures
 (results seen in /proc/net/mpls*)
-ttl processing should now be correct
-added yon's bug fix for TCP failures
-updated to 2.4.13

I would apreciate if someone could verify that the TTL processing
works and that the couters are correct. Ofcourse let me know if anything
breaks.

Laters,
Jim
-- 
James R. Leu

Re: [mpls-linux-general] about..... Label stacking in LDP

[Mouli T <mou...@ya...>]

Hello,
     I have gone through both porintg layers(linux and
Zebra).But there also nobody is calling  send_instr().
(in both files linux/ldp_mpls_impl.c and in  
zebra/zldp_mpls_impl.c). 

    


regards,
mouli


--- "James R. Leu" <jl...@mi...> wrote:
> You will not see any direct calls to any of the
> platform specific functions.
> Only calls to the "published" API found in the the
> _impl.h files will be seen
> in the ldp-portable library.  Timers, memmory
> allocation, sockets, mpls
> forwarding, binary tree, tracing etc are all
> implmented in the "porting layer".
> The API in the _impl.h files is implement in the
> porting layer.  The porting
> layers live in linux and zebra directories.
> 
> On Tue, Nov 06, 2001 at 04:23:40AM -0800, Mouli T
> wrote:
> > Hello,
> > 
> >   I am going throgh the code of LDP.
> >   In that i can not able to find where the Label
> > stacking is implemented.
> > 
> >   Basically to implement label stack we need to
> push 
> > a label on a labeled packet by calling 
> >  "send_instr()" function()(in ldp_netlink.c).
> >   But in LDP code nobody is calling this function.
> > 
> >    Please, let me know about how Label stacking is
> 
> > implemented in LDP.
> > 
> > 
> > bye
> > Venu
> > 
> >   
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Find a job, post your resume.
> > http://careers.yahoo.com
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu


__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com