RIOT/tests/gnrc_ipv6_ext
Koen Zandberg 8a6d04ce52
Merge pull request #7925 from RIOT-OS/gnrc_netif2_integration/master
gnrc_netif2: gnrc_ipv6_nib: full integration into GNRC
2017-11-27 21:12:14 +01:00
..
2017-11-17 10:41:54 +01: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.