2019-02-19 16:42:07 +08:00
|
|
|
.. _networking_with_host:
|
|
|
|
|
|
|
|
|
|
Networking with the host system
|
|
|
|
|
###############################
|
|
|
|
|
|
2019-02-24 19:39:14 +08:00
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 1
|
|
|
|
|
:hidden:
|
|
|
|
|
|
|
|
|
|
native_posix_setup.rst
|
|
|
|
|
qemu_eth_setup.rst
|
|
|
|
|
qemu_setup.rst
|
|
|
|
|
usbnet_setup.rst
|
2020-05-06 07:56:52 +08:00
|
|
|
qemu_user_setup.rst
|
2020-05-08 19:48:46 +08:00
|
|
|
networking_with_multiple_instances.rst
|
2020-11-04 20:37:51 +08:00
|
|
|
qemu_802154_setup.rst
|
2019-02-24 19:39:14 +08:00
|
|
|
|
2019-02-19 16:42:07 +08:00
|
|
|
While developing networking software, it is usually necessary to connect and
|
|
|
|
|
exchange data with the host system like a Linux desktop computer.
|
|
|
|
|
Depending on what board is used for development, the following options are
|
|
|
|
|
possible:
|
|
|
|
|
|
|
|
|
|
* QEMU using SLIP (Serial Line Internet Protocol).
|
|
|
|
|
|
|
|
|
|
* Here IP packets are exchanged between Zephyr and the host system via serial
|
|
|
|
|
port. This is the legacy way of transferring data. It is also quite slow so
|
|
|
|
|
use it only when necessary. See :ref:`networking_with_qemu` for details.
|
|
|
|
|
|
|
|
|
|
* QEMU using built-in Ethernet driver.
|
|
|
|
|
|
|
|
|
|
* Here IP packets are exchanged between Zephyr and the host system via QEMU's
|
|
|
|
|
built-in Ethernet driver. Not all QEMU boards support built-in Ethernet so
|
|
|
|
|
in some cases, you might need to use the SLIP method for host connectivity.
|
|
|
|
|
See :ref:`networking_with_eth_qemu` for details.
|
|
|
|
|
|
2020-05-06 07:56:52 +08:00
|
|
|
* QEMU using SLIRP (Qemu User Networking).
|
|
|
|
|
|
|
|
|
|
* QEMU User Networking is implemented using "slirp", which provides a full TCP/IP
|
|
|
|
|
stack within QEMU and uses that stack to implement a virtual NAT'd network. As
|
|
|
|
|
this support is built into QEMU, it can be used with any model and requires no
|
|
|
|
|
admin privileges on the host machine, unlike TAP. However, it has several
|
|
|
|
|
limitations including performance which makes it less valuable for practical
|
|
|
|
|
purposes. See :ref:`networking_with_user_qemu` for details.
|
|
|
|
|
|
2019-02-19 16:42:07 +08:00
|
|
|
* native_posix board.
|
|
|
|
|
|
2019-02-28 05:55:32 +08:00
|
|
|
* The Zephyr instance can be executed as a user space process in the host
|
2019-02-19 16:42:07 +08:00
|
|
|
system. This is the most convenient way to debug the Zephyr system as one
|
|
|
|
|
can attach host debugger directly to the running Zephyr instance. This
|
|
|
|
|
requires that there is an adaptation driver in Zephyr for interfacing
|
|
|
|
|
with the host system. An Ethernet driver exists in Zephyr for this purpose.
|
|
|
|
|
See :ref:`networking_with_native_posix` for details.
|
|
|
|
|
|
|
|
|
|
* USB device networking.
|
|
|
|
|
|
|
|
|
|
* Here, the Zephyr instance is run on a real board and the connectivity to
|
|
|
|
|
the host system is done via USB.
|
|
|
|
|
See :ref:`usb_device_networking_setup` for details.
|
2020-05-08 19:48:46 +08:00
|
|
|
|
|
|
|
|
* Connecting multiple Zephyr instances together.
|
|
|
|
|
|
|
|
|
|
* If you have multiple Zephyr instances, either QEMU or native_posix ones,
|
|
|
|
|
and want to create a connection between them, see
|
|
|
|
|
:ref:`networking_with_multiple_instances` for details.
|
2020-11-04 20:37:51 +08:00
|
|
|
|
|
|
|
|
* Simulating IEEE 802.15.4 network between two QEMUs.
|
|
|
|
|
|
|
|
|
|
* Here, two Zephyr instances are running and there is IEEE 802.15.4 link layer
|
|
|
|
|
run over an UART between them.
|
|
|
|
|
See :ref:`networking_with_ieee802154_qemu` for details.
|
