History

Reto Schneider 7eabab2f5d samples, tests: Use semi-accurate project names When using an IDE (e.g. Eclipse, Qt Creator), the project name gets displayed. This greatly simplifies the navigation between projects when having many of them open at the same time. Naming every project "NONE" defeats this functionality. This patch tries to use sensible project names while not duplicating too much of what is already represented in the path. This is done by using the name of the directory the relevant CMakeLists.txt file is stored in. To ensure unique project names in the samples (and again, in the tests folder) folder, small manual adjustments have been done. Signed-off-by: Reto Schneider <code@reto-schneider.ch>		2018-10-27 21:31:25 -04:00
..
node	samples, tests: Use semi-accurate project names	2018-10-27 21:31:25 -04:00
root	samples, tests: Use semi-accurate project names	2018-10-27 21:31:25 -04:00
README.md	…

README.md

RPL Mesh Network over QEMU

Overview

This sample uses virtual-hub tool from zephyrproject-rtos/net-tools to setup a multi-node RPL network on top of QEMU. This way, is possible to validate different network topologies in virtualized environment.

In this sample, we will build a three node graph connected like a row:

root <-> node1 <-> node2

Requirements

First of all, we must clone net-tools repository, and build virtual-hub:

cd virtual-hub
mkdir build && cd build
cmake ..
make

Building and Running

Build and run the RPL root application:

cd root
mkdir build && cd build
cmake -DQEMU_PIPE_ID=1 ..
make
make node

Build and run the first RPL node application:

cd node
mkdir build-1 && cd build-1
cmake -DQEMU_PIPE_ID=2 ..
make
make node

Build and run the second RPL node application:

cd node
mkdir build-2 && cd build-2
cmake -DQEMU_PIPE_ID=3 ..
make
make node

Now we should run the virtual-hub, which will connect all the pipes according to the csv file:

cd virtual-hub/build
./hub ../input.csv

Wait until the network is fine, you can check it using net shell on root application:

select net
route

You should see two routes pointing to both clients application.

Virtual-Hub Notes

When trying to reboot/drop a node from network you must also reboot the virtual-hub to keep it working properly.

For more details about how to customize the network, follow the README instructions from virtual-hub repository.