[riot-notifications] [RIOT-OS/RIOT] usb: fails to respond ro ping when used with 802.15.4 (#12002)

chrysn notifications at github.com
Wed Sep 18 13:10:33 CEST 2019

Going through the issue now that I have good terminal usability, I can confirm that following the tutorial did solve my issues with USB ethernet and nimble IPSP; adding the `gnrc_sixlowpan_border_router_default` (`…6lowpan_router…` was insufficient, as was `gnrc_ipv6_router_default` alone which gets pulled in by `…border_router…`) module made the difference.

The difference between working and non-working setups was that in the non-working cases, all addresses the USB interface got were always tentative (even with prefix delegation) and thus not used, whereas in the working cases they were `VAL`id (as were the other interface's addresses in the non-working cases).

<details><summary>ifconfig's output on the USB interface when NetworkManager IPv6 forwarding is active and another interface is present</summary><p>

    Iface 11  HWaddr: CA:63:71:D5:F4:A4 
              L2-PDU:1500 MTU:1500  HL:64  Source address length: 6
              Link type: wired
              inet6 addr: fe80::c863:71ff:fed5:f4a4  scope: local  TNT[1]
              inet6 addr: 2a02:1234:abcd:8016:c863:71ff:fed5:f4a4  scope: global  TNT[1]
              inet6 group: ff02::1

@bergzand, can you confirm that it is expected behavior to require a router module in the presence of two network interfaces for link-local addresses on at least one of them to come up? (Because I don't think so, and that would make the approved solution here a workaround rather than a fix.)

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190918/763c4ad3/attachment.htm>

More information about the notifications mailing list