gnrc_ipv6: Forward multicast packets addressed to self #5729

miri64 · 2016-08-05T12:54:10Z

Adaptation of #4528

miri64 · 2016-08-05T13:34:26Z

Murdock is happy :-)

kYc0o · 2016-08-05T13:42:14Z

Can I test it on monday? code was already ACKed so maybe it doesn't really need testing...

edit: code wasn't ACKed, I'll test on monday.

miri64 · 2016-08-05T13:50:59Z

Sure.

miri64 · 2016-08-05T13:51:31Z

I just tried to test it but it wasn't really working as I was expecting... But might be, that I just configured my Linux wrong :-/

miri64 · 2016-08-10T08:52:20Z

@kYc0o ping?

kYc0o · 2016-08-10T09:08:27Z

oups! sorry! I forgot this... I'm taking a look :) your tests succeeded?

kYc0o · 2016-08-11T16:00:32Z

Well I just tested in 2 samr21 and I have a panic.

First:

custom-1;ifconfig 7 add ff0e::1
1470930941.633923;custom-1;> ifconfig 7 add ff0e::1
1470930941.634350;custom-1;success: added ff0e::1/64 to interface 7

Then:

1470930968.251771;custom-2;> ping6 ff0e::1
1470930968.256324;custom-1;> 0x49ef
1470930968.264988;custom-1;*** RIOT kernel panic:
1470930968.265206;custom-1;FAILED ASSERTION.
1470930968.265376;custom-1;
1470930968.269420;custom-1; pid | name                 | state    Q | pri | stack ( used) | base       | current    
1470930968.273706;custom-1;   - | isr_stack            | -        - |   - |   512 (  148) | 0x20000000 | 0x200001b8
1470930968.281281;custom-1;   1 | idle                 | pending  Q |  15 |   256 (  128) | 0x2000041c | 0x2000049c 
1470930968.289528;custom-1;   2 | main                 | bl mutex _ |   7 |  1536 (  836) | 0x2000051c | 0x2000097c 
1470930968.297685;custom-1;   3 | pktdump              | bl rx    _ |   6 |  1536 (  248) | 0x2000317c | 0x20003684 
1470930968.306177;custom-1;   4 | 6lo                  | bl rx    _ |   3 |  1024 (  448) | 0x20003d44 | 0x2000401c 
1470930968.313585;custom-1;   5 | ipv6                 | running  Q |   4 |  1024 (  660) | 0x2000109c | 0x20001384 
1470930968.321605;custom-1;   6 | udp                  | bl rx    _ |   5 |  1024 (  280) | 0x2000454c | 0x20004834 
1470930968.333887;custom-1;   7 | at86rf2xx            | bl rx    _ |   3 |  1024 (  392) | 0x20000c00 | 0x20000efc 
1470930968.344932;custom-1;   8 | RPL                  | bl rx    _ |   5 |  1024 (  208) | 0x20003874 | 0x20003ba4 
1470930968.345168;custom-1;     | SUM                  |            |     |  8960 ( 3348)
1470930968.345344;custom-1;
1470930968.345502;custom-1;*** halted.
1470930968.345654;custom-1;
1470930969.251554;custom-2;ping timeout
1470930971.251300;custom-2;ping timeout
1470930973.252739;custom-2;ping timeout
1470930973.258598;custom-2;--- ff0e::1 ping statistics ---
1470930973.258820;custom-2;3 packets transmitted, 0 received, 100% packet loss

So the problem you already experienced is still there...

kYc0o · 2016-08-30T22:11:24Z

Did you have time to look into this one?

miri64 · 2016-10-18T14:07:31Z

Nope, will try to do this for the release.

miri64 · 2016-10-31T14:58:43Z

I doubt I will find time for this, but it's not a feature so not effected by feature freeze

miri64 · 2016-11-09T15:01:33Z

I don't think I manage to work on this until tomorrow. So postponed.

