ipv6bot

Firstly, this bug affects [likely] all versions of unraid. If you do a ``docker network inspect bridge`` you will notice it does not have the --ipv6 flag enabled meaning no container will ever be able to make a ipv6 connection. You can test this yourself by running ``docker run -it --rm --network=bridge ping ipv6.google.com`` But you will also notice something peculiar. Something that was unacceptable in 2010, and unheard of post 2012... ``docker run -it --rm --network=host ping ipv6.google.com`` or ``ping ipv6.google.com`` this is assuming of course you have a router / wireless router made after early 2008 and a decent isp. This OS wont latch onto router announcements or DHCPv6 leases. This is unacceptable for any modern operating system, windows XP sp2 can get a ipv6 lease. Setting up a user defined bridge would depend on the docker bridge that is not getting a IPv6 lease. And the host wont get a automatic IPv6 lease from the router. Now, this is a BUG report, not a philosophical debate about the merits of ipv6 in a home networking environment. However, I would like to make some key points to any developers listening on why this is a important feature. (Though there should not be any need for this, it is unacceptable that ipv6 does not work out of the box in this day and age). 1. Not everyone has their own IPv4 that they can open ports on. CGNATs are becoming more common every day. A user could open :80 and :443 on their IPv6 ports. Then you would use a CDN to tunnel up ipv4 traffic, or use a tunnel broker. 2. Most ISP's support this. If you think your ISP does not, they likely do. 3. Most of the time your IPv6 transit providers will be better than your IPv4 transits, because the network hardware required is better. For example if I can get my transit to go through Hurricane Electric it will run really well. If I send IPv6 traffic through my modem my ISP has one IPv6 upstream. This essentially gets all my traffic on my preferred transit. 4. most (good) routers allow you to setup a tunnel broker so even if your isp does not have IPv6 you can get it easily. 5. Its 2010 and some years later. This should work out of the box. Only boomers who listen to 8 tracs or use VHS do not have dual stack networking. Finally I am marking the priority Urgent because it is pretty appropriate for a headless nas not having proper networking support.