Communication among running RIOT board (native) and unix application

Nazmul_Alam · 31 August 2016 00:02

Hello,

I am new to RIOT and trying to run it in native system. I would like to know if it is possible to add another tap interface to the bridge to monitor two native application’s packet transaction and their contents?

I want to communicate with an ipv4 based socket application with one of the running RIOT image. Will it be possible if I add an address to each of the images? or do I need another image as the border router to facilitate the connection between them?

Thanks in advance.

Michael_Frey · 31 August 2016 07:46

Hi,

I am new to RIOT and trying to run it in native system. I would like to know if it is possible to add another tap interface to the bridge to monitor two native application's packet transaction and their contents?

have you looked into des-virt? Have you also checked out the tutorials [1] at the wiki, such as [1].

I want to communicate with an ipv4 based socket application with one of the

To my best knowledge there is no IPv4 support in RIOT (yet).

Best, Michael

[1] Home · RIOT-OS/RIOT Wiki · GitHub [2] Tutorial: RIOT and Multi Hop Routing with RPL · RIOT-OS/RIOT Wiki · GitHub

Oleg_Hahm · 31 August 2016 08:43

Hi Nazmul, hi Michael!

> I am new to RIOT and trying to run it in native system. I would like to > know if it is possible to add another tap interface to the bridge to > monitor two native application's packet transaction and their contents?

have you looked into des-virt? Have you also checked out the tutorials [1] at the wiki, such as [1].

There's also a basic documentation available in the gnrc_networking example:

github.com

RIOT-OS/RIOT/blob/master/examples/gnrc_networking/README.md

# gnrc_networking example

This example shows you how to try out the code in two different ways:
Either by communicating between the RIOT machine and its Linux host,
or by communicating between two RIOT instances.
Note that the former only works with native, i.e. if you run RIOT on
your Linux machine.

## Connecting RIOT native and the Linux host

> **Note:** RIOT does not support IPv4, so you need to stick to IPv6
> anytime. To establish a connection between RIOT and the Linux host,
> you will need `netcat` (with IPv6 support). Ubuntu 14.04 comes with
> netcat IPv6 support pre-installed.
> On Debian it's available in the package `netcat-openbsd`. Be aware
> that many programs require you to add an option such as -6 to tell
> them to use IPv6, otherwise they will fail. If you're using a
> _Raspberry Pi_, run `sudo modprobe ipv6` before trying this example,
> because raspbian does not load the IPv6 module automatically.
> On some systems (openSUSE for example), the _firewall_ may interfere,

This file has been truncated. show original

> I want to communicate with an ipv4 based socket application with one of > the

To my best knowledge there is no IPv4 support in RIOT (yet).

In theory lwip, which is available as a package in RIOT, has support for IPv4, but in practise I think no one has every tested this in RIOT.

Cheers, Oleg

Nazmul_Alam · 31 August 2016 17:13

Hi Michael and Oleg,

Thank you for your valuable suggestions, I will look into it.