On Fri, 23 Jan 2004, Jung Janos wrote:
> Hi!
>
> mplsadm2 -AO 0 (out: key1)
> mplsadm2 -O key1 -o push:gen:16:set:eth1:ipv4:10.120.0.6
> ip route add 10.120.0.6/32 lsp key1
> #out:RTNETLINK answers: no such device
I am not really sure (I am mostly working on the 2.6 version with a new
mplsadm and debugging mechanisms that will make it easier to track bugs),
but I wonder if the eth1 interfcace is MPLS enabled? Try setting the
labelspace (e.g. to 0) before actually mapping the traffic to the LSP
mplsadm2 -L eth1:0
before
mplsadm2 -O key1 -o push:gen:16:set:eth1:ipv4:10.120.0.6
Idem for host B
> what does it mean? what is RTNETLINK?
The answer to that question is complicated and out of the scope of this
mail :-P but netlink is a linux kernel mechanism that allows user space
applications to communicate with parts of the kernel (for example to
get/set routes).
> i think this host can not send
> IP packets over mpls :)
It's being lazy....
Not sure if it answers your question, but it is worth trying.
Regards,
R.
|