[mpls-linux-general] MPLS tunnels OOPsing kernel [Follow Up]

[<igb...@ya...>]

Ok,

We have gone through and turned debugging on when
setting up a tunnel.


Here are the commands we used, the debug output from
mplsadm and the output of /proc/net/mpls_tunnel



Commands:


mplsadm -d
mplsadm -L eth1:0
mplsadm -AO gen:100:eth1:ipv4:10.0.1.1
mplsadm -AT mpls0
ifconfig mpls0 10.0.1.1 netmask 255.255.255.252
mplsadm -BO gen:100:eth1 -T mpls0
route add -host 10.0.1.2/32 mpls0


Output from debug messages:

MPLS: debug is now on
mpls_set_labelspace: enter
mpls_set_labelspace: labelspace(0)
mpls_set_labelspace: exit
mpls_add_out_label: enter
mpls_make_dst: enter
mpls_make_dst: before bind neighbor
mpls_make_dst: bind neighbor succeeded
mpls_make_dst: exit(c3816be0)
mpls_info_default_moi_instruction: enter
mpls_info_default_moi_instruction: exit
Label GEN 100
Key GEN 100 5
mpls_add_out_label: exit
mpls_tunnel_add_out: enter
mpls_tunnel_add_out: error getting node in radix tree



and the output of /proc/net/mpls_tunnel

mpls0 00000000


An ifconfig on the mpls0 interface shows that the link
encapsulation as UNSPEC and that the addr of the
tunnel and the point to point address are the same. Is
this correct ???

As soon as any traffic is sent down the tunnel the
machine OOPS's with the output we sent yesterday.

The last line of the mplsadm output seems to be most
interesting. Any idea why it should say that ??


Thanks





__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com