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
1f57c0bd2e
RIOT/tests/lwip_sock_ip
History
Marian Buschsieweke 0e90e6195f
tests: Updated Updated BOARD_INSUFFICIENT_MEMORY 
Added arduino-nano to BOARD_INSUFFICIENT_MEMORY/BOARD_BLACKLIST following suit
of how arduino-uno is marked, as arduino-nano is mostly an Uno in a different
form factor.
2019-03-14 15:39:54 +01:00
..
tests
constants.h
main.c tests/lwip_sock_ip: make non-static consts static 2018-10-16 19:09:23 +02:00
Makefile tests: Updated Updated BOARD_INSUFFICIENT_MEMORY 2019-03-14 15:39:54 +01:00
README.md
stack.c Merge pull request #10905 from maribu/packet_size_l2_pdu 2019-02-22 15:23:00 +01:00
stack.h

README.md

Tests for lwIP's sock_ip port

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