RIOT-2016.10 - Release Notes ============================ RIOT is a real-time multi-threading operating system that supports a range of devices that are typically found in the Internet of Things: 8-bit microcontrollers, 16-bit microcontrollers and light-weight 32-bit processors. RIOT is based on the following design principles: energy-efficiency, real-time capabilities, small memory footprint, modularity, and uniform API access, independent of the underlying hardware (this API offers partial POSIX compliance). RIOT is developed by an international open source community which is independent of specific vendors (e.g. similarly to the Linux community) and is licensed with a non-viral copyleft license (LGPLv2.1), which allows indirect business models around the free open-source software platform provided by RIOT. About this release: =================== This release provides a lot of new features as well as it fixes several major bugs. Among these new features are the new simplified network socket API called sock, the GNRC specific CoAP implementation gcoap and several new packages: TinyDTLS, the Aversive++ microcontroller library for robotics, the u8g2 graphic library, and nanocoap. Using the new sock API an implementation of the Simple Time Network Protocol (SNTP) was also introduced, allowing for time synchronization between nodes. New platforms include the Arduino Uno, the Arduino Duemilanove, the Arduino Zero, SODAQ Autonomo, and the Zolertia remote (rev. B). The most significant bug fix was done in native which led to a significantly more robust handling of ISRs and now allows for at least 1,000 native instances running stably on one machine. About 263 pull requests with about 398 commits have been merged since the last release and about 42 issues have been solved. 37 people contributed with code in 100 days. 1006 files have been touched with 166500 insertions and 26926 deletions. Notations used below: ===================== + means new feature/item * means modified feature/item - means removed feature/item New features and changes ======================== General ------- * Verbose behavior for assert() macro Core ---- + MPU support for Cortex-M API changes ----------- + Socket-like sock API (replacing conn) * netdev2: Add Testmodes and CCA modes * IEEE 802.15.4: clean-up Intra-PAN behavior * IEEE 802.15.4: centralize default values * gnrc_pktbuf: allow for 0-sized snips + gnrc_netapi: mbox and arbitrary callback support System libraries ---------------- No new features or changes Networking ---------- + Provide sock-port for GNRC + gcoap: a GNRC-based CoAP implementation + Simple Network Time Protocol (RFC 5905, section 14) + Priority Queue for packet snips + IPv4 header definitions Packages -------- + nanocoap: CoAP header parser/builder + TinyDTLS: DTLS library + tiny-asn1: asn.1/der decoder + Aversive++ microcontroller programming library + u8g2 graphic library Platforms --------- + Support for stm32f2xx MCU family + Low power modes for samd21 CPUs + More Arduino-based platforms: + Arduino Uno + Arduino Duemilanove + Arduino Zero + More boards of ST's Nucleo platforms: + ST Nucleo F030 board support + ST Nucleo F070 board support + ST Nucleo F446 board support + SODAQ Automono + Zolertia remote rev. B Drivers ------- + W5100 Ethernet device + Atmel IO1 Xplained extension + LPD8808 LED strips * at86rf2xx: provide capability to access the RND_VALUE random value register Build System ------------ + static-tests build target for easy local execution of CI's static tests Other ----- + Provide Arduino API to Nucleo boards + Packer configuration file to build vagrant boxes + CC2650STK Debugger Support + ethos: add Ethos over TCP support Fixed Issues from the last release ================================== #534: native debugging on osx fails #2071: native: *long* overdue fixes #3341: netdev2_tap crashes when hammered #5007: gnrc icmpv6: Ping reply goes out the wrong interface #5432: native: valgrind fails Known Issues ============ Networking related issues ------------------------- #3075: nhdp: unnecessary microsecond precision: NHDP works with timer values of microsecond precision which is not required. Changing to lower precision would save some memory. #4048: potential racey memory leak: According to the packet buffer stats, flood-pinging a multicast destination may lead to a memory leak due to a race condition. However, it seems to be a rare case and a completely filled up packet buffer was not observed. #4388: POSIX sockets: open socket is bound to a specific thread: This was an inherit problem of the conn API under GNRC. Since the POSIX sockets are still based on conn for this release, this issue persists #4527: gnrc_ipv6: Multicast is not forwarded if routing node listens to the address (might still be fixable for release, see #5729, #5230: gnrc ipv6: multicast packets are not dispatched to the upper layers) #5016: gnrc_rpl: Rejoining RPL instance as root after reboot messes up routing #5055: cpuid: multiple radios will get same EUI-64 Nodes with multiple interfaces might get the same EUI-64 for them since they are generated from the same CPU ID. #5656: Possible Weakness with locking in the GNRC network stack: For some operations mutexes to the network interfaces need to get unlocked in the current implementation to not get deadlocked. Recursive mutexes as provided in #5731 might help to solve this problem. #5748: gnrc: nodes crashing with too small packet buffer: A packet buffer of size ~512 B might lead to crashes. The issue describes this for several hundret nodes, but agressive flooding with just two nodes was also shown to lead to this problem. #5858: gnrc: 6lo: potential problem with reassembly of fragments: If one frame gets lost the reassembly state machine might get out of sync ### NDP is not working properly #4499: handle of l2src_len in gnrc_ndp_rtr_sol_handle: Reception of a router solicitation might lead to invalid zero-length link-layer addresses in neighbor cache. #5005: ndp: router advertisement sent with global address: Under some circumstances a router might send RAs with GUAs. While they are ignored on receive (as RFC 4861 specifies), RAs should have link-local addresses and not even be send out this way. #5122: NDP: global unicast address on non-6LBR nodes disappears after a while: Several issues (also see #5760) lead to a global unicast address effectively being banned from the network (disappears from neighbor cache, is not added again) #5467: ipv6 address vanishes when ARO (wrongly) indicates DUP caused by outdated ncache at router #5539: Border Router: packet not forwarded from ethos to interface 6 #5790: ND: Lost of Global IPV6 on node after sending lot of UDP frame from BR Timer related issues -------------------- #4841: xtimer: timer already in the list: Under some conditions an xtimer can end up twice in the internal list of the xtimer module #4902: xtimer: xtimer_set: xtimer_set does not handle integer overflows well #5338: xtimer: xtimer_now() not ISR safe for non-32-bit platforms. #5928: xtimer: usage in board_init() crashes: some boards use the xtimer in there board_init() function. The xtimer is however first initialized in the auto_init module which is executed after board_init() #6052: tests: xtimer_drift gets stuck: xtimer_drift application freezes after ~30-200 seconds native related issues --------------------- #495: native not float safe: When the FPU is used when an asynchronous context switch occurs, either the stack gets corrupted or a floating point exception occurs. #2175: ubjson: valgind registers "Invalid write of size 4" in unittests #4590: pkg: building relic with clang fails. #5796: native: tlsf: early malloc will lead to a crash: TLSF needs pools to be initialized (which is currently expected to be done in an application). If a malloc is needed before an application's main started (e.g. driver initialization) the node can crash, since no pool is allocated yet. other platform related issues ----------------------------- #1891: newlib-nano: Printf formatting does not work properly for some numberic types: PRI[uxdi]64, PRI[uxdi]8 and float are not parsed in newlib-nano #2006: cpu/nrf51822: timer callback may be fired too early #2143: unittests: tests-core doesn't compile for all platforms: GCC build-ins were used in the unittests which are not available with msp430-gcc #2300: qemu unittest fails because of a page fault #4512: pkg: tests: RELIC unittests fail on iotlab-m3 #4522: avsextrem: linker sometimes doesn't find `bl_init_clks()` #4560: make: clang is more pedantic than gcc oonf_api is not building with clang. (Partly solved by #4593) #4694: drivers/lm75a: does not build #4737: cortex-m: Hard fault after a thread exits (under some circumstances) #4822: kw2xrf: packet loss when packets get fragmented #4876: at86rf2xx: Simultaneous use of different transceiver types is not supported #4954: chronos: compiling with -O0 breaks #4866: not all GPIO driver implementations are thread safe: Due to non-atomic operations in the drivers some pin configurations might get lost. #5009: RIOT is saw-toothing in energy consumption (even when idling) #5103: xtimer: weird behavior of tests/xtimer_drift: xtimer_drift randomly jumps a few seconds on nrf52 #5361: cpu/cc26x0: timer broken #5405: Eratic timings on iotlab-m3 with compression context activated #5460: cpu/samd21: i2c timing with compiler optimization #5486: at86rf2xx: lost interrupts #5489: cpu/lpc11u34: ADC broken #5603: atmega boards second UART issue #5678: at86rf2xx: failed assertion in _isr #5719: cc2538: rf driver doesn't handle large packets #5799: kw2x: 15.4 duplicate transmits #5944: msp430: ipv6_hdr unittests fail #5848: arduino: Race condition in sys/arduino/Makefile.include #5954: nRF52 uart_write get stuck #6018: nRF52 gnrc 6lowpan ble memory leak other issues ------------ #1263: TLSF implementation contains (a) read-before-write error(s). #3256: make: Setting constants on compile time doesn't really set them everywhere #3366: periph/i2c: handle NACK #4488: Making the newlib thread-safe: When calling puts/printf after thread_create(), the CPU hangs for DMA enabled uart drivers. #4866: periph: GPIO drivers are not thread safe #5128: make: buildtest breaks when exporting FEATURES_PROVIDED var #5207: make: buildest fails with board dependent application Makefiles #5390: pkg: OpenWSN does not compile: This package still uses deprecated modules and was not tested for a long time. #5520: tests/periph_uart not working #5561: C++11 extensions in header files #5776: make: Predefining CFLAGS are parsed weirdly #5863: OSX + SAMR21-xpro: shell cannot handle command inputs larger than 64 chars #5962: Makefile: UNDEF variable is not working as documented #6022: pkg: build order issue Special Thanks ============== We like to give our special thanks to all the companies that provided us with their hardware for porting and testing, namely the people from (in alphabeticalorder): Atmel, Freescale, Imagination Technologies, Limifrog, Nordic, OpenMote, Phytec, SiLabs, UDOO,and Zolertia; and also companies that directly sponsored development time: Cisco Systems, Eistec, Ell-i, Enigeering Spirit, Nordic, FreshTemp LLC, OTAkeys and Phytec. More information ================ http://www.riot-os.org Mailing lists ------------- * RIOT OS kernel developers list devel@riot-os.org (http://lists.riot-os.org/mailman/listinfo/devel) * RIOT OS users list users@riot-os.org (http://lists.riot-os.org/mailman/listinfo/users) * RIOT commits commits@riot-os.org (http://lists.riot-os.org/mailman/listinfo/commits) * Github notifications notifications@riot-os.org (http://lists.riot-os.org/mailman/listinfo/notifications) IRC --- * Join the RIOT IRC channel at: irc.freenode.net, #riot-os License ======= * Most of the code developed by the RIOT community is licensed under the GNU Lesser General Public License (LGPL) version 2.1 as published by the Free Software Foundation. * Some external sources are published under a separate, LGPL compatible license (e.g. some files developed by SICS). All code files contain licensing information.

