mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00

History

Marian Buschsieweke d2a3ff3d83 boards/{bluepill,blackpill}: rename and improve doc - renamed: - `bluepill` --> `bluepill-stm32f103c8` - `bluepill-128kib` --> `bluepill-stm32f103cb` - `blackpill` --> `blackpill-stm32f103c8` - `blackpill-128kib` --> `blackpill-stm32f103cb` - doc: - added link to corresponding hardware page on the STM32-base project - added picture		2023-01-02 16:23:10 +01:00
..
tests	tests: expect match \r\n or \s	2019-11-27 14:12:12 +01:00
constants.h	treewide: Remove excessive newlines	2021-08-13 19:50:38 +02:00
main.c	tests/lwip*: use ztimer instead of xtimer	2022-03-03 15:54:22 +01:00
Makefile	Merge pull request #17434 from kaspar030/murdock_use_emulators	2022-04-06 14:41:48 +02:00
Makefile.ci	boards/{bluepill,blackpill}: rename and improve doc	2023-01-02 16:23:10 +01:00
README.md	netdev2: rename to netdev and remove `gnrc_netdev`	2017-03-15 09:31:20 +01:00
stack.c	tests/lwip*: use ztimer instead of xtimer	2022-03-03 15:54:22 +01:00
stack.h	tests: fix doxygen grouping	2018-06-11 19:12:02 +02:00

README.md

Tests for lwIP's sock_tcp port

This tests the sock_tcp port of lwIP. There is no network device needed since a virtual device is provided at the backend.

These tests test both IPv4 and IPv6 capabilities. They can be activated by the LWIP_IPV4 and LWIP_IPV6 environment variables to a non-zero value. IPv6 is activated by default:

make all test
# or
LWIP_IPV6=1 make all test

To just test IPv4 set the LWIP_IPV4 to a non-zero value (IPv6 will be deactivated automatically):

LWIP_IPV4=1 make all test

To test both set the LWIP_IPV4 and LWIP_IPV6 to a non-zero value:

LWIP_IPV4=1 LWIP_IPV6=1 make all test

Since lwIP uses a lot of macro magic to activate/deactivate these capabilities it is advisable to test all three configurations individually (just IPv4, just IPv6, IPv4/IPv6 dual stack mode).