IPv6 support bugs

I have CoreELEC 20.3-Nexus on a Minix U22-XJ and noticed quite a few problems with the IPv6 support:

1, IPv6 is not enabled by default. While savvy users can turn it on, many users will not know about it. A lot of ISPs use CGNAT, so not having IPv6 by default results not only in a slower connection and greater likelihood of getting banned or hitting per-ip rate limits for that user, but the extra load on the CGNAT gateways caused by streaming videos can impact other users as well.

2, The zeroconf browser can see IPv6-only hosts and services on the LAN, but is unable to mount them (see attached debug log). For dual stack services it only ever connects via legacy IP which is undesirable.

3, Settings/connections/wired on a dual stack network only shows the legacy address and does not show the IPv6 address, on an IPv6-only network no address is shown at all. Wireless is probably the same.

4, Settings/connections/wired/DNS Servers - the input field only allows legacy IP addresses to be entered manually, but it does display the IPv6 nameservers acquired from DHCPv6/SLAAC when running in dual stack mode.

5, Having an IPv6-only connection results in no DNS servers showing up either through the UI or in the /etc/resolv.conf file, despite the fact that the system uses IPv6 nameservers when in dual stack mode. This is likely at least a partial cause of 6 below.

6, When an IPv6-only configuration is in use, attempting to access any URL fails stating the network is offline, despite this the system is still able to download updates, can still be accessed via SSH and command line tools like wget/curl are able to access the same URLs just fine if you add a nameserver back to /etc/resolv.conf.

7, Manually adding an NFS url to an IPv6-only host fails either by IP or DNS. If a dual stack host is entered by name, the connection is always made over legacy IP. Mounting the same NFS share from the Linux shell works over IPv6 without problems.

Debug log: https://paste.coreelec.org/vGYqZN

I doubt there is much users with IPv6. Which means all this is very low priority. Or no priority at all because no one is actually looking this.

Globally around 45% of users accessing google do so using IPv6 whether they realise it or not:

These stats are also much higher among consumers than corporate users, so clearly there are a LOT of users who have IPv6, even if many of them have no idea and don’t notice some of their devices aren’t using it because the ISP provides a degraded fallback to legacy IP.

There are a great many benefits to be had from using IPv6. Bypassing CGNAT gateways being a big one that affects a large number of users.

Lack of IPv6 support in certain devices is a big problem for some too (and having it off by default is just as bad because most users won’t know to turn it on):

For my use case the local ISPs provide 1gbps fibre connections and ALL use CGNAT, so legacy traffic is a lot slower - eg downloading from the big CDNs over v6 i can saturate the line at all times, legacy traffic is often much slower from the same CDN.

But more importantly, my friends and neighbours are also behind CGNAT. We have a few shared media servers between us but it’s only possible to access them over v6 because legacy traffic is behind a NAT gateway controlled by the ISP. Over v6 we can stream from each other at gigabit speeds, legacy traffic we can’t do at all unless we jumped through hoops to rent a server somewhere to proxy the traffic - which would be costly and slow.