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

[mpls-linux-general] local address

[yu-xiao j. <yx...@ho...>]

Hi James,

Today's mail reminds me to ask you a question about "local host address"

See your figure:

Example:
             10.0.1.0/24           10.0.2.0/24
    ------- .1         .2 ----- .2            .3 -------
   | LER A |-------------| LSR |----------------| LER B |
    ------- eth1     eth1 ----- eth2        eth1 -------
      lo0                  lo0                    lo0
   1.1.1.1/32           2.2.2.2/32             3.3.3.3/32


     -------------- flow of packets ------------->


In your example, there is a local host address for each router(such as 
1.1.1.1, 2.2.2.2...). I remember one thing: when you do LDP, you need "add 
global <ip for lsrid>" here <ip for lsrid> means "local host address", I am 
not sure whether I am right or not. Now question:

1. Usually lo is "127.0.0.1", Can I assign any ip address for lo? What 's 
the purpose? What's the relation with the ip address of each NIC(such as 
10.0.1.1)?
2. When I do LDP, I must assign different lo ip address for each router, 
because here it is used for identifying the different router. Am I right? 
Please give me help.

Thanks,


jenny,

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

[mpls-linux-general] ldp

[<mi...@en...>]

Hi,

I would like to ask your opinion with regard to some
error messages that I'm getting while running
ldp-linux from the ldp-portable package.

- I'm using the last version of the ldp-portable distro
  (copied through CVS from sf.net);
- I've compiled ldp-linux using :
  CC = gcc # not kgcc, where gcc is version 2.91.66
  Also added -DMPLS_LINUX cflag to  Makefile,
  ( /usr/src/ldp-portable/Makefile );
  I had to remove -Werror flag in order to bypass a
  warning related to some function declarations
  from linux-port/ldp_mpls_impl.c ;
- kernel version is 2.4.5 ;
- kernel was compiled after patching with mpls-linux-0.993
 hostname$ dmesg
  -- snip --
  Initializing RT netlink socket
  ...
  MPLS version 0.993 06/05/2001 jl...@mi...
  MPLS Tunnel interface
  -- snip --

I used a basic test config:

  [ machine A running ldp_linux ] ------ [ machine B running ldp_linux ]

After I start ldp_linux and configure it with "add global" & "add interface",
i'm getting the following error messages:
-- snip --
UDP_DATA
recvfrom: Invalid argument
 [ machine A running ldp_linux ] ------ [ machine B running ldp_linux ]

After I start ldp_linux and add global IP & add interface,


I'm getting the following error messages:
-- snip --
UDP_DATA
recvfrom: Invalid argument
Before header decode: size = 0
UDP_DATA
recvfrom: Invalid argument
Before header decode: size = 0
-- snip --

Then, I set trace 0xffffffff, and get the following :
-- snip --

OUT: Failed while decoding HEADER:-2
OUT: Hello Send fired: entity(4)
OUT: Hello Send: entity(4)
OUT: LPD Header : protocolVersion = 1
OUT:    pduLength = 30
OUT:    lsrAddress = 88c9944c
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***:

-- snip --

I've got the same errors when I used the sample config provided
with ldp-portable ;

Any suggestion will be greatly appreciated,
Thanks and Cheers,

-istvan
ps: I've checked with tcpdump and both machines running ldp_linux
    send out hello discovery msgs on mcasts 224.0.0.2, which
    looks ok to me.

[mpls-linux-general] mpls-linux-0.990 problems

[JK S. <ks...@ve...>]

Hi James,
I have downloaded mpls-linux-0.990 and was trying to setup a simple
mpls working as given in /utils/README.Example
I runned the script as given there. Using Ethereal protocol Analyser I could
not find any MPLS packets when I  ping/ftp.

Also what ever may be the Labeling between the two nodes I was able to ping.

If anybody tried this example and can respond I would appreciate ...

Bye
--jkswamy


--------------------------------------------------------------
Velankani Information Systems Ltd, Bangalore, India

Re: [mpls-linux-general] LSP Tunnel

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

On Mon, Jun 18, 2001 at 11:18:44AM +0500, Saeed Akhter wrote:
> Hi ALL,
> 
> I am wondering if we can create a LSP tunnel with only 1 LSR, even if we 
> can, is it recommendable ? please clarify.

See the last two messages that I sent to the mailing list, Sunil was
trying to accomplish nearly the same thing.

> Thanks
> Saeed
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Re: MPLS-Linux

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

On Tue, Jun 19, 2001 at 01:51:12AM -0000, Sunil Kumar wrote:
> Hi,
> 
> I figured-out my previous problem by myself i.e Static Tunnel creation.
> 
> Can you tell me that for forwarding un-labeled packets do we need to 
> configure something on Linux box ? like instead of gen:16:0 gen:0:0 or 
> anything like that which forwards the un-labeled packets ?

If you create just an incoming label (ie do not bind it to an outgoing label)
it will by default send the unlabeled packet to the IP stack for a route
lookup.

Example:
             10.0.1.0/24           10.0.2.0/24
    ------- .1         .2 ----- .2            .3 -------
   | LER A |-------------| LSR |----------------| LER B |
    ------- eth1     eth1 ----- eth2        eth1 -------
      lo0                  lo0                    lo0
   1.1.1.1/32           2.2.2.2/32             3.3.3.3/32


     -------------- flow of packets ------------->

