RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
bb8402fc0b
RIOT/tests/lwip_sock_tcp
History
Erik Ekman 691bd46aae tests/lwip_sock: Don't control IPv6 usage from IPv4 
Require less hacks to use dual stack
2021-11-06 18:01:06 +01:00
..
tests
constants.h
main.c
Makefile tests/lwip_sock: Don't control IPv6 usage from IPv4 2021-11-06 18:01:06 +01:00
Makefile.ci boards/stm32g031-disco,examples,tests: Added STM32G031-DISCO board 2021-10-13 12:14:45 -04:00
README.md
stack.c
stack.h

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).