kYc0o · 2017-01-11T14:03:25Z

ping! ❄️

miri64 · 2017-01-11T14:39:56Z

Did not find any time to look into it :(

OlegHahm · 2017-01-11T15:45:52Z

I will try to help - maybe at the hack'n'ACK.

RIOT-2016.10 - Release Notes ============================ RIOT is a real-time multi-threading operating system that supports a range of devices that are typically found in the Internet of Things: 8-bit microcontrollers, 16-bit microcontrollers and light-weight 32-bit processors. RIOT is based on the following design principles: energy-efficiency, real-time capabilities, small memory footprint, modularity, and uniform API access, independent of the underlying hardware (this API offers partial POSIX compliance). RIOT is developed by an international open source community which is independent of specific vendors (e.g. similarly to the Linux community) and is licensed with a non-viral copyleft license (LGPLv2.1), which allows indirect business models around the free open-source software platform provided by RIOT. About this release: =================== This release provides a lot of new features as well as it fixes several major bugs. Among these new features are the new simplified network socket API called sock, the GNRC specific CoAP implementation gcoap and several new packages: TinyDTLS, the Aversive++ microcontroller library for robotics, the u8g2 graphic library, and nanocoap. Using the new sock API an implementation of the Simple Time Network Protocol (SNTP) was also introduced, allowing for time synchronization between nodes. New platforms include the Arduino Uno, the Arduino Duemilanove, the Arduino Zero, SODAQ Autonomo, and the Zolertia remote (rev. B). The most significant bug fix was done in native which led to a significantly more robust handling of ISRs and now allows for at least 1,000 native instances running stably on one machine. About 263 pull requests with about 398 commits have been merged since the last release and about 42 issues have been solved. 37 people contributed with code in 100 days. 1006 files have been touched with 166500 insertions and 26926 deletions. Notations used below: ===================== + means new feature/item * means modified feature/item - means removed feature/item New features and changes ======================== General ------- * Verbose behavior for assert() macro Core ---- + MPU support for Cortex-M API changes ----------- + Socket-like sock API (replacing conn) * netdev2: Add Testmodes and CCA modes * IEEE 802.15.4: clean-up Intra-PAN behavior * IEEE 802.15.4: centralize default values * gnrc_pktbuf: allow for 0-sized snips + gnrc_netapi: mbox and arbitrary callback support System libraries ---------------- No new features or changes Networking ---------- + Provide sock-port for GNRC + gcoap: a GNRC-based CoAP implementation + Simple Network Time Protocol (RFC 5905, section 14) + Priority Queue for packet snips + IPv4 header definitions Packages -------- + nanocoap: CoAP header parser/builder + TinyDTLS: DTLS library + tiny-asn1: asn.1/der decoder + Aversive++ microcontroller programming library + u8g2 graphic library Platforms --------- + Support for stm32f2xx MCU family + Low power modes for samd21 CPUs + More Arduino-based platforms: + Arduino Uno + Arduino Duemilanove + Arduino Zero + More boards of ST's Nucleo platforms: + ST Nucleo F030 board support + ST Nucleo F070 board support + ST Nucleo F446 board support + SODAQ Automono + Zolertia remote rev. B Drivers ------- + W5100 Ethernet device + Atmel IO1 Xplained extension + LPD8808 LED strips * at86rf2xx: provide capability to access the RND_VALUE random value register Build System ------------ + static-tests build target for easy local execution of CI's static tests Other ----- + Provide Arduino API to Nucleo boards + Packer configuration file to build vagrant boxes + CC2650STK Debugger Support + ethos: add Ethos over TCP support Fixed Issues from the last release ================================== RIOT-OS#534: native debugging on osx fails RIOT-OS#2071: native: *long* overdue fixes RIOT-OS#3341: netdev2_tap crashes when hammered RIOT-OS#5007: gnrc icmpv6: Ping reply goes out the wrong interface RIOT-OS#5432: native: valgrind fails Known Issues ============ Networking related issues ------------------------- RIOT-OS#3075: nhdp: unnecessary microsecond precision: NHDP works with timer values of microsecond precision which is not required. Changing to lower precision would save some memory. RIOT-OS#4048: potential racey memory leak: According to the packet buffer stats, flood-pinging a multicast destination may lead to a memory leak due to a race condition. However, it seems to be a rare case and a completely filled up packet buffer was not observed. RIOT-OS#4388: POSIX sockets: open socket is bound to a specific thread: This was an inherit problem of the conn API under GNRC. Since the POSIX sockets are still based on conn for this release, this issue persists RIOT-OS#4527: gnrc_ipv6: Multicast is not forwarded if routing node listens to the address (might still be fixable for release, see RIOT-OS#5729, RIOT-OS#5230: gnrc ipv6: multicast packets are not dispatched to the upper layers) RIOT-OS#5016: gnrc_rpl: Rejoining RPL instance as root after reboot messes up routing RIOT-OS#5055: cpuid: multiple radios will get same EUI-64 Nodes with multiple interfaces might get the same EUI-64 for them since they are generated from the same CPU ID. RIOT-OS#5656: Possible Weakness with locking in the GNRC network stack: For some operations mutexes to the network interfaces need to get unlocked in the current implementation to not get deadlocked. Recursive mutexes as provided in RIOT-OS#5731 might help to solve this problem. RIOT-OS#5748: gnrc: nodes crashing with too small packet buffer: A packet buffer of size ~512 B might lead to crashes. The issue describes this for several hundret nodes, but agressive flooding with just two nodes was also shown to lead to this problem. RIOT-OS#5858: gnrc: 6lo: potential problem with reassembly of fragments: If one frame gets lost the reassembly state machine might get out of sync ### NDP is not working properly RIOT-OS#4499: handle of l2src_len in gnrc_ndp_rtr_sol_handle: Reception of a router solicitation might lead to invalid zero-length link-layer addresses in neighbor cache. RIOT-OS#5005: ndp: router advertisement sent with global address: Under some circumstances a router might send RAs with GUAs. While they are ignored on receive (as RFC 4861 specifies), RAs should have link-local addresses and not even be send out this way. RIOT-OS#5122: NDP: global unicast address on non-6LBR nodes disappears after a while: Several issues (also see RIOT-OS#5760) lead to a global unicast address effectively being banned from the network (disappears from neighbor cache, is not added again) RIOT-OS#5467: ipv6 address vanishes when ARO (wrongly) indicates DUP caused by outdated ncache at router RIOT-OS#5539: Border Router: packet not forwarded from ethos to interface 6 RIOT-OS#5790: ND: Lost of Global IPV6 on node after sending lot of UDP frame from BR Timer related issues -------------------- RIOT-OS#4841: xtimer: timer already in the list: Under some conditions an xtimer can end up twice in the internal list of the xtimer module RIOT-OS#4902: xtimer: xtimer_set: xtimer_set does not handle integer overflows well RIOT-OS#5338: xtimer: xtimer_now() not ISR safe for non-32-bit platforms. RIOT-OS#5928: xtimer: usage in board_init() crashes: some boards use the xtimer in there board_init() function. The xtimer is however first initialized in the auto_init module which is executed after board_init() RIOT-OS#6052: tests: xtimer_drift gets stuck: xtimer_drift application freezes after ~30-200 seconds native related issues --------------------- RIOT-OS#495: native not float safe: When the FPU is used when an asynchronous context switch occurs, either the stack gets corrupted or a floating point exception occurs. RIOT-OS#2175: ubjson: valgind registers "Invalid write of size 4" in unittests RIOT-OS#4590: pkg: building relic with clang fails. RIOT-OS#5796: native: tlsf: early malloc will lead to a crash: TLSF needs pools to be initialized (which is currently expected to be done in an application). If a malloc is needed before an application's main started (e.g. driver initialization) the node can crash, since no pool is allocated yet. other platform related issues ----------------------------- RIOT-OS#1891: newlib-nano: Printf formatting does not work properly for some numberic types: PRI[uxdi]64, PRI[uxdi]8 and float are not parsed in newlib-nano RIOT-OS#2006: cpu/nrf51822: timer callback may be fired too early RIOT-OS#2143: unittests: tests-core doesn't compile for all platforms: GCC build-ins were used in the unittests which are not available with msp430-gcc RIOT-OS#2300: qemu unittest fails because of a page fault RIOT-OS#4512: pkg: tests: RELIC unittests fail on iotlab-m3 RIOT-OS#4522: avsextrem: linker sometimes doesn't find `bl_init_clks()` RIOT-OS#4560: make: clang is more pedantic than gcc oonf_api is not building with clang. (Partly solved by RIOT-OS#4593) RIOT-OS#4694: drivers/lm75a: does not build RIOT-OS#4737: cortex-m: Hard fault after a thread exits (under some circumstances) RIOT-OS#4822: kw2xrf: packet loss when packets get fragmented RIOT-OS#4876: at86rf2xx: Simultaneous use of different transceiver types is not supported RIOT-OS#4954: chronos: compiling with -O0 breaks RIOT-OS#4866: not all GPIO driver implementations are thread safe: Due to non-atomic operations in the drivers some pin configurations might get lost. RIOT-OS#5009: RIOT is saw-toothing in energy consumption (even when idling) RIOT-OS#5103: xtimer: weird behavior of tests/xtimer_drift: xtimer_drift randomly jumps a few seconds on nrf52 RIOT-OS#5361: cpu/cc26x0: timer broken RIOT-OS#5405: Eratic timings on iotlab-m3 with compression context activated RIOT-OS#5460: cpu/samd21: i2c timing with compiler optimization RIOT-OS#5486: at86rf2xx: lost interrupts RIOT-OS#5489: cpu/lpc11u34: ADC broken RIOT-OS#5603: atmega boards second UART issue RIOT-OS#5678: at86rf2xx: failed assertion in _isr RIOT-OS#5719: cc2538: rf driver doesn't handle large packets RIOT-OS#5799: kw2x: 15.4 duplicate transmits RIOT-OS#5944: msp430: ipv6_hdr unittests fail RIOT-OS#5848: arduino: Race condition in sys/arduino/Makefile.include RIOT-OS#5954: nRF52 uart_write get stuck RIOT-OS#6018: nRF52 gnrc 6lowpan ble memory leak other issues ------------ RIOT-OS#1263: TLSF implementation contains (a) read-before-write error(s). RIOT-OS#3256: make: Setting constants on compile time doesn't really set them everywhere RIOT-OS#3366: periph/i2c: handle NACK RIOT-OS#4488: Making the newlib thread-safe: When calling puts/printf after thread_create(), the CPU hangs for DMA enabled uart drivers. RIOT-OS#4866: periph: GPIO drivers are not thread safe RIOT-OS#5128: make: buildtest breaks when exporting FEATURES_PROVIDED var RIOT-OS#5207: make: buildest fails with board dependent application Makefiles RIOT-OS#5390: pkg: OpenWSN does not compile: This package still uses deprecated modules and was not tested for a long time. RIOT-OS#5520: tests/periph_uart not working RIOT-OS#5561: C++11 extensions in header files RIOT-OS#5776: make: Predefining CFLAGS are parsed weirdly RIOT-OS#5863: OSX + SAMR21-xpro: shell cannot handle command inputs larger than 64 chars RIOT-OS#5962: Makefile: UNDEF variable is not working as documented RIOT-OS#6022: pkg: build order issue Special Thanks ============== We like to give our special thanks to all the companies that provided us with their hardware for porting and testing, namely the people from (in alphabeticalorder): Atmel, Freescale, Imagination Technologies, Limifrog, Nordic, OpenMote, Phytec, SiLabs, UDOO,and Zolertia; and also companies that directly sponsored development time: Cisco Systems, Eistec, Ell-i, Enigeering Spirit, Nordic, FreshTemp LLC, OTAkeys and Phytec. More information ================ http://www.riot-os.org Mailing lists ------------- * RIOT OS kernel developers list devel@riot-os.org (http://lists.riot-os.org/mailman/listinfo/devel) * RIOT OS users list users@riot-os.org (http://lists.riot-os.org/mailman/listinfo/users) * RIOT commits commits@riot-os.org (http://lists.riot-os.org/mailman/listinfo/commits) * Github notifications notifications@riot-os.org (http://lists.riot-os.org/mailman/listinfo/notifications) IRC --- * Join the RIOT IRC channel at: irc.freenode.net, #riot-os License ======= * Most of the code developed by the RIOT community is licensed under the GNU Lesser General Public License (LGPL) version 2.1 as published by the Free Software Foundation. * Some external sources are published under a separate, LGPL compatible license (e.g. some files developed by SICS). All code files contain licensing information.

kYc0o · 2017-03-15T13:01:35Z

This is not affected by #6627?

miri64 · 2017-03-15T13:02:46Z

I don't see why.

kYc0o · 2017-03-15T13:04:23Z

I got just the impression that grc_mac will forward the packets if they're marked multicast, but I have no knowledge if a packet can be only marked multicast on upper layers.

miri64 · 2017-03-15T13:24:18Z

I got just the impression that grc_mac will forward the packets if they're marked multicast, but I have no knowledge if a packet can be only marked multicast on upper layers.

Yes, there is no broadcast in IPv6, so packets will be marked as multicast. gnrc_mac isn't used at the moment, so the relation of this PR and #6627 is minimal. The flag is for the link-layer set a multicast address based on the network layer. (E.g. in Ethernet multicast addresses for IPv4 and IPv6 are different and the broadcast address is another one, too. On the other hand, IEEE 802.15.4 has no concept for multicast and just broadcasts).

kYc0o · 2017-03-15T14:03:33Z

OK, got it, thanks for the explanation 😄

kaspar030 · 2017-04-21T08:10:43Z

@miri64 is there a chance of fixing this for .04?

miri64 · 2017-04-21T08:25:19Z

Mh, I've only adapted this PR and tbh forgot what this fix was about. The code looks like, if I'm not mistaking, it is supposed to demux all non-link-local multicast packets, which seems a little bit off to me.

kaspar030 · 2017-04-25T06:52:36Z

Ok, then I'll postpone.

kYc0o · 2017-06-30T13:55:36Z

@miri64 is there a chance of fixing this for .04?

Can we ask the same for .07?

miri64 · 2017-06-30T13:58:37Z

Did not put any work into this => still the same situation.

miri64 · 2017-11-06T13:49:04Z

I plan to clean-up GNRC's IPv6 majorly as soon #7925 is merged and will include this with that. So closing this as memo.

gnrc_ipv6: Forward multicast packets addressed to self

bca831b

miri64 added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Area: network Area: Networking GNRC labels Aug 5, 2016

miri64 assigned kYc0o Aug 5, 2016

miri64 force-pushed the gnrc_ipv6/fix/forward-own-mcast branch from 96d4744 to bca831b Compare August 5, 2016 12:54

miri64 mentioned this pull request Aug 5, 2016

gnrc_ipv6: Forward multicast packets even if they are registered with the receiving netif #4528

Closed

miri64 added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Aug 5, 2016

miri64 mentioned this pull request Oct 18, 2016

gnrc_ipv6: Multicast is not forwarded if routing node listens to the address #4527

Open

miri64 added this to the Release 2016.10 milestone Oct 18, 2016

miri64 added the State: WIP State: The PR is still work-in-progress and its code is not in its final presentable form yet label Oct 18, 2016

miri64 mentioned this pull request Nov 7, 2016

gnrc_ipv6: fix UDP issue #5926

Closed

miri64 modified the milestones: Release 2017.01, Release 2016.10 Nov 9, 2016

OlegHahm self-assigned this Dec 8, 2016

miri64 modified the milestones: Release 2017.04, Release 2017.01 Jan 11, 2017

PeterKietzmann mentioned this pull request Jan 31, 2017

gnrc ipv6: multicast packets are not dispatched to the upper layers #5230

Open

kaspar030 modified the milestones: Release 2017.07, Release 2017.04 Apr 25, 2017

kYc0o modified the milestones: Release 2017.10, Release 2017.07 Jun 30, 2017

miri64 closed this Nov 6, 2017

miri64 added the State: archived State: The PR has been archived for possible future re-adaptation label Nov 6, 2017

miri64 deleted the gnrc_ipv6/fix/forward-own-mcast branch November 6, 2017 13:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

gnrc_ipv6: Forward multicast packets addressed to self #5729

gnrc_ipv6: Forward multicast packets addressed to self #5729

miri64 commented Aug 5, 2016

miri64 commented Aug 5, 2016

kYc0o commented Aug 5, 2016 •

edited

Loading

miri64 commented Aug 5, 2016

miri64 commented Aug 5, 2016

miri64 commented Aug 10, 2016

kYc0o commented Aug 10, 2016

kYc0o commented Aug 11, 2016

kYc0o commented Aug 30, 2016

miri64 commented Oct 18, 2016

miri64 commented Oct 31, 2016

miri64 commented Nov 9, 2016

kYc0o commented Jan 11, 2017

miri64 commented Jan 11, 2017

OlegHahm commented Jan 11, 2017

kYc0o commented Mar 15, 2017

miri64 commented Mar 15, 2017

kYc0o commented Mar 15, 2017

miri64 commented Mar 15, 2017

kYc0o commented Mar 15, 2017

kaspar030 commented Apr 21, 2017

miri64 commented Apr 21, 2017

kaspar030 commented Apr 25, 2017

kYc0o commented Jun 30, 2017

miri64 commented Jun 30, 2017

miri64 commented Nov 6, 2017

gnrc_ipv6: Forward multicast packets addressed to self #5729

gnrc_ipv6: Forward multicast packets addressed to self #5729

Conversation

miri64 commented Aug 5, 2016

miri64 commented Aug 5, 2016

kYc0o commented Aug 5, 2016 • edited Loading

miri64 commented Aug 5, 2016

miri64 commented Aug 5, 2016

miri64 commented Aug 10, 2016

kYc0o commented Aug 10, 2016

kYc0o commented Aug 11, 2016

kYc0o commented Aug 30, 2016

miri64 commented Oct 18, 2016

miri64 commented Oct 31, 2016

miri64 commented Nov 9, 2016

kYc0o commented Jan 11, 2017

miri64 commented Jan 11, 2017

OlegHahm commented Jan 11, 2017

kYc0o commented Mar 15, 2017

miri64 commented Mar 15, 2017

kYc0o commented Mar 15, 2017

miri64 commented Mar 15, 2017

kYc0o commented Mar 15, 2017

kaspar030 commented Apr 21, 2017

miri64 commented Apr 21, 2017

kaspar030 commented Apr 25, 2017

kYc0o commented Jun 30, 2017

miri64 commented Jun 30, 2017

miri64 commented Nov 6, 2017

kYc0o commented Aug 5, 2016 •

edited

Loading