mpls-linux-general

[mpls-linux-general] In label instructions + misc questions

[ncc49a <nc...@si...>]

Hi James,

   In response to my earlier mail, I did something like this:

mplsadm -v -I gen:123:0 -i exp2tc:1:2:3:4:peek:dlv:0x800

    There was still the earlier error and also the error that 0x800 was =
not recognised, though mpls_in reflects that the instruction had been =
executed. Could u provide a simple example to correctly implement the =
above?

    Also, for outgoing labels when I execute 2 commands in turn: ds2exp =
and exp2tc, only the results of the later command, that is exp2tc are =
reflected in mpls_in. But shouldn't they both be relevant i.e for an =
outgoing pkt, its DSCP is converted to its EXP for downstream LSRs to =
make reference to. And on its way out of the interface, this exp is then =
converted to a tc_index for "tc" to police? Or am I wrong somewhere?

    Thanks a lot!

Regards,

Paul=20

Re: [mpls-linux-general] In label instructions + misc questions

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

On Tue, Feb 19, 2002 at 07:08:29AM +0800, ncc49a wrote:
> Hi James,
> 
>    In response to my earlier mail, I did something like this:
> 
> mplsadm -v -I gen:123:0 -i exp2tc:1:2:3:4:peek:dlv:0x800

mplsadm -v -I gen:123:0 -i exp2tc:1:2:3:4:peek

_should_ work ... but (see below)

>     There was still the earlier error and also the error that 0x800 was not recognised, though mpls_in reflects that the instruction had been executed. Could u provide a simple example to correctly implement the above?
> 
>     Also, for outgoing labels when I execute 2 commands in turn: ds2exp and exp2tc, only the results of the later command, that is exp2tc are reflected in mpls_in. But shouldn't they both be relevant i.e for an outgoing pkt, its DSCP is converted to its EXP for downstream LSRs to make reference to. And on its way out of the interface, this exp is then converted to a tc_index for "tc" to police? Or am I wrong somewhere?

I'm guessing that mplsadm is not parsing any of the 'array' based instructions
correctly.  I'll look into it.

Jim


> 
>     Thanks a lot!
> 
> Regards,
> 
> Paul 

-- 
James R. Leu

Re: [mpls-linux-general] In label instructions + misc questions

[Stefano A. <avi...@li...>]

Hi Paul, James and all

On Tuesday 19 February 2002 00:08, ncc49a wrote:
> Hi James,
>
>    In response to my earlier mail, I did something like this:
>
> mplsadm -v -I gen:123:0 -i exp2tc:1:2:3:4:peek:dlv:0x800
>
>     There was still the earlier error and also the error that 0x800 was not
> recognised, though mpls_in reflects that the instruction had been executed.
> Could u provide a simple example to correctly implement the above?
>
>     Also, for outgoing labels when I execute 2 commands in turn: ds2exp and
> exp2tc, only the results of the later command, that is exp2tc are reflected
> in mpls_in. But shouldn't they both be relevant i.e for an outgoing pkt,
> its DSCP is converted to its EXP for downstream LSRs to make reference to.
> And on its way out of the interface, this exp is then converted to a
> tc_index for "tc" to police? Or am I wrong somewhere?
>
>     Thanks a lot!
>
> Regards,
>
> Paul

I executed successfully the following instructions:

  mplsadm2 -A -O gen:100:eth2:ipv4:192.168.1.18
  mplsadm2 -L eth0:0
  mplsadm2 -A -I gen:50:0 -i 
ds2exp:0x3f:0x2e:1:0x0a:2:exp2tc:1:0x2e:2:0x0a:fwd:key:2

for Paul : if you execute a command for ds2exp and then a command for exp2tc, 
only the latest instructions will be set

for James : after executing the last command, it appears on the screen "In 
Instr: Device not configured" even if the instructions are set correctly.
Moreover you should correct in mpls_proc.c (case exp2tc) to avoid that 
information like exp(5)->tc(ffff) are printed in /proc/net/mpls_*

Stefano