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
eef26e2ef6
RIOT/tests/lwip_sock_udp
History
Kaspar Schleiser 0fcc7d3834 cleanup: apply headerguard script output
2017-05-24 17:54:02 +02:00
..
tests pkg: provide sock_udp support for lwip 2017-02-07 15:48:47 +01:00
constants.h cleanup: apply headerguard script output 2017-05-24 17:54:02 +02:00
main.c tests: adapt lwip tests for v2.0.2's API 2017-05-11 11:49:38 +02:00
Makefile tests: remove nucleo32-l031 from memory intensive tests 2017-03-15 14:08:06 +01:00
README.md netdev2: rename to netdev and remove gnrc_netdev 2017-03-15 09:31:20 +01:00
stack.c tests: adapt lwip tests for v2.0.2's API 2017-05-11 11:49:38 +02:00
stack.h cleanup: apply headerguard script output 2017-05-24 17:54:02 +02:00

README.md

Tests for lwIP's sock_udp port

This tests the sock_udp 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).