mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00

History

Cenk Gündoğan 710c7e6cf6 transport_layer: Splitting UDP and TCP Currently, the tcp and udp implementations are bound to each other in a module called destiny. Thus, when using only one of them then the other one gets also compiled into the binary and initialized, which results in unnecessary RAM usage and workload for the CPU. The approach in this PR defines a common module named socket_base, which contains functions used by the posix layer. Compiled by it's own, those functions return negative error codes, to symbolize upper layers that they are not supported. When also including the modules udp or tcp respectively, functions from socket_base get overwritten with the correct functionality. Defining udp or tcp in a Makefile also includes socket_base. Defining pnet in a Makefile also includes socket_base.		2014-09-11 20:07:46 +02:00
..
helper.c	rpl: moved headers to sys/net/include	2014-08-21 21:34:45 +02:00
main.c	transport_layer: Splitting UDP and TCP	2014-09-11 20:07:46 +02:00
Makefile	transport_layer: Splitting UDP and TCP	2014-09-11 20:07:46 +02:00
README.md	examples: fix rpl_udp README regarding invocation	2014-02-27 16:35:07 +01:00
rpl_udp.h	licenses: updated some missing licenses in headers	2014-08-21 23:52:42 +02:00
rpl.c	transport_layer: Splitting UDP and TCP	2014-09-11 20:07:46 +02:00
udp.c	transport_layer: Splitting UDP and TCP	2014-09-11 20:07:46 +02:00

README.md

#tl;dr

command order:

set <node-id>
init [r|n]
server
send <node-id> <message>

setup

compile the application

cd RIOT/examples/rpl_udp
make

Set up a bridge for two tap devices to communicate over

../../cpu/native/tapsetup.sh create 2

rpl init

Run the first node

make term

Type help to see the commands available. Now you need set the node ID. This ID will be used by other nodes to address this node.

> set 1
set 1
Set node ID to 1

Init your rpl node as either a root or a node router.

> init n
init n
INFO: Initialize as node on address 2
6LoWPAN and RPL initialized.
Channel set to 10
Destiny initialized

> init r
init r
INFO: Initialize as root on address 1
6LoWPAN and RPL initialized.
Channel set to 10
Destiny initialized

(It is advised to start all nodes before running the root node, because the interval for sending DIOs from the root increases over time) A few seconds withing running, setting and initializing your second node, the nodes will automatically start to exchange control traffic. You should be seeing output similar to the following:

41 CC FC 34 12 36 12 00 FF FE 00 00 02 36 12 00 FF FE 00 00 01 7A 33 3A 9B 03 F9 90 00 00 04 00 00 80
IPv6 datagram received (next header: 3A) from fe80:0000:0000:0000:3612:00ff:fe00:0001 	 ICMP type: 5A 	 ICMP code: 08
Received packet from ID 1
	Length:	34
	Src:	1
	Dst:	2
	LQI:	0
	RSSI:	0

You can now use the dodag command to obtain information on the node's rank in the rpl dodag as well as their preferred parent

> dodag
dodag
---------------------------
Part of Dodag:
fe80:0000:0000:0000:3612:00ff:fe00:0001
my rank: 512
my preferred parent:
fe80:0000:0000:0000:3612:00ff:fe00:0001
---------------------------

#sending via UDP

In order to be able to receive UDP messages from other nodes, we have to start rpl_udp's UDP server:

> server
server
UDP SERVER ON PORT 511 (THREAD PID: 17)

When rpl is running, you can send a message from any participating node to the node initialized as a server (in our case, node 1) using the send command

> send 1 hi
send 1 hi
Successful deliverd 11 bytes over UDP to abcd:0000:0000:0000:3612:00ff:fe00:0001 to 6LoWPAN

In case of an error message, make sure that rpl is running and you've started the UDP server on the receiving node by running the server command.