If you were setting up LER A to be an LER for packets destined to 3.3.3.3/32
You would set it up this way:

Using FEC bindings
------------------
route add -host 3.3.3.3 gw 10.0.1.2
mplsadm -A -B -O gen:3333:eth1:ipv4:10.0.1.2 -f 3.3.3.3/32

Using MPLS tunnel
-----------------

mplsadm -A -B -O gen:3333:eth1:ipv4:10.0.1.2 -T mpls0
ifconfig mpls0 1.1.1.1 pointopoint 3.3.3.3

(remember MPLS tunnel intefaces are unidirectional ... they only do TX no
RX, so you do not have to create one at the egress)


The LSR would be setup as:

mplsadm -L eth1:0
mplsadm -A -B -I gen:3333:0 -O gen:3334:eth2:ipv4:10.0.2.3

The egress LER would be setup as:

mplsadm -L eth1:0
mplsadm -A -I gen:3334:0

When packets arrive at LER B with label 3334 on any interface in labelspace
0 it will pop the label and forward the packet to the IP stack.  The IP
stack will do a route look up, therefore LER B must know how to get to the
destination.

Looking at the info in /proc/net/mpls_* may be helpful to see what is
happening under the hood.

(Remember if you're using 'ping' to verify that it is working, LER B needs
to know how to get back to 1.1.1.1 and if you're going to 'route' the packet
back to 1.1.1.1, LSR will need to know how to get to 1.1.1.1 ;-)

If you're looking for even more info about what is happening under then hood
turn on MPLS kernel debugging 'mplsadm -d' then look at you kernel
log file or use the command 'dmesg' to look at the output.

Jim

> >From: "James R. Leu" <jl...@mi...>
> >Reply-To: jl...@mi...
> >To: Sunil Kumar <sun...@ho...>
> >Subject: Re: MPLS-Linux
> >Date: Mon, 18 Jun 2001 17:00:17 -0500
> >
> >Hello,
> >
> >I suggest joining the mpls-linux mailing list for future questions:
> >
> >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> >On Mon, Jun 18, 2001 at 09:36:42PM -0000, Sunil Kumar wrote:
> > > Hi,
> > >
> > > I want to creat a Manual/Static Tunnel with following topology;
> > >
> > >
> > >   LER A--------------------LSR------------------LER B
> > >   172.16.10.2   172.16.10.1  172.17.10.1     172.17.10.2
> > >                         ETH1   ETH2
> >
> >Your diagram and the commands you've issued don't agree.
> >Describe to me what you're trying to do.
> >
> > > - LER A & B are simulated Routers so we can't configure any mplsadm
> > >   command on those.
> > > - I have configured LSR as under ;
> > >
> > > mplsadm -A -O gen:1024:eth1:ipv4:172.16.10.2
> > >
> > > mplsadm -A -T mpls0
> > >
> > > ifconfig mpls0 172.17.10.2 netmask 255.255.0.0
> > >
> > > mplsadm -B -O gen:1024:eth1 -T mpls0
> > >
> > > route add -net 172.17.0.0/16 mpls0
> > >
> > > - Is there anything I did wrong in above configuration ? please advise 
> >the
> > > correct command script, if the above is not correct.
> > >
> > > - How can I verify the Tunnel ID and the traffic going through it on
> > >   MPLS Linux Router ? please clarify.
> >
> >Tunnel ID?  Are you trying to do some sort of RSVP-TE testing using a
> >box like an Ixia or an Adtech?  If so, it's not going to work.
> >MPLS-Linux is a forwarding plane.  That means it only knows how to
> >"label switch" packets on established LSPs. There are two ways to establish
> >LSPs in the world of MPLS.  Statically or dynamically.  RSVP-TE LDP CR-LDP
> >are all means of doing dynamic LSP establishments (commonly call MPLS
> >signalling protocols).  mplsadm is for setting up static LSPs manually.
> >
> >If you want to talk RSVP-TE or LDP join the mailing list and ask the
> >question there.
> >
> > > Thanks
> > > Sunil
> >
> >--
> >James R. Leu
> 
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Re: MPLS-Linux

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

On Mon, Jun 18, 2001 at 11:08:00PM -0000, Sunil Kumar wrote:
> Hi James,
> 
> Thanks, I have already subscribed to the mpls-linux-general mailing list and 
> trying to get the info from there as well.

I see that, thank you, hopefully others can answer some of your
questions, or provide more background to some of my answers.

> I am trying to establish a Static Tunnel between LER A and LER A without any 
> RSVP-TE or CR-LDP.

Good, I just wanted to make sure we were talking about the same thing.

> I am able to receive MPLS labeled packets on Linux box through Ethereal with 
> correct sequence and TTL ,and my question is , do I need to do some other 
> configurations on Linux box(LSR) to establish a tunnel or multiple tunnel in 
> addition of establishing an LSP ?
> 
> I have configure my MPLS linux box as under;
> 
> 
> mplsadm -v -L eth1:0
> mplsadm -v -L eth2:0
> mplsadm -A -B -I gen:16:0 -O gen:16:eth1:ipv4:172.16.10.2
> mplsadm -A -B -I gen:17:0 -O hen:17:eth2:ipv4:172.17.10.2
>
> I believe above will establish an LSP between LER A and LER B.

