[riot-notifications] [RIOT-OS/RIOT] dhcpv6: Initial implementation of a client (with IA_PD support) (#8796)

Martine Lenders notifications at github.com
Thu Apr 5 10:28:05 CEST 2018


miri64 commented on this pull request.



> @@ -0,0 +1,53 @@
+include ../Makefile.tests_common
+
+RIOTBASE ?= $(CURDIR)/../..
+
+BOARD_INSUFFICIENT_MEMORY := chronos msb-430 msb-430h nucleo32-f042 \
+                             nucleo32-f031 nucleo-f030 nucleo-l053 \
+                             nucleo32-l031 stm32f0discovery telosb \
+                             wsn430-v1_3b wsn430-v1_4 z1
+
+# The following boards do not have an available UART
+BOARD_BLACKLIST += mips-malta pic32-wifire pic32-clicker ruuvitag thingy52
+
+TEST_ON_CI_WHITELIST += all

Yes, I know that `TEST_ON_CI_WHITELIST` is running `make test`. My question was, how can we make such tests possible on Murdock? This isn't such an exotic use case. As soon as you want to test some packet injecting or analysis for network traffic (which is the a sensible way to test networking automated, beyond the dull "let's see if we can send some [valid] packets around") you need to bind to a tap interface, which requires `sudo`. Beyond that, yes I use `scapy` which is a nifty python tool and library to generate and analyse network traffic ;-) (and requires sudo to do that on Ethernet packet, which you need to as soon as TAP interfaces are involved).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/8796#discussion_r179385305
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20180405/74a9517c/attachment.html>


More information about the notifications mailing list