Re: [mpls-linux-general] RTNETLINK answers: Operation not permitted

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

Do you have mpls4 loaded?  I have tried to make everything with mpls-linux
1.950 modular (I may have gone over board :-).

The layer controlling L3 -> MPLS is called the shim layer and could be
made into a module (don't threaten me or I'll do it ;-).  The layer
controlling MPLS to IPv4 is a module (mpls4).  There is a module for
the tunnel interface (mpls_tunnel), which if loaded multiple time (with
different names) will create multiple mpls tunnel interfaces.  And of
course MPLS itself is a module now.  The MPLS -> IPv6 module is called
mpls6 and there is a module the handles MPLS -> ethernet called mplsbr
(for EoMPLS).  Finally there are IPtables and ebtables target modules
for mapping iptables or ebtables rules to MPLS.

Do a 'modprobe mpls4' this will load the protocol driver for IPv4 which
handle the ipv4 part of the nexthop creation and handles delivery of MPLS
packets to IPv4 on the egress LER.

I have found an error with unloading the mpls4 module and when creating
an ilm (mpls command appears to segfault)  These are related to locking
issues that popped up when compiling the FC4 RPM.  I'm working on fixes.
Once I have all of the bugs worked out, I'll make a formal announcement.
In the meantime I'll continue to update SF with my incremental changes.

(make sure you have iproute 1.950c)

On Mon, Dec 19, 2005 at 08:22:40PM -0500, Siddhardha N. Garige wrote:
>  Hi,
> I am trying to setup a simple LSP between two linux boxes and i am having
> some trouble.
> Here is the trace.
>=20
>=20
> -bash-3.00# cat /sys/mpls/version
> 1.950
>=20
> -bash-3.00# mpls nhlfe add key 0
> NHLFE entry key 0x00000003 mtu 0 propagate_ttl
>          (0 bytes, 0 pkts)
>=20
> -bash-3.00# mpls nhlfe change key 0x3 instructions push gen 1000 nexthop
> eth0 ipv4 172.16.88.2
> RTNETLINK answers: Operation not permitted
>=20
> Debug messages:
> -bash-3.00# tail /var/log/debug
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_opcode.c:1082:mpls_build_opcode_set: exit
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_instr.c:89:mpls_instrs_free: enter
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_instr.c:65:mpls_instr_release: enter
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_opcode.c:376:mpls_clean_opcode_push: enter
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_opcode.c:378:mpls_clean_opcode_push: exit
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_instr.c:73:mpls_instr_release: exit
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_instr.c:65:mpls_instr_release: enter
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_instr.c:73:mpls_instr_release: exit
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_instr.c:95:mpls_instrs_free: exit
> Dec 19 22:37:07 mpls02 kernel: MPLS DEBUG
> net/mpls/mpls_netlink.c:339:genl_mpls_nhlfe_new: Exit: -1
>=20
> Any help?..
>=20
> Regards,
> Sid

--=20
James R. Leu
jl...@mi...