[Lr-wpan+6lowpan+UDP]

Gonçalo Atanásio

unread,

Jun 27, 2016, 6:08:46 AM6/27/16

to ns-3-users

Hi,

I'm trying to implement UDP over Lr-wpan+ 6lowpan, but I can't receive the packets. Is it possible to do this?
I'm using the client server UDP applications.

Best regards.

Konstantinos

unread,

Jun 27, 2016, 6:14:30 AM6/27/16

to ns-3-users

Hi,

Yes it is possible. You can use debug/tracing to identify where the packets are lost/dropped etc.

Regards,

K.

Gonçalo Atanásio

unread,

Jun 27, 2016, 6:25:04 AM6/27/16

to ns-3-users

Thanks Konstantinos, I did that and, I found some things a little bit odd:

-First thing, all worked out with csma instead of lr-wpan.
-Second, with lr-wpan and 6lowpan I wave 2 netdevices.

When I compare the output of the two (csma and lr-wpan), I found that the problem is in netDevice, because 6lowpan does not do the same thing like with the csma.

The phy layer receives the packet "0x1e67950 receiving packet with power: -76.6777dBm" and MAC too "PdDataIndication(): Packet is for me; forwarding up". But after that I just cant understand what is happening.

Best regards

Konstantinos

unread,

Jun 27, 2016, 6:41:47 AM6/27/16

to ns-3-users

In order to help you more, we need a test/minimal scenario with a small description of the expected output.

This is explained in the posting guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting#Surprising_behavior_and_bugs

Since you have identified that the PdDataIndication is called, you need to investigate more why the packet is not forwarded up.

Perhaps the callback is not connected:

m_mcpsDataIndicationCallback (params, p);

Regards,

K.

Gonçalo Atanásio

unread,

Jun 27, 2016, 9:20:21 AM6/27/16

to ns-3-users

Sorry for my bad habits,

My scenario is:

-2 nodes with lrwpan + sixlowpan

-1 have the app udp-server

-The other have udp-client

-The Client send packets to the Server, only that. They have one header that I developed, but the header works fine.

The packet is received by the Ipv6L3Protocol too,

Ipv6L3Protocol:Receive(0x1e623d0, 0x1e68b10, 0x1dfcba0, 34525, 02-02-ff:ff, 02-02-ff:ff, 1)
Packet from 02-02-ff:ff received on node 0

My script is in annex.

lrwpan_sixlowpan_udp.cc

Message has been deleted

Gonçalo Atanásio

unread,

Jun 27, 2016, 11:55:08 AM6/27/16

to ns-3-users

Sorry, I just discovered the problem. Was in the 6lowpan attributes I've chosen. Really sorry for my incompetence.

Best Regards

Em segunda-feira, 27 de junho de 2016 11:41:47 UTC+1, Konstantinos escreveu:

Gonçalo Atanásio

unread,

Jun 27, 2016, 2:07:42 PM6/27/16

to ns-3-users

Hi Konstantinos,

I have just one more question, sorry for being annoying, I've modified DSDV to ipv6 and I'm including it with "SetRoutingHelper", I send the script in annex.

The problem is, I have the routing tables well met but when I send a packet from the APP I talked about early, the packet goes to DSDV to check the rout and it returns the rout. Until here we are good. But, next, the netdevice from lr-wpan and 6lowpan says, we need ARP that in Ipv6 is NDISC, and goes again to DSDV with the NDISC address (for example: ff02::1:ff00:2).

I really can't find a solution for this, do you have any suggestion?

Em segunda-feira, 27 de junho de 2016 11:41:47 UTC+1, Konstantinos escreveu:

dsdvIpv6_802_15_4.cc

Konstantinos

unread,

Jun 27, 2016, 3:26:17 PM6/27/16

to ns-3-users

The porting to IPv6 may not be as straight forward as it seems (i.e converting at IPv4 to IPv6).

I would recommend to review the AODV v6 proposal here (https://groups.google.com/d/msg/ns-3-users/mtetYLTBd-I/A-SlVa8J1bEJ) that faced with similar issue.

Regards,

K.

Gonçalo Atanásio

unread,

Jun 27, 2016, 4:49:46 PM6/27/16

to ns-3-users

Yes, I know it's not simple, I've been doing the porting for a couple of weeks now, I've faced some troubles with broadcast->multicast, global and local addresses. But now I've been stuck here in the NDISC for some time. Thanks for the help, really. I didn't find that post, thanks for referring it.

Best Regards

Gonçalo Atanásio

unread,

Jun 28, 2016, 9:26:02 AM6/28/16

to ns-3-users

Hi Konstantinos,

With the same script I talked about and the same configuration, I'm having one unusual behavior. When 6lowpan receives the packet it thinks it is a fragment from UDP but is the entire packet. I don't know why is that.

Packet received: ns3::SixLowPanFragN (datagram size 1280 tag 21614 offset 14) ns3::Icmpv6DestinationUnreachable Fragment [72:176]
Packet length: 109
Dispatches: 229 - 224
SixLowPanNetDevice:ProcessFragment(0xf73750, ns3::SixLowPanFragN (datagram size 1280 tag 21614 offset 14) ns3::Icmpv6DestinationUnreachable Fragment [72:176])
This is for the FRAGN (Source = 20-20-00:20, Dest = 20-20-00:10)
Packet Tag is 21614
Packet original size is 1280 //why 6lowpan thinks original size is 1280?
Fragment size is 104

Em segunda-feira, 27 de junho de 2016 20:26:17 UTC+1, Konstantinos escreveu:

Gonçalo Atanásio

unread,

Jun 28, 2016, 10:30:19 AM6/28/16

to ns-3-users

Ok, just solve it by putting attacker mode in 1 and then it sends only the first fragment that is actually the packet. And now I'm receiving packets.

Em terça-feira, 28 de junho de 2016 14:26:02 UTC+1, Gonçalo Atanásio escreveu:

Hi Konstantinos

Reply all

Reply to author

Forward