Re: [mpls-linux-general] Ping Problem

[Ramon C. <cas...@in...>]

On Thu, 25 Mar 2004, Josef Perlinger wrote:


MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on 
if. w/o labelspace
MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)


This usually means that you recived a packet on an interface that was not 
"MPLS enabled", that is, the labelspace is -1. So the kernel network stack
actually hands over the frame to the MPLS module, but it has not allocated 
the required data structs for the incoming interface so it drops the 
packet...


Could you please try setting a labelspace (let it be 0) for the used 
interfaces and try again? I *do* see that the is an IOCTL to set the 
labelspace, but could you please check after that it has really been set?
Maybe you spot a bug..

PS: I will add some code to mpls_input so we get the name of the interface 
displayed...


thanks,
Ramon




> Ping from UML1 to UML2

...
> MPLS DEBUG net/mpls/mpls_ioctls.c:59:mpls_ioctl: IOCTL Set LabelSpace 
> MPLS DEBUG net/mpls/mpls_if.c:176:__mpls_set_labelspace: enter
> MPLS DEBUG net/mpls/mpls_if.c:198:__mpls_set_labelspace: exit
...
> MPLS DEBUG net/mpls/mpls_input.c:240:mpls_skb_recv: enter
> MPLS mpls_skb_dump: from eth1 with len 88 (1704)headroom=30 tailroom=1418
> 00000000000000000000000000000000*fefd0b000102fefd0b0001018847{00010140450000
> 5400004000400122a70b0001010b00010208007acc130100004063214800091d7b08090a0b0c
> 0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f303132
> 3334353637}00
> MPLS DEBUG net/mpls/mpls_input.c:256:mpls_skb_recv: unicast packet recv on
> if. w/o labelspace
> MPLS DEBUG net/mpls/mpls_input.c:303:mpls_skb_recv: exit(DROP)



> Something isn't implemented in here

Most probably :)

R.