Re: QEMU networking: CONFIG_NET_TESTING breaks things, echo_server IPv6 address is "wrong"

Maureen Helm

-----Original Message-----
From: Paul Sokolovsky [mailto:paul.sokolovsky(a)]
Sent: Thursday, August 18, 2016 10:43 AM
To: Flavio Santes <flavio.santes(a)>
Cc: devel(a)
Subject: [devel] Re: Re: QEMU networking: CONFIG_NET_TESTING breaks
things, echo_server IPv6 address is "wrong"

On Wed, 17 Aug 2016 20:19:06 -0000
"Flavio Santes" <flavio.santes(a)> wrote:



Taking a chance, I'd like to start with drawing attention to "docs:
Subsystems/Networking section is almost empty". Zephyr networking
See also

information currently is sparse, disperse, bits are out of date, and
there're omissions/inconsistencies. Just linking a wiki landing page
from the official docs and letting community fill in that wiki would
be a good first step.

Anyway, waiting for real hardware support, I decided to give QEMU
networking a try. After some moderate googling, I arrived at;a=summary
and . The
initial outcome: nothing works.
There is support for real hardware, see:;a=blob;f=sample

There is also a driver for enc28j60, see:
Yes, thanks, I meant for Ethernet support in FRDM-K64F which I have on my
hands now.
Can you share?


The obvious question is what to do in this situation. I'm personally
keen to update to describe
a setup which actually works now (this is mostly doing steps in the
right order, but also building with CONFIG_NET_TESTING=n).
I've made first pass of changes to , ordering
connection bring up steps properly and adding a bit more info here and there.
Going to look into CONFIG_NET_TESTING in more detail before adding
suggestion to disable it in the wiki.

Best Regards,
Paul | Open source software for ARM SoCs Follow Linaro:!/linaroorg -

Join to automatically receive all group messages.