[mpls-linux-general] mpls-linux 1.108 (BETA!!!)

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

I just updated the CVS on sourceforge.  Check out the mpls-linux module
with a revision of mpls-linux_1_108.  This will have a kernel patch
a patch to iptables, and a patch to ppp.  You only need the iptables
patch if you want to use the new "instructions".

The basic functionality has been well tested, the new functionality
only has limited testing.

You'll notice this is the first release to have iptables.  Eventually
iptables will be the interface to bind a FEC to a LSP, not via the -B -f -O
combintion on mplsadm.

New instructions via mplsadm (only usable via -i and -o):

push:gen:16:eth1
fwd:gen:16:eth1
nffwd:0xF:0x1:0x44001001[:0x2:0x44001001]...
    where 0xF is the mask to apply to the nfmark or the packet, the
    resulting value is use for the lookup

    0x1:0x44001001 means packets with nfmark 0x1 (after mask is applied)
    is handled to the outgoing label entry with the key of 0x44001001
    (get the key from mpls_out)

    add upto 64 nfmark:key pairs

dsfwd:0xF:0x1:0x44001001[:0x2:0x44001001]...
    same as nfmark but the lookup value is taken from the ip header
    (this instruction is only valid on ingress LER)

expfwd:0x1:0x44001001[:0x2:0x44001001]...
    similar to nfmark but the lookup value is taken from the expbits
    in the incoming label shim.  There is not a mask value, only 8 exp:key
    pairs are allowed.

outgoing version 
set:eth1:ipv4:1.1.1.1
    set the outgoing next hop info

incoming version 
set:eth1
    set the rx-interface on the packet

set_ds:0x3
    set the dscp on the outgoing IP packet (only valid on egress LER)

set_exp:0x7
    set the expbits in the outgoing label shim

exp2tc:0x7:0x5[:0x4:0x100]...
    translate an expbit value from an incoming label shim into a
    tc-index which can be used by the tcindex traffic scheduler
    8 exp:tc pairs allowed

exp2ds:0x7:0x1:[0x1:0x6]...
    same at exp2tc except the dscp in the ip header is overwritten
    (only valid on egress LER)

tc2exp:0x5:0x7[:0x3F:0x4]...
    reverse of exp2tc, use a tc value on a packet and set the outgoing
    expbits in the label shim
    (64 tc:exp pairs allowed)

ds2exp:0x1:0x7[:0x6:0x1]...
    reverse of exp2ds, use a ds value in an IP header and set the
    outgoing expbits (only valid on ingress LER)
    (64 ds:exp pairs allowed)

NOTES:
    order does matter!
    don't think of outgoing info as having to push a label!
    I know some places I use key values and other places I use the
      old gen:16:eth1 values, evetually everything will use the keys

Please e-mail me with bugs and questions

Jim
-- 
James R. Leu