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
5dc32b14cc
RIOT/tests/lwip_sock_tcp
History
Alexandre Abadie 15d58760a9
Merge pull request #12822 from fjmolinas/pr_fix_eol 
tests: fix tests matching varied sized group regex
2019-11-28 08:01:30 +01:00
..
tests tests: expect match \r\n or \s 2019-11-27 14:12:12 +01:00
constants.h tests/lwip_sock_tcp: make IPv4 address byteorder static 2018-10-16 19:09:23 +02:00
main.c tests: add test_utils_interactive_sync when possible 2019-11-27 15:07:42 +01:00
Makefile tests: BOARD_INSUFFICIENT_MEMORY -> Makefile.ci 2019-10-17 15:11:59 +02:00
Makefile.ci tests: add stm32f030f4-demo to Makefile.ci 2019-10-21 15:33:11 +02:00
README.md netdev2: rename to netdev and remove gnrc_netdev 2017-03-15 09:31:20 +01:00
stack.c tests: fix doxygen grouping 2018-06-11 19:12:02 +02: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).