From: KeithG <ys3al35l@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH] doc: move EnableIPv6 under Network
Date: Wed, 30 Dec 2020 12:25:32 -0600 [thread overview]
Message-ID: <CAG17S_MDtKWxmWaN0SO7ELS8X7ammR4M6kcDqUbinrzvBBvW+A@mail.gmail.com> (raw)
In-Reply-To: <2bcc7986-92ab-752a-9e5c-0e698ed44e9d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]
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
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 2828 bytes --]
next prev parent reply other threads:[~2020-12-30 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 15:38 [PATCH] doc: move EnableIPv6 under Network Carlo Abelli
2020-12-22 15:37 ` Denis Kenzior
2020-12-27 13:34 ` flokli
2020-12-30 17:35 ` Denis Kenzior
2020-12-30 18:25 ` KeithG [this message]
2020-12-30 18:29 ` Denis Kenzior
2020-12-31 1:17 ` KeithG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG17S_MDtKWxmWaN0SO7ELS8X7ammR4M6kcDqUbinrzvBBvW+A@mail.gmail.com \
--to=ys3al35l@gmail.com \
--cc=iwd@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.