Border Router: packet not forwarded from ethos to interface 6 #5539

biboc · 2016-06-10T15:32:49Z

My setup:

Linux with start_network.sh (i.e ethos and uhcpd running)
Border router on samr21
Gnrc_networking node A
Gnrc_networking node B

I run a program that sends 20 UDP packets to my nodes every 20 sec.
After some time, instead of seeing:
got packet from fe80::46:a5ff:fe3d:fc3e port 58493
uhcp: push from fe80::46:a5ff:fe3d:fc3e:58493 prefix=2001:db8::/64
gnrc_uhcpc: uhcp_handle_prefix(): got same prefix again

uhcp client gives:
uhcp_client(): timeout waiting for reply
uhcp_client(): sending REQ...
...
In a loop.

EDIT
I thought it was uhcpd which was buggy but i think it is BR. I tried to ping interface 6 from Linux, no success.
I went deeper, communication goes over ethos and it arrives at

case ETHOS_FRAME_TYPE_DATA:
            if (dev->framesize) {
                dev->last_framesize = dev->framesize;
                dev->netdev.event_callback((netdev2_t*) dev, NETDEV2_EVENT_ISR, dev->netdev.isr_arg);
            }

dev->framesize so callback should be called. I don't know where to debug then?

In the other way, uhcp client (BR) sends data and uhcpd server on Linux receives every packet:
got packet from fe80::221:d3ff:fe60:5a8d port 12345
Then it tries to answer the request but unfortunately like the ping the answer does not go to uhcp client.

What's the problem, why can't Linux communicate to BR anymore?

If I reboot the BR, it works and I see again that uhcp client and server can communicates.
How can I debug it more?

@miri64, I don't know if it is a know issue? But the network crashes somewhere, can you help to debug a bit more? I'm on April release

EDIT:
I enabled DEBUG on gnrc_netdev2.c and gnrc_netdev2_eth.c:
When it works:

gnrc_netdev2: GNRC_NETDEV_MSG_TYPE_EVENT received
gnrc_netdev2: event triggered -> 2
gnrc_netdev2_eth: received packet from 6e:e4:6f:8a:ea:23 of length 118
gnrc_netdev2: waiting for incoming messages

When it does not work:

gnrc_netdev2: GNRC_NETDEV_MSG_TYPE_EVENT received
gnrc_netdev2: event triggered -> 2
gnrc_netdev2_eth: received packet from 6f:8a:ea:23:33:33 of length 86
gnrc_netdev2: unable to forward packet of type 0
gnrc_netdev2: waiting for incoming messages

As you can see the length and address have changed and I remarked that address has been shifted when it is not working. Both call are simple ping.

The text was updated successfully, but these errors were encountered:

miri64 · 2016-07-05T14:42:52Z

So the gist is, somehow everything is 0 if I see that correctly

biboc · 2016-07-05T16:00:51Z

Yes, I only keep ping6 from linux, it works for a while and then it does not work anymore, I see that packets get stopped with gnrc_netdev2: unable to forward packet of type 0

How can I debug more? Can the gnrc_pktsnip_t be corrupted somewhere?

biboc · 2016-07-05T21:15:59Z

What could cause the packet to be malformed every time?

smlng · 2016-07-06T07:12:38Z

could this be related to (or even fixed by) #5596?

biboc · 2016-07-06T07:29:20Z

@smlng, I don't think so, because packet is locked in netdev2 so before ipv6 layer if I'm right?

biboc · 2016-07-06T09:20:23Z

@miri64, any idea on that?

kaspar030 · 2016-07-06T09:51:15Z

What could cause the packet to be malformed every time?

It is possible that ethos' state somehow get's corrupted.

biboc · 2016-07-06T10:14:03Z

@kaspar030, ok, how can I check that? ethos on linux or BR?
I can easily reproduce it by keeping a ping on 2001:db8:: node or even interface 6 on BR

Here is a gist with some more debugs:
https://gist.github.com/bapclenet/2fa3c4185633d827980109aab0003644
You'll see the ping working at the beginning and failing at the end.

biboc · 2016-07-06T13:38:43Z

@kaspar030, on ethos, is there some controls that a packet is correctly arrived on BR before sending a new one?

biboc · 2016-07-06T13:53:43Z

I tried at 9600Baud and with 48MHz or 8Mhz, it does not change, pkt gets corrupted at some point.

Did someone try to continuously ping a node from linux (with Global IP)?

biboc · 2016-07-06T14:38:31Z

In the irq_handler of UART, I checked if I have an error:

