1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
RIOT/tests/gnrc_ipv6_ext
2018-01-17 16:25:26 +01:00
..
tests Merge pull request #8247 from aabadie/pr/tests/python_E305 2017-12-13 10:52:57 +01:00
main.c gnrc_netif2: rename to gnrc_netif 2017-11-17 10:41:54 +01:00
Makefile tests/gnrc_ipv6_ext: Increase ipv6 addr numof 2018-01-17 16:25:26 +01:00
README.md tests/gnrc_ipv6_ext: update README.md 2017-02-06 16:27:51 +09:00

gnrc_ipv6_ext test

This test sends a packet to itself with extension headers. This is based on gnrc_networking example.

Enable debug output of gnrc_ipv6.c before run. When the test is run, it should show the following debug output:

ipv6: Received (src = fd01::1, dst = fd01::2, next header = 0, length = 42)
ipv6: forward nh = 0 to other threads
ipv6: handle extension header (nh = 0)
ipv6: waiting for incoming message.
ipv6: GNRC_NETAPI_MSG_TYPE_RCV received
ipv6: Received (src = fd01::1, dst = fd01::3, next header = 0, length = 42)
ipv6: forward nh = 0 to other threads
ipv6: handle extension header (nh = 0)
ipv6: waiting for incoming message.
ipv6: GNRC_NETAPI_MSG_TYPE_RCV received
ipv6: Received (src = fd01::1, dst = fd01::2, next header = 0, length = 42)
ipv6: forward nh = 0 to other threads
ipv6: handle extension header (nh = 0)
ipv6: forward nh = 17 to other threads
ipv6: waiting for incoming message.
pkt->users: 0

It configures the network interface with addresses fd01::02 and fd01::03. Then it sends a packet to fd01::02 with a routing extension header containing addresses fd01::03 and fd01::02. So the packet should be forwarded from fd01::02 to fd01::03, then to fd01::02 again.

The packet has a Hop-by-Hop extension header that should be ignored.

The test also asserts that the packet is released.