You got it!  Actually 2 LSPs are created, one from A to B (17) and
one from B to A (16) ;-)

> Or what would be the mplsadm commands for creating a tunnel or multiple 
> tunnels between an LERA and LERA through one LSR or multiple LSRs ?

From the perspective of the LSR a 'tunnel' and an LSP are the same thing.
BTW 'tunnel' is sort of a mis-nomer, I think it was first used by CISCO
to explain how MPLS traffic engineering worked and it made sense to
use the term 'tunnel' because that is how a CISCO router represent a traffic
engineered LSP to the user (via tunnel interfaces).  I added the MPLS tunnel
to provide an easy to use method to do LSP hierarchy and to just cover
all of the basics.

> Is there any good source to learn the mplsadm command scripts ? as even on 
> Sourceforge the material is not sufficient enough for a new comer to 
> understand and configure MPLS-Linux properly.

The best I have to offer is the README's in the doc directory or the MPLS
linux package.  Of course I will always accept documents for addition to
the package ;-)

Jim

> >From: "James R. Leu" <jl...@mi...>
> >Reply-To: jl...@mi...
> >To: Sunil Kumar <sun...@ho...>
> >Subject: Re: MPLS-Linux
> >Date: Mon, 18 Jun 2001 17:00:17 -0500
> >
> >Hello,
> >
> >I suggest joining the mpls-linux mailing list for future questions:
> >
> >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> >On Mon, Jun 18, 2001 at 09:36:42PM -0000, Sunil Kumar wrote:
> > > Hi,
> > >
> > > I want to creat a Manual/Static Tunnel with following topology;
> > >
> > >
> > >   LER A--------------------LSR------------------LER B
> > >   172.16.10.2   172.16.10.1  172.17.10.1     172.17.10.2
> > >                         ETH1   ETH2
> >
> >Your diagram and the commands you've issued don't agree.
> >Describe to me what you're trying to do.
> >
> > > - LER A & B are simulated Routers so we can't configure any mplsadm
> > >   command on those.
> > > - I have configured LSR as under ;
> > >
> > > mplsadm -A -O gen:1024:eth1:ipv4:172.16.10.2
> > >
> > > mplsadm -A -T mpls0
> > >
> > > ifconfig mpls0 172.17.10.2 netmask 255.255.0.0
> > >
> > > mplsadm -B -O gen:1024:eth1 -T mpls0
> > >
> > > route add -net 172.17.0.0/16 mpls0
> > >
> > > - Is there anything I did wrong in above configuration ? please advise 
> >the
> > > correct command script, if the above is not correct.
> > >
> > > - How can I verify the Tunnel ID and the traffic going through it on
> > >   MPLS Linux Router ? please clarify.
> >
> >Tunnel ID?  Are you trying to do some sort of RSVP-TE testing using a
> >box like an Ixia or an Adtech?  If so, it's not going to work.
> >MPLS-Linux is a forwarding plane.  That means it only knows how to
> >"label switch" packets on established LSPs. There are two ways to establish
> >LSPs in the world of MPLS.  Statically or dynamically.  RSVP-TE LDP CR-LDP
> >are all means of doing dynamic LSP establishments (commonly call MPLS
> >signalling protocols).  mplsadm is for setting up static LSPs manually.
> >
> >If you want to talk RSVP-TE or LDP join the mailing list and ask the
> >question there.
> >
> > > Thanks
> > > Sunil
> >
> >--
> >James R. Leu
> 
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] Re: MPLS-Linux

[Sunil K. <sun...@ho...>]

Hi,

I figured-out my previous problem by myself i.e Static Tunnel creation.

Can you tell me that for forwarding un-labeled packets do we need to 
configure something on Linux box ? like instead of gen:16:0 gen:0:0 or 
anything like that which forwards the un-labeled packets ?

Please clarify.

Thanks
Sunil








>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: Sunil Kumar <sun...@ho...>
>Subject: Re: MPLS-Linux
>Date: Mon, 18 Jun 2001 17:00:17 -0500
>
>Hello,
>
>I suggest joining the mpls-linux mailing list for future questions:
>
>http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>On Mon, Jun 18, 2001 at 09:36:42PM -0000, Sunil Kumar wrote:
> > Hi,
> >
> > I want to creat a Manual/Static Tunnel with following topology;
> >
> >
> >   LER A--------------------LSR------------------LER B
> >   172.16.10.2   172.16.10.1  172.17.10.1     172.17.10.2
> >                         ETH1   ETH2
>
>Your diagram and the commands you've issued don't agree.
>Describe to me what you're trying to do.
>
> > - LER A & B are simulated Routers so we can't configure any mplsadm
> >   command on those.
> > - I have configured LSR as under ;
> >
> > mplsadm -A -O gen:1024:eth1:ipv4:172.16.10.2
> >
> > mplsadm -A -T mpls0
> >
> > ifconfig mpls0 172.17.10.2 netmask 255.255.0.0
> >
> > mplsadm -B -O gen:1024:eth1 -T mpls0
> >
> > route add -net 172.17.0.0/16 mpls0
> >
> > - Is there anything I did wrong in above configuration ? please advise 
>the
> > correct command script, if the above is not correct.
> >
> > - How can I verify the Tunnel ID and the traffic going through it on
> >   MPLS Linux Router ? please clarify.
>
>Tunnel ID?  Are you trying to do some sort of RSVP-TE testing using a
>box like an Ixia or an Adtech?  If so, it's not going to work.
>MPLS-Linux is a forwarding plane.  That means it only knows how to
>"label switch" packets on established LSPs. There are two ways to establish
>LSPs in the world of MPLS.  Statically or dynamically.  RSVP-TE LDP CR-LDP
>are all means of doing dynamic LSP establishments (commonly call MPLS
>signalling protocols).  mplsadm is for setting up static LSPs manually.
>
>If you want to talk RSVP-TE or LDP join the mailing list and ask the
>question there.
>
> > Thanks
> > Sunil
>
>--
>James R. Leu

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[mpls-linux-general] Re: MPLS-Linux

