[riot-notifications] [RIOT-OS/RIOT] gcoap example request on tap I/F fails with NIB issue (#8199)

Alexandre Abadie notifications at github.com
Wed Mar 27 14:41:26 CET 2019


I'd like to mention that I'm facing the same issue between a Raspberry PI with 801.15.4 enabled and which is propagating an ULA prefix (fd00:ab:ad:1e::/64).
- I'm running gcoap example on a samr21-xpro: the IPv6 address is correctly configured with one link-local address and one ULA address.
```
> ifconfig
2019-03-27 14:36:23,618 - INFO # ifconfig
2019-03-27 14:36:23,623 - INFO # Iface  7  HWaddr: 6b:82  Channel: 26  Page: 0  NID: 0x23
2019-03-27 14:36:23,628 - INFO #           Long HWaddr: 79:65:34:58:ec:de:6b:82 
2019-03-27 14:36:23,635 - INFO #            TX-Power: 0dBm  State: IDLE  max. Retrans.: 3  CSMA Retries: 4 
2019-03-27 14:36:23,641 - INFO #           AUTOACK  ACK_REQ  CSMA  MTU:1280  HL:255  IPHC  
2019-03-27 14:36:23,644 - INFO #           Source address length: 8
2019-03-27 14:36:23,647 - INFO #           Link type: wireless
2019-03-27 14:36:23,652 - INFO #           inet6 addr: fe80::7b65:3458:ecde:6b82  scope: local  VAL
2019-03-27 14:36:23,659 - INFO #           inet6 addr: fd00:ab:ad:1e:7b65:3458:ecde:6b82  scope: global
2019-03-27 14:36:23,662 - INFO #           inet6 group: ff02::1
2019-03-27 14:36:23,663 - INFO # 
```
- on the raspberry pi, I have this:
```
$ ip addr show lowpan0
4: lowpan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN group default qlen 1
    link/6lowpan 18:c0:ff:ee:1a:c0:ff:ee brd ff:ff:ff:ff:ff:ff:ff:ff
    inet6 fd00:ab:ad:1e::1/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::1ac0:ffee:1ac0:ffee/64 scope link 
       valid_lft forever preferred_lft forever
```

Then, when I try to get a CoAP resource on the board with aiocoap-client, I have the following message and the request hangs:
```
$ aiocoap-client coap://[fd00:ab:ad:1e:7b65:3458:ecde:6b82]/.well-known/core
WARNING:coap:Received Type.ACK from <UDP6EndpointAddress [fe80::7b65:3458:ecde:6b82%lowpan0]:5683 with local address>, but could not match it to a running exchange.
```

It works if I use:
```
$ aiocoap-client coap://[fe80::7b65:3458:ecde:6b82%lowpan0]/.well-known/core
</cli/stats>,</riot/board>
```

By bisecting, I found that 55adbee48808bda975dd5ee420c605bbddf4c94c is the culprit.

-- 
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/issues/8199#issuecomment-477159622
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190327/4ff1da50/attachment.html>


More information about the notifications mailing list