mpls-linux-general

[mpls-linux-general] mplsadm2

[Levisse M. <le...@en...>]

Hi

we installed the rpm version of mplsadm2 and we tried to set up an LSP 
as described below.
The problem is that mplsadm2 does not recognize the -2 option when 
using the mplsadm2 -B -O... command.

Was there any change since that time ?

Michel


> From: James R. Leu <jleu@mi...>
> BETA: mpls-linux 1.127
> 2002-01-29 21:04
> A new beta is availble for download via CVS (tag mpls-linux_1_127).
>
>  Bug fixes
>  Locking
>  Better refence counting
>  Layer 2 Cross Connects (ethernet, port mode)
>
>  NOTE: There are a LOT of changes in this code.  None of these changes
>  are documented.  Look back in the archive to see the previous 
> mpls-linux 1.1
>  annoucements form more info.  (if someone wants to write a CHANGES doc
>  from 1.0 to 1.1 that would be great!!)
>
>  The big change in this version is L2CCs.  To use:
>
>  Ingress LER:
>
>  mplsadm2 -A -O gen:16:eth1:ipv4:11.0.1.2
>  mplsadm2 -B -O key:0x2 -2 eth:eth2:port
>
>  Egress LER:
>
>  mplsadm2 -L eth1:0
>  mplsadm2 -A -I gen:16:0
>  mplsadm2 -B -I gen:16:0 -2 eth:eth3:port
>
>  The result is that all packet arriving on the ingress port (eth2)
>  get shipped across the LSP, and sent egress port (eth3) unchanged.
>
>  Do not enable any L3 protocols on the ingress interface.  Just do an
>  'ifconfig eth2 up'.
>
>  What is this for?  Read draft-martini and you'll see where I'm going.
>
>  Jim
>
>  --
>  James R. Leu 

[mpls-linux-general] mplsadm2

[Kiran K. <kir...@gm...>]

hi,
I am having problems running this command,
mplsadm2 -L eth0:0
it gives me the following error..
MPLSADM mplsadm.c:680:main: Label Space input: eth0:0
MPLSADM mplsadm.c:740:main: Interface: eth0 Label Space: 0
MPLSADM mplsadm.c:753:main: Request or argp is not valid.
Set Labelspace: Invalid argument

this command has been shown using mplsadm in the user guide.
please let us know if there are differences between mplsadm and
mplsadm2 command arguments.
thanks
kiran

Re: [mpls-linux-general] mplsadm2

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

The Layer 2 cross connect code was removed and placed in a seperate project.
If you grab the 'l2cc-kernel' and 'l2cc-linux' directories from my p4 depot
you will get all of the code.  It hasn't been worked on a couple of
months, so it may be a bit stale.

On Tue, Jul 01, 2003 at 02:28:03PM +0200, Levisse Michel wrote:
> Hi 
> 
> we installed the rpm version of mplsadm2 and we tried to set up an LSP 
> as described below. 
> The problem is that mplsadm2 does not recognize the -2 option when 
> using the mplsadm2 -B -O... command. 
> 
> Was there any change since that time ? 
> 
> Michel 
> 
>  
> 
> > From: James R. Leu <jleu@mi...> 
> > BETA: mpls-linux 1.127 
> > 2002-01-29 21:04 
> > A new beta is availble for download via CVS (tag mpls-linux_1_127). 
> >   
> >  Bug fixes 
> >  Locking 
> >  Better refence counting 
> >  Layer 2 Cross Connects (ethernet, port mode) 
> >   
> >  NOTE: There are a LOT of changes in this code.  None of these 
> > changes 
> >  are documented.  Look back in the archive to see the previous 
> > mpls-linux 1.1 
> >  annoucements form more info.  (if someone wants to write a CHANGES 
> > doc 
> >  from 1.0 to 1.1 that would be great!!) 
> >   
> >  The big change in this version is L2CCs.  To use: 
> >   
> >  Ingress LER: 
> >   
> >  mplsadm2 -A -O gen:16:eth1:ipv4:11.0.1.2 
> >  mplsadm2 -B -O key:0x2 -2 eth:eth2:port 
> >   
> >  Egress LER: 
> >   
> >  mplsadm2 -L eth1:0 
> >  mplsadm2 -A -I gen:16:0 
> >  mplsadm2 -B -I gen:16:0 -2 eth:eth3:port 
> >   
> >  The result is that all packet arriving on the ingress port (eth2) 
> >  get shipped across the LSP, and sent egress port (eth3) unchanged. 
> >   
> >  Do not enable any L3 protocols on the ingress interface.  Just do 
> > an  
> >  'ifconfig eth2 up'. 
> >   
> >  What is this for?  Read draft-martini and you'll see where I'm 
> > going. 
> >   
> >  Jim 
> >   
> >  --  
> >  James R. Leu 
> 
> 

-- 
James R. Leu