Ashim, Ken,
from what I understand, `ethos` works by multiplexing `ethernet` packets
with `stdio` ones where `tunslip` does it with `ip` packets.
So `ethos` uses `tap` interfaces as it works at link layer where
`tunslip` uses `tun` as it works at network layer.
Cheers
Gaëtan
On 6/25/19
I am a user of these tools rather than a developer, and do not know
enough of the internals to answer your questions. It may even be
possible that you can use ethos/tap for this application, and I just
couldn't find the right configuration. Perhaps someone else can chime in.
On 6/25/19 3:25
Dear Ken
Thank you very much! Everything worked like a charm. I just have a few follow
up questions. It seems that usually tap is preferred over tun for most of the
RIOT applications. Why is this? Also is it possible to get a tun interface set
up with ethos?
Kind regards
Ashim Asharaph
I forgot one other thing. You'll need the header for SLIP parameters.
Grab the one from gcoap and copy it to the location of your Makefile [1].
[1]
https://github.com/RIOT-OS/RIOT/blob/master/examples/gcoap/slipdev_params.h
On 6/22/19 7:23 AM, Ken Bannister wrote:
Hi Ashim,
I tried to get
Hi Ashim,
I tried to get ethos to work with a samr21-xpro, but failed. I was not
permitted to assign an IP address to the wired interface. Rather than
pursue that, I was successful with SLIP, the legacy border router tool.
See the gist for the Wakaama Makefile modified for SLIP [1]. Compile
Dear RIOT developers
I would like to get LWM2M communication through ethos between a board and
computer (without using a border router). It is necessary to do it this way
because the board does not have any wireless or ethernet capability. I am
testing the idea on a samr21-xpro for now. I am