[Sunil K. <sun...@ho...>]

Hi James,

Thanks, I have already subscribed to the mpls-linux-general mailing list and 
trying to get the info from there as well.

I am trying to establish a Static Tunnel between LER A and LER A without any 
RSVP-TE or CR-LDP.

I am able to receive MPLS labeled packets on Linux box through Ethereal with 
correct sequence and TTL ,and my question is , do I need to do some other 
configurations on LIunx box(LSR) to establish a tunnel or multiple tunnel in 
addition of establishing an LSP ?

I have configure my MPLS linux box as under;


mplsadm -v -L eth1:0
mplsadm -v -L eth2:0
mplsadm -A -B -I gen:16:0 -O gen:16:eth1:ipv4:172.16.10.2
mplsadm -A -B -I gen:17:0 -O hen:17:eth2:ipv4:172.17.10.2

I believe above will establish an LSP between LER A and LER B.

Or what would be the mplsadm commands for creating a tunnel or multiple 
tunnels between an LERA and LERA through one LSR or multiple LSRs ?

Is there any good source to learn the mplsadm command scripts ? as even on 
Sourceforge the material is not sufficient enough for a new comer to 
understand and configure MPLS-Linux properly.

Please respond.I will appreciate your help.

Thanks
Sunil



>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: Sunil Kumar <sun...@ho...>
>Subject: Re: MPLS-Linux
>Date: Mon, 18 Jun 2001 17:00:17 -0500
>
>Hello,
>
>I suggest joining the mpls-linux mailing list for future questions:
>
>http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>On Mon, Jun 18, 2001 at 09:36:42PM -0000, Sunil Kumar wrote:
> > Hi,
> >
> > I want to creat a Manual/Static Tunnel with following topology;
> >
> >
> >   LER A--------------------LSR------------------LER B
> >   172.16.10.2   172.16.10.1  172.17.10.1     172.17.10.2
> >                         ETH1   ETH2
>
>Your diagram and the commands you've issued don't agree.
>Describe to me what you're trying to do.
>
> > - LER A & B are simulated Routers so we can't configure any mplsadm
> >   command on those.
> > - I have configured LSR as under ;
> >
> > mplsadm -A -O gen:1024:eth1:ipv4:172.16.10.2
> >
> > mplsadm -A -T mpls0
> >
> > ifconfig mpls0 172.17.10.2 netmask 255.255.0.0
> >
> > mplsadm -B -O gen:1024:eth1 -T mpls0
> >
> > route add -net 172.17.0.0/16 mpls0
> >
> > - Is there anything I did wrong in above configuration ? please advise 
>the
> > correct command script, if the above is not correct.
> >
> > - How can I verify the Tunnel ID and the traffic going through it on
> >   MPLS Linux Router ? please clarify.
>
>Tunnel ID?  Are you trying to do some sort of RSVP-TE testing using a
>box like an Ixia or an Adtech?  If so, it's not going to work.
>MPLS-Linux is a forwarding plane.  That means it only knows how to
>"label switch" packets on established LSPs. There are two ways to establish
>LSPs in the world of MPLS.  Statically or dynamically.  RSVP-TE LDP CR-LDP
>are all means of doing dynamic LSP establishments (commonly call MPLS
>signalling protocols).  mplsadm is for setting up static LSPs manually.
>
>If you want to talk RSVP-TE or LDP join the mailing list and ask the
>question there.
>
> > Thanks
> > Sunil
>
>--
>James R. Leu

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[mpls-linux-general] MPLS-Linux

[Sunil K. <sun...@ho...>]

Hi,

I want to creat a Manual/Static Tunnel with following topology;


  LER A--------------------LSR------------------LER B
  172.16.10.2   172.16.10.1  172.17.10.1     172.17.10.2
                        ETH1   ETH2


- LER A & B are simulated Routers so we can't configure any mplsadm
  command on those.
- I have configured LSR as under ;


mplsadm -A -O gen:1024:eth1:ipv4:172.16.10.2

mplsadm -A -T mpls0

ifconfig mpls0 172.17.10.2 netmask 255.255.0.0

mplsadm -B -O gen:1024:eth1 -T mpls0

route add -net 172.17.0.0/16 mpls0

- Is there anything I did wrong in above configuration ? please advise the 
correct command script, if the above is not correct.

- How can I verify the Tunnel ID and the traffic going through it on
  MPLS Linux Router ? please clarify.



Thanks
Sunil




_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[mpls-linux-general] LSP Tunnel