static inline void irq_handler(int dev)
{
    SercomUsart *uart = _uart(dev);

    if (uart->STATUS.reg & SERCOM_USART_STATUS_BUFOVF) {
        printf("SERCOM_USART_STATUS_BUFOVF\n");
        uart->STATUS.reg = SERCOM_USART_STATUS_BUFOVF;
    }

And yes BUFOVF is raised each time before it starts to not working

biboc · 2016-07-06T16:24:27Z

I think, I understand the bug, when I constantly ping a node, it sends a ping every 1sec. UHCP sends a request every 1min and if by bad luck uhcp server sends answer at the same time as my ping, Linux being much quicker than samr21, linux sends both message very quickly and RIOT does not have time to deal with them.
It is an assumption, but adding a little delay in the loop in linux ethos helps to not have collision.
The ideal solution would be to have a queue in ethos linux and before sending a new message it should get an ACK from ethos RIOT.
@kaspar, did you think about that when you wrote ethos?

biboc · 2016-07-08T07:55:49Z

Tell me if I'm wrong but the packet sent by serial to netdev is allocated somewhere or it is still allocated in the ringbuffer of ethos? If it is kept in the ringbuffer and a new packet arrives before the other has finished to be transmitted, the packet is overwritten? @kaspar030

kYc0o · 2016-07-26T12:09:32Z

Anyone against to postpone this bug to be solved on the next release?

kYc0o · 2016-07-26T22:28:25Z

Postponed.

biboc · 2016-08-26T15:40:39Z

@kaspar030, have you tried to reproduce the bug?

miri64 · 2016-10-17T12:23:40Z

@kaspar030 ping?

miri64 · 2016-11-08T18:54:40Z

This sounds a little like the analysis given by @Yonezawa-T2 in #5926. @biboc can you check if #6064 fixes this issue for you?

biboc · 2016-11-09T17:24:59Z

I don't think this issue is related because this is more about ethos communication over serial.

biboc · 2016-11-09T17:46:31Z

Did you try to send many packets in a row to see if the communication is still on?

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.

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-04-26T13:12:10Z

#6064 was merged, @biboc can you test if this is still an issue?

biboc · 2017-04-26T15:26:07Z

I'm sorry @kYc0o , I won't be able to test this for now.
I don't think #6064 is related to this bug.
Currently, with a small sleep (50ms) before sending a packet from ethos to BR, there are no problem.
This problem may exist due to hardware configuration and not ethos software so if nobody encounters it, I would vote to close this issue.

miri64 · 2017-11-06T16:11:11Z

Fixed by #7925

miri64 · 2017-11-27T22:42:57Z

@biboc can you test if this is still an issue, now that #7925 is merged?

biboc · 2017-11-28T13:11:00Z

I have no time now to test it unfortunately
This issue is very old and IMO should be removed

miri64 · 2017-11-28T13:17:32Z

I'll try to see what I can do, once I'm through with testing for #5790.

miri64 · 2017-11-28T13:49:14Z

I actually think this was covered in my earlier tests for #7925, unless I'm missing something. But since you @biboc as OP also say it should be closed, I close it now (untested, but pretty confident that it is fixed).

biboc changed the title ~~Border Router: uhcp~~ Border Router: packet not forwarded from ethos to interface 6 Jul 5, 2016

biboc assigned miri64 Jul 5, 2016

OlegHahm added Type: question The issue poses a question regarding usage of RIOT Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Area: network Area: Networking labels Jul 6, 2016

OlegHahm added this to the Release 2016.07 milestone Jul 6, 2016

kYc0o modified the milestones: Release 2016.10, Release 2016.07 Jul 26, 2016

aabadie mentioned this issue Oct 17, 2016

Problems with BR example on Ubuntu 16.04 #5458

Closed

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

PeterKietzmann modified the milestones: Release 2017.01, Release 2017.04 Jan 26, 2017

aabadie modified the milestones: Release 2017.04, Release 2017.07 Jun 21, 2017

aabadie modified the milestones: Release 2017.07, Release 2017.10 Jul 14, 2017

miri64 closed this as completed Nov 28, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Border Router: packet not forwarded from ethos to interface 6 #5539

Border Router: packet not forwarded from ethos to interface 6 #5539

biboc commented Jun 10, 2016 •

edited

Loading

miri64 commented Jul 5, 2016

biboc commented Jul 5, 2016

biboc commented Jul 5, 2016

smlng commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

kaspar030 commented Jul 6, 2016

biboc commented Jul 6, 2016 •

edited

Loading

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 8, 2016

kYc0o commented Jul 26, 2016

kYc0o commented Jul 26, 2016

biboc commented Aug 26, 2016

miri64 commented Oct 17, 2016

miri64 commented Nov 8, 2016

biboc commented Nov 9, 2016

biboc commented Nov 9, 2016

kYc0o commented Apr 26, 2017

biboc commented Apr 26, 2017

miri64 commented Nov 6, 2017

miri64 commented Nov 27, 2017

biboc commented Nov 28, 2017

miri64 commented Nov 28, 2017

miri64 commented Nov 28, 2017

Border Router: packet not forwarded from ethos to interface 6 #5539

Border Router: packet not forwarded from ethos to interface 6 #5539

Comments

biboc commented Jun 10, 2016 • edited Loading

miri64 commented Jul 5, 2016

biboc commented Jul 5, 2016

biboc commented Jul 5, 2016

smlng commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

kaspar030 commented Jul 6, 2016

biboc commented Jul 6, 2016 • edited Loading

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 6, 2016

biboc commented Jul 8, 2016

kYc0o commented Jul 26, 2016

kYc0o commented Jul 26, 2016

biboc commented Aug 26, 2016

miri64 commented Oct 17, 2016

miri64 commented Nov 8, 2016

biboc commented Nov 9, 2016

biboc commented Nov 9, 2016

kYc0o commented Apr 26, 2017

biboc commented Apr 26, 2017

miri64 commented Nov 6, 2017

miri64 commented Nov 27, 2017

biboc commented Nov 28, 2017

miri64 commented Nov 28, 2017

miri64 commented Nov 28, 2017

biboc commented Jun 10, 2016 •

edited

Loading

biboc commented Jul 6, 2016 •

edited

Loading