Hi,
will do that.
Just to make sure I'm understanding things correctly:
RIOT does solicit stateless IPv6 addresses by sending RS, and the BR
should reply with RA. This is part of SLAAC. I have the nagging feeling
that OpenWRT messes up SLAAC on all it's interfaces somehow.
Before switching to Raspbian, I'll do another round of OpenWRT with a
sniffer but will leave odhcpd handling just RAs and will disable dhcpv6
so I make sure I'm just using SLAAC/RA/NDP. After a node solicits an IP
will proceed to neighbor soliciting, right?
Please let me know if my understanding is correct about this.
Thanks
--ilf
On Wed, Jan 17, 2018 at 7:24 PM, smlng <[email protected]> wrote:
Hi again,
On 17. Jan 2018, at 17:14, Iliyan ILF Stoyanov
<[email protected]> wrote:
thanks for the reply. I'm using openwrt as a BR distro with odhcpd
handling the RA (and also dhcpv6). The setup works between a Pi-Pi
(although my second Pi in the PAN uses dhcpv6 for getting an IP, so
that is not a proof of a working solution so far.
you could try to use one of your boards as a sniffer, see [1]. So you
can check if you see
Router Solicitations (RS) by RIOT nodes and hopefully Router
Advertisements (RA) from your
RasPi. RIOT needs RAs to (auto) configure its IPv6 interfaces with
addresses, there is no
DHCP client on RIOT (yet).
Thus, if odhcpd does not send RAs or if it does, these RAs may
contain options RIOT does not
except (e.g., as Kaspar already said on-link flag must not be set),
in all cases auto-conf
may fail in RIOT.
[1]: https://github.com/RIOT-OS/applications/tree/master/sniffer
Best,
Sebastian
_______________________________________________
users mailing list
[email protected]
https://lists.riot-os.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.riot-os.org/mailman/listinfo/users
