Re: [mpls-linux-general] MPLS+IPv6

[Bruno J. M. <bj...@me...>]

I've checked dmesg and seems the packets aren't entering the MPLS stack...

The only messages that I have are from (modified) mplsadm2 commands:
	mplsadm2 -d
	mplsadm2 -A -O 0 -o push.gen.56.set.eth1.ipv6.$NET::65

MPLSADM mplsadm6.c:696:main: Out segment input: 0
MPLSADM mplsadm6.c:692:main: Out instr input:
push.gen.56.set.eth1.ipv6.fc97:86d5:b2ed::65
Key: 0x00000002
Out Segment add: Success
MPLSADM mplsadm6.c:296:fill_instructions: Instruction: push
MPLSADM mplsadm6.c:233:fill_label: Label type: gen
MPLSADM mplsadm6.c:296:fill_instructions: Instruction: set
MPLSADM mplsadm6.c:185:parse_nh_info: eth1
MPLSADM mplsadm6.c:186:parse_nh_info: fc97:86d5:b2ed::65
MPLSADM mplsadm6.c:208:parse_nh_info: Nexthop protocol: ipv6
MPLSADM mplsadm6.c:600:fill_instructions: Length: 2
Out Instr: Success

	output of dmesg:

MPLS DEBUG net/mpls/mpls_ioctls.c:109:mpls_ioctl: IOCTL Add NHLFE 35847
MPLS DEBUG net/mpls/mpls_out_info.c:322:mpls_add_out_label: enter
MPLS DEBUG net/mpls/mpls_out_info.c:395:mpls_add_out_label: added MOI-NHLFE moi-2
MPLS DEBUG net/mpls/mpls_out_info.c:396:mpls_add_out_label: exit
MPLS DEBUG net/mpls/mpls_ioctls.c:180:mpls_ioctl: IOCTL Set OUT Instr. 35864
MPLS DEBUG include/net/mpls.h:665:mpls_out_info_hold: moi-2-get 3
MPLS DEBUG net/mpls/mpls_opcode_all.c:203:mpls_build_opcode_push: enter
MPLS DEBUG net/mpls/mpls_opcode_all.c:216:mpls_build_opcode_push: exit
MPLS DEBUG net/mpls/mpls_opcode_all.c:853:mpls_build_opcode_set: enter
MPLS DEBUG net/mpls/mpls_dst.c:170:mpls_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_dst.c:229:mpls_dst_alloc: exit(c1663bc0)
MPLS DEBUG net/mpls/mpls_opcode_all.c:918:mpls_build_opcode_set: exit
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-00-PUSH
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit
MPLS DEBUG net/mpls/mpls_utils.c:349:mpls_instr_register: enter
MPLS DEBUG net/mpls/mpls_utils.c:352:mpls_instr_register: registering OP-01-SET
MPLS DEBUG net/mpls/mpls_utils.c:356:mpls_instr_register: exit

routerPC5:/usr/src/mpls-linux/utils# cat /proc/net/mpls/out
MOI Key:0x00000002 Instruction Set
PUSH PUSH(gen 56)
SET SET(eth1,0.0.0.0)

I first used
	ip6tables -A OUTPUT -d $NET:2::/64 -j spec_nh --spec_nh 0x8847:0x2
and then
	ip -f inet6 route add $NET:2::/64 dev eth1 spec_nh 0x8847 0x2

and none of the above commands worked! The packets aren't using MPLS to leave the router...

I have an IPv6 network with 5 PC's running debian testing/unstable, kernel
2.6.2+mpls-1.922.

Can you help me resolve my problem/improving IPv6 support in
MPLS and ldp-portable?

I can make some changes in the code, but I you need to point me on what to do!

Regarding the changes in mplsadm2, you can see the parsing of commands
has changed from ":" to "." (because in IPv6, separator is now ":"). This
conflicts with IPv4 addresses...

Bruno


On Wed, 24 Mar 2004, James R. Leu wrote:

> On Wed, Mar 24, 2004 at 08:26:38PM +0000, Bruno Jorge Marcelino wrote:
> > Hi there!
> >
> > I'm doing some research on MPLS and IPv6 for my master thesis...
> >
> > Right now, i'm using kernel 2.6.2 with mpls-1.922 patch!
>
> I will be releasing 1.930 soon, with support for MPLS ICMP and better
> internal locking and referencing.
>
> > I've changed mplsadm2 to work with IPv6 address, and by looking at
> > debugging messages, I think that's all OK (no errors are found).
>
> Please send me a patch, I'd like to include support for IPv6.
>
> > Exception is in /proc/net/mpls/in, where  SET(ethX,X.X.X.X) appears
> > with 0.0.0.0 (because macro NIPQUAD(a) only works with IPv4 addresses, right?).
>
> This should be an easy to fix.
>
> > But I have a problem when binding FEC to LSP (with mpls patched
> > ip6tables): it isn't working! The traffic is not leaving the router using
> > mpls.
> >
> > Do you have any idea on the problem?
>
> Did you check the MPLS kernel debug?  (execute the command 'dmesg').
> Did the packets ever enter the MPLS stack?  What command did you
> use?  None of the IPv6 code has been tested.  I do not have an IPv6 network
> to test with (nor do I know how to set one up).
>
> Have you tried 'ip'?
>
> ip -f inet6 route add <ipv6 route>/<mask len> dev eth0 spec_nh 0x8847 <key>
>
> > What's the status on porting ldp-portable to 2.6 kernel with IPv6?
>
> ldp-portable has the structures to handle IPv6, but no code has been written
> to handle IPv6.  I would be glad to point you to the places I know that
> would be affected by IPv6.
>
> --
> James R. Leu
> jl...@mi...
>