marc
/
RIOT
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
14626 Commits
7 Branches
4 Tags
43 MiB
 
 
 
 
 
 
Tree: 961056548b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '961056548b'
${ noResults }
RIOT/tests/lwip_sock_udp
Kaspar Schleiser 0fcc7d3834
cleanup: apply headerguard script output 		6 years ago
..
tests pkg: provide sock_udp support for lwip 6 years ago
Makefile tests: remove nucleo32-l031 from memory intensive tests 6 years ago
README.md netdev2: rename to netdev and remove `gnrc_netdev` 6 years ago
constants.h cleanup: apply headerguard script output 6 years ago
main.c tests: adapt lwip tests for v2.0.2's API 6 years ago
stack.c tests: adapt lwip tests for v2.0.2's API 6 years ago
stack.h cleanup: apply headerguard script output 6 years ago

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