[Saeed A. <she...@ho...>]

Hi ALL,

I am wondering if we can create a LSP tunnel with only 1 LSR, even if we 
can, is it recommendable ? please clarify.

Thanks
Saeed
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

[mpls-linux-general] MPLS-Linux test cases

[Sunil K. <sun...@ho...>]

Hi All,

Did anybody conducted mpls-linux test cases with some testing 
device/Generators like Ixia,SmartBit etc.? If yes, then please send me those 
test cases.

I am particularly looking for MPLS & RSVP Test suites.

I will appreciate if anybody can provide me those test cases.

Thanks
Sunil


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[mpls-linux-general] 3C990 Linux drivers for kernel 2.4.x

[Lijun Q. <lj...@rc...>]

Hi all,

Did anybody try the 3C990 ethernet card with drivers for kernel 2.4.x?

thanks
Lijun

[mpls-linux-general] Can MPLS project be used in RTLinux (Real time Linux)?

[yu-xiao j. <yx...@ho...>]

Hi James,

We have done IP diffserv in our testbed. We want to start doing MPLS 
diffserv. I just wonder whether current MPLS project support Real Time 
Linux. I mean if I install RTLinux on my router, can I use the same mplsadm 
and ldp package.

Does somebody do the same research work? Any help will be apprteciated.


regards,


jenny Jia


>From: mpl...@li...
>Reply-To: mpl...@li...
>To: mpl...@li...
>Subject: mpls-linux-general digest, Vol 1 #88 - 5 msgs
>Date: Tue, 12 Jun 2001 12:03:56 -0700
>
>Send mpls-linux-general mailing list submissions to
>	mpl...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>or, via email, send a message with subject or body 'help' to
>	mpl...@li...
>
>You can reach the person managing the list at
>	mpl...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of mpls-linux-general digest..."
>
>
>Today's Topics:
>
>    1. Re: MPLS linux configuration (James R. Leu)
>    2. Re: MPLS/linux (James R. Leu)
>    3. Re: MPLS/linux (James R. Leu)
>    4. database (nomit kalidhar)
>    5. Re: database (James R. Leu)
>
>--__--__--
>
>Message: 1
>Date: Mon, 11 Jun 2001 14:17:54 -0500
>From: "James R. Leu" <jl...@mi...>
>To: Sunil Kumar <sun...@ho...>
>Cc: mpl...@li..., mpl...@mp...
>Reply-To: jl...@mi...
>Organization: none
>Subject: [mpls-linux-general] Re: MPLS linux configuration
>
>On Mon, Jun 11, 2001 at 04:49:16PM -0000, Sunil Kumar wrote:
> > Hi All,
> >
> > Can anybody just verify or correct my following configurations;
> >
> >
> >
> >   Ingress-----LSR-------Egress
> >           eth1   eth2
> >
> > I applied following commands ;
> >
> > 1- mplsadm -L eth1:0
> >    mplsadm -A -B -I gen:16:0 -o gen:16:eth1:ipv4:192.168.200.3(whereas
> >    192.168.200.3 is the Next hop-Egress- IP address.
> >
> > 2- Then , I applied;
> >
> >    mplsadm -L eth2:0
> >    mplsadm -A -B -I gen:18:0 -o gen:18:ipv4:192.168.100.3(whereas
> >    192.168.100.3 is the Ingress IP address.
> >
> >
> > My main intention is to set-up an LSP between Ingress and Egress through
> > LSR.
> >
> > Please let me have the response at earliest.
>
>You got it right.  Do a 'mplsadm -d' to toggle kernel debugging of MPLS.
>Use 'dmesg' to see the debugging output.  You will see lots of messages
>from the MPLS stack when you start to send traffic.
>
>Jim
>--
>James R. Leu
>
>
>--__--__--
>
>Message: 2
>Date: Mon, 11 Jun 2001 14:37:11 -0500
>From: "James R. Leu" <jl...@mi...>
>To: SAAD SHEIKH <sa...@ho...>
>Cc: mpl...@li..., mpl...@mp...
>Subject: Re: [mpls-linux-general] MPLS/linux
>Reply-To: jl...@mi...
>Organization: none
>
>On Sat, Jun 09, 2001 at 02:56:50AM -0000, SAAD SHEIKH wrote:
> > Hi Everybody,
> >
> > I would appreciate if anybody can guide me through following:
> >
> > I am a new comer to MPLS, and want to start with following topology;
> >
> >
> > Ingress----------------------LSR-----------------Egress
> > 192.168.100.3            eth1   eth2             192.168.200.3
> >
> >                  192.168.100.1  192.168.200.1
> >
> >
> > I have configured the LSR as under ;
> >
> > mplsadm -v -L eth1:0
> > mplsadm -v -L eth2:0
> >
> > mplsadm -A -B -I gen:16:0 -o gen:16:eth1:ipv4:192.168.100.3
> > mplsadm -A -B -I gen:16:0 -o gen:16:eth2:ipv4:192.168.200.3
> >
> > Please see where I am wrong and kindly advise me with the correct 
>commands
> > in detail while realizing my new entrance into MPLS technology.
>
>The above configure will only label switch packets at the LSR, you do not 
>have
>anything configure to add labels or remove labels from the packets at the
>ingress and egress:
>
>Ingress:
>
>-terminate LSP 16
>mplsadm -v -L eth1:0
>mplsadm -A -I gen:16:0
>
>-orginate LSP 16
>route add -net 192.168.200.0/24 gw 192.168.100.1
>mplsadm -A -B -O gen:16:eth1:ipv4:192.168.100.1 -f 192.168.200.0/24
>
>Egress:
>
>-terminate LSP 16
>mplsadm -v -L eth1:0
>mplsadm -A -I gen:16:0
>
>-orginate LSP 16
>route add -net 192.168.100.0/24 gw 192.168.200.1
>mplsadm -A -B -O gen:16:eth1:ipv4:192.168.200.1 -f 192.168.100.0/24
>
>Jim
>--
>James R. Leu
>
>
>--__--__--
>
>Message: 3
>Date: Mon, 11 Jun 2001 15:07:14 -0500
>From: "James R. Leu" <jl...@mi...>
>To: SAAD SHEIKH <sa...@ho...>
>Cc: mpl...@li...
>Subject: Re: [mpls-linux-general] MPLS/linux
>Reply-To: jl...@mi...
>Organization: none
>
>On Mon, Jun 11, 2001 at 07:59:49PM -0000, SAAD SHEIKH wrote:
> > Thanks Jim,
> >
> > In fact I am using simulated Ingress and Egress Routers which are in 
>fact
> > two ports of a testing Device so I just set it up( I am sure I set it up
> > properly)and I need to configure only LSR so that Ingress(Port 1 of 
>testing
> > device) can establish an LSP with Egress(Port 2 of testing device).
> >
> > I only need to configure LSR(linux Router) so that LSP can work 
>fine.Please
> > guide me in this perspective when I have to configure only and LSR same 
>as
> > the previous scenerio.
> >
>
><snip>
>
> > > > Ingress----------------------LSR-----------------Egress
> > > > 192.168.100.3            eth1   eth2             192.168.200.3
> > > >
> > > >                  192.168.100.1  192.168.200.1
> > > >
> > > >
> > > > I have configured the LSR as under ;
> > > >
> > > > mplsadm -v -L eth1:0
> > > > mplsadm -v -L eth2:0
> > > >
>
>You're telling incoming label 16 (in labelspace 0) to go too two
>different places, that won't work.  Try this instead:
>
>
>mplsadm -v -L eth1:0
>mplsadm -v -L eth2:0
>mplsadm -A -B -I gen:16:0 -o gen:16:eth1:ipv4:192.168.100.3
>mplsadm -A -B -I gen:17:0 -o gen:17:eth2:ipv4:192.168.200.3
>
>When you start forwarding traffic, do a 'mplsadm -d' and use dmesg
>to see the debug messages from the kernel.  Doing an other 'mplsadm -d'
>will turn off the messages.
>
>Jim
>--
>James R. Leu
>
>
>--__--__--
>
>Message: 4
>Date: Tue, 12 Jun 2001 15:02:35 +0530
>From: "nomit kalidhar" <nom...@in...>
>To: <mpl...@li...>
>Subject: [mpls-linux-general] database
>
>Hello
>
>I used some of the commands of "mplsadm" to add modifier, bind modifier
>etc.
>how can i see the effect of these commands. Is there something similar
>as the "route" or netstat command in MPLS Linux
>
>TIA
>
>Nomit
>
>
>--__--__--
>
>Message: 5
>Date: Tue, 12 Jun 2001 08:06:08 -0500
>From: "James R. Leu" <jl...@mi...>
>To: nomit kalidhar <nom...@in...>
>Cc: mpl...@li...
>Subject: Re: [mpls-linux-general] database
>Reply-To: jl...@mi...
>Organization: none
>
>On Tue, Jun 12, 2001 at 03:02:35PM +0530, nomit kalidhar wrote:
> > Hello
> >
> > I used some of the commands of "mplsadm" to add modifier, bind modifier
> > etc.
> > how can i see the effect of these commands. Is there something similar
> > as the "route" or netstat command in MPLS Linux
>
>As it says in the README in the patches directory, you can look at some
>files in the /proc filesystem.  Specifically /proc/net/mpls_*
>
>Jim
>
> > TIA
> >
> > Nomit
> >
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>--
>James R. Leu
>
>
>
>--__--__--
>
>_______________________________________________
>mpls-linux-general mailing list
>mpl...@li...
>http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>
>End of mpls-linux-general Digest

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Re: [mpls-linux-general] database

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

On Tue, Jun 12, 2001 at 03:02:35PM +0530, nomit kalidhar wrote:
> Hello
> 
> I used some of the commands of "mplsadm" to add modifier, bind modifier
> etc.
> how can i see the effect of these commands. Is there something similar
> as the "route" or netstat command in MPLS Linux

As it says in the README in the patches directory, you can look at some
files in the /proc filesystem.  Specifically /proc/net/mpls_*

Jim

> TIA
> 
> Nomit
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] database

[nomit k. <nom...@in...>]

Hello

I used some of the commands of "mplsadm" to add modifier, bind modifier
etc.
how can i see the effect of these commands. Is there something similar
as the "route" or netstat command in MPLS Linux

TIA

Nomit

Re: [mpls-linux-general] MPLS/linux

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

On Mon, Jun 11, 2001 at 07:59:49PM -0000, SAAD SHEIKH wrote:
> Thanks Jim,
> 
> In fact I am using simulated Ingress and Egress Routers which are in fact 
> two ports of a testing Device so I just set it up( I am sure I set it up 
> properly)and I need to configure only LSR so that Ingress(Port 1 of testing 
> device) can establish an LSP with Egress(Port 2 of testing device).
> 
> I only need to configure LSR(linux Router) so that LSP can work fine.Please 
> guide me in this perspective when I have to configure only and LSR same as 
> the previous scenerio.
> 

<snip>

> > > Ingress----------------------LSR-----------------Egress
> > > 192.168.100.3            eth1   eth2             192.168.200.3
> > >
> > >                  192.168.100.1  192.168.200.1
> > >
> > >
> > > I have configured the LSR as under ;
> > >
> > > mplsadm -v -L eth1:0
> > > mplsadm -v -L eth2:0
> > >

You're telling incoming label 16 (in labelspace 0) to go too two
different places, that won't work.  Try this instead:


mplsadm -v -L eth1:0
mplsadm -v -L eth2:0
mplsadm -A -B -I gen:16:0 -o gen:16:eth1:ipv4:192.168.100.3
mplsadm -A -B -I gen:17:0 -o gen:17:eth2:ipv4:192.168.200.3

When you start forwarding traffic, do a 'mplsadm -d' and use dmesg
to see the debug messages from the kernel.  Doing an other 'mplsadm -d'
will turn off the messages.

Jim
-- 
James R. Leu

Re: [mpls-linux-general] MPLS/linux

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

On Sat, Jun 09, 2001 at 02:56:50AM -0000, SAAD SHEIKH wrote:
> Hi Everybody,
> 
> I would appreciate if anybody can guide me through following:
> 
> I am a new comer to MPLS, and want to start with following topology;
> 
> 
> Ingress----------------------LSR-----------------Egress
> 192.168.100.3            eth1   eth2             192.168.200.3
> 
>                  192.168.100.1  192.168.200.1
> 
> 
> I have configured the LSR as under ;
> 
> mplsadm -v -L eth1:0
> mplsadm -v -L eth2:0
> 
> mplsadm -A -B -I gen:16:0 -o gen:16:eth1:ipv4:192.168.100.3
> mplsadm -A -B -I gen:16:0 -o gen:16:eth2:ipv4:192.168.200.3
> 
> Please see where I am wrong and kindly advise me with the correct commands 
> in detail while realizing my new entrance into MPLS technology.

The above configure will only label switch packets at the LSR, you do not have
anything configure to add labels or remove labels from the packets at the
ingress and egress:

Ingress:

-terminate LSP 16
mplsadm -v -L eth1:0
mplsadm -A -I gen:16:0

-orginate LSP 16
route add -net 192.168.200.0/24 gw 192.168.100.1
mplsadm -A -B -O gen:16:eth1:ipv4:192.168.100.1 -f 192.168.200.0/24

Egress:

-terminate LSP 16
mplsadm -v -L eth1:0
mplsadm -A -I gen:16:0

-orginate LSP 16
route add -net 192.168.100.0/24 gw 192.168.200.1
mplsadm -A -B -O gen:16:eth1:ipv4:192.168.200.1 -f 192.168.100.0/24

Jim
-- 
James R. Leu

[mpls-linux-general] Re: MPLS linux configuration

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

On Mon, Jun 11, 2001 at 04:49:16PM -0000, Sunil Kumar wrote:
> Hi All,
> 
> Can anybody just verify or correct my following configurations;
> 
> 
> 
>   Ingress-----LSR-------Egress
>           eth1   eth2
> 
> I applied following commands ;
> 
> 1- mplsadm -L eth1:0
>    mplsadm -A -B -I gen:16:0 -o gen:16:eth1:ipv4:192.168.200.3(whereas
>    192.168.200.3 is the Next hop-Egress- IP address.
> 
> 2- Then , I applied;
> 
>    mplsadm -L eth2:0
>    mplsadm -A -B -I gen:18:0 -o gen:18:ipv4:192.168.100.3(whereas
>    192.168.100.3 is the Ingress IP address.
> 
> 
> My main intention is to set-up an LSP between Ingress and Egress through 
> LSR.
> 
> Please let me have the response at earliest.

You got it right.  Do a 'mplsadm -d' to toggle kernel debugging of MPLS.
Use 'dmesg' to see the debugging output.  You will see lots of messages
from the MPLS stack when you start to send traffic.

Jim
-- 
James R. Leu

[mpls-linux-general] MPLS linux configuration

[Sunil K. <sun...@ho...>]

Hi All,

Can anybody just verify or correct my following configurations;



  Ingress-----LSR-------Egress
          eth1   eth2

I applied following commands ;

1- mplsadm -L eth1:0
   mplsadm -A -B -I gen:16:0 -o gen:16:eth1:ipv4:192.168.200.3(whereas
   192.168.200.3 is the Next hop-Egress- IP address.

2- Then , I applied;

   mplsadm -L eth2:0
   mplsadm -A -B -I gen:18:0 -o gen:18:ipv4:192.168.100.3(whereas
   192.168.100.3 is the Ingress IP address.


My main intention is to set-up an LSP between Ingress and Egress through 
LSR.

Please let me have the response at earliest.

Thanks
Sunil


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[mpls-linux-general] MPLS Linux configuration

[Sunil K. <sun...@ho...>]

Hello Everybody,

I will appreciate if anybody can respond to following querries :

1- Is there any training event scheduled in San Jose or San Francisco on
MPLS Technology during 2-3 week of June'01 ? please let me know about it.I 
am more interested in MPLS-Linux.


2- Can anybody tell me how to setup MPLS label receiving and forwarding  on 
an LSR ? In fact I need to know the exact mplsadm commands to enable LSR to 
receive MPLS labels/packets from Ingress and then forward it to an Egress 
Router and Egress Router can also forward it back to Ingress Router.

3- You can say I want to establish an LSP between Ingress and Egress through 
a LSR.

I would appreciate if I can have a very comprehensive sort of reply with
mplsadm configuration scripts.

I have mpls installed on my Linux kernel 2.4.1.

Thanks in Advance
Sunil
>_________________________________________________________________
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

Re: [mpls-linux-general] IPv6

[Luis F B. <ha...@in...>]

On Sun, 10 Jun 2001, J=F6rn Seger wrote:

JS>Sounds interesting, but how do you solve label stacking? This might
JS>be one of the biggest advantage of mpls.

By using IPv6 extension headers. It's not the same thing as having
concatenated labels, which eases the processing at the router. But the
router would have to open the packet anyway to swap labels, so...

--=20
Luis F Balbinot
ha...@in...
http://cscience.org/~hades/

Re: [mpls-linux-general] IPv6

[Jing S. <js...@ca...>]

>

And, How the lable switching engine  and LIB built in linux?

regards

James Shen


>
> > My research team is doing some experiments with what we called "MPLS over
> > IPv6" by using IPv6 header fields (flow label, etc) to store MPLS label
> > information so that we can remove the MPLS labels and reduce the overhead,
> > fragmentation issues, etc. It's not a new idea. We are modifying NS-2 to
> > simulate that, but we'd like to see the real thing working, so we found
> > out that this implementation was available.
> >
>
> Sounds interesting, but how do you solve label stacking? This might be one of
> the biggest advantage of mpls.
>
> best regards - Jn
>
> _

Re: [mpls-linux-general] IPv6

[<j....@gm...>]

Am Samstag,  9. Juni 2001 19:36 schrieb Luis F Balbinot:
> Hello all,
>
> Is there anyone using IPv6 with this MPLS implementation?
>
> My research team is doing some experiments with what we called "MPLS over
> IPv6" by using IPv6 header fields (flow label, etc) to store MPLS label
> information so that we can remove the MPLS labels and reduce the overhead,
> fragmentation issues, etc. It's not a new idea. We are modifying NS-2 to
> simulate that, but we'd like to see the real thing working, so we found
> out that this implementation was available.
>

Sounds interesting, but how do you solve label stacking? This might be one of 
the biggest advantage of mpls.

best regards - Jörn

[mpls-linux-general] Re: [ippm] Measure the delay jitter of video stream over MPLS network?

[Jizhong (J. W. <ji...@cs...>]

Hi James,

What's the transport protocol you used? If you use RTP, the 'time stamp'
may be helpful.

Jim

Jing Shen wrote:

> Hi:
>
> Execuse me for my stupid question, but I really need help
> on this question.
>
> I've just setup a little test bed with MPLS & QoS enabled.
> I want to measure the effect of QoS enabled MPLS channel
> on video streams. I hope the test should be as simple as possible.
>
> I've download a little tool named mpeg_video
> which is a mpeg-1 decoder. I place the mpeg-1 files
> on one end of the testbed(linux)  and mpeg-1 decoder on the other
> end ( Solaris box). The decoder use NFS to fetch the content to play.
> After reading the source code of the mpeg-1 decoder I find I
> can just record the start and stop time of each frame, while I want to
> measure the delay and delay jitter of each stream. And, I don't know if
> there
> is a free tool  can be used to generate a  graph of jitter-frame
> relationship
> from raw data.
>
> Is there any person would like to do me a favor on this question?
>
> Thanks a lot .
>
> Regards
>
> James Shen
>
> _______________________________________________
> ippm mailing list
> ip...@ad...
> http://mailhost.advanced.org/mailman/listinfo/ippm

--
=================================================================
Jim Wu                                 ji...@cs...
School of Computer Sci. & Eng.         FAX:   +61 2 9385 5995
The University of New South Wales      Tel:   +61 2 9385 4358
UNSW SYDNEY, NSW 2052                  http://www.cse.unsw.edu.au/~jimw
Australia
=================================================================

[mpls-linux-general] IPv6

[Luis F B. <ha...@in...>]

Hello all,

Is there anyone using IPv6 with this MPLS implementation?

My research team is doing some experiments with what we called "MPLS over
IPv6" by using IPv6 header fields (flow label, etc) to store MPLS label
information so that we can remove the MPLS labels and reduce the overhead,
fragmentation issues, etc. It's not a new idea. We are modifying NS-2 to
simulate that, but we'd like to see the real thing working, so we found
out that this implementation was available.

Please let me know if you had "good" experiences with IPv6 and this
MPLS implementation ;-)

Best Regards,
Luis F Balbinot
ha...@in...
Federal University of Rio Grande do Sul
Computer Science Department