On Wed, Dec 30, 2020 at 11:56 AM Denis Kenzior <denkenz@gmail.com> wrote:

> Hi,
>
> On 12/27/20 7:34 AM, flokli(a)flokli.de wrote:
> > Last time I checked, IPv6 RA weren't supported yet. Is this still the
> case? Also, why does it default to `false`?
>
> Correct, IPV6 RAs are not yet supported.  And this is  the reason why IPV6
> is
> disabled by default.
>
> In iwd versions prior to 1.10 you could let iwd setup IPv4 aspects (using
> DHCPv4) and let the kernel handle RAs.  But, really, such a setup was
> broken
> because:
>    - kernel didn't know anything about route metrics to be used by iwd
>    - details obtained from RAs, like DNS, host names, etc were not
> configured
>    - Stateful (DHCPv6) configurations didn't work
>
> Certain setups may have appeared to work, but it was just pure luck.
> Given the
> above, and the fact that iwd's IPv6 support is not yet complete, the
> safest
> option was to disable it by default.
>
> Regards,
> -Denis
>
This is interesting to me. I am using connman and iwd (1.10) and have ipv6
enabled on my home network. On my RPi, the ipv6 addresses are listed:
The /etc/iwd/main.conf lists only:
[General]
UseDefaultInterface=true
NameResolvingService=resolvconf

There is nothing referencing ipv6 in connman's main.conf nor in the psk for
the AP I am using.  Yet, I get these addresses when iwd negotiates the
connection:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.41  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fd21:98c8:1d28:0:ba27:xxff:fexx:xxxx  prefixlen 64  scopeid
0x0<global>
        inet6 fd21:98c8:1d28::41  prefixlen 64  scopeid 0x0<global>
        inet6 2600:1700:4320:6caf:ba27:xxff:fexx:xxxx  prefixlen 64
 scopeid 0x0<global>
        inet6 fe80::ba27:xxff:fexx:xxxx  prefixlen 64  scopeid 0x20<link>
        ether b8:27:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 11056898  bytes 8907204479 (8.2 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3810279  bytes 415445265 (396.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

How should I disable it? Should I?

Keith