I can't get IPv6 in any worthwhile form from my ISP. IMHO IPv6 isn't any more useful than IPv4 if you only have ULA. And NAT is not as well supported since it wasn't intended to even be really necessary for example. So even if you are starting from scratch or just using it internally, there are some disadvantages to implementing it over just sticking with IPv6. But if your ISP actually provides IPv6 it might be worth it as long as your devices all support it. But otherwise you're going to need to set up IPv4 in addition, anyway, so you're just going to create problems for no good reason, IMHO.
Don't use ULA, those are non internet routable addresses so they will never use v6 for internet things. Use the range assigned from your ISP.
SLAAC. Because Android has one ass of a dev who refuses to include DHCPv6
You can use both at the same time and it is useful to have ULA if your ISP changes your assigned prefix.
Blocked by my ISP. So I have it all blocked.
I don't use IPv6 on my lab. They been screaming to the bleachers since like 2010 that IPv6 is right around the corner due to lack of addresses, and I've still seen no real reason to want to adopt for it.
My current provider doesn't even support it... so why should I?
My current provider doesn't even support it...
In what kind of godforsaken backwater do ISPs that don't support IPv6 still exist!?
The largest of the 3 carriers in Canada.
Bell.
Does not support ipv6.
Switzerland, we have the best and worst of both worlds. 25GBit Fiber home connections for less than 100 USD per month and ISPs that only support IPv4.
There are a few ISPs in North America that support ipv6, but many many don't. As much as I detest the recent push toward "5G Internet to the Home", it at least does increase adoption of IPv6 since (from what I understand) basically all mobile carriers are v6-only and do NAT64 for v4 support.
I don't know if that translates to the 5G-at-home offering but it wouldn't surprise me since most customers don't care what address scheme is being used as long as Netflix works.
My setup is a pile of kludges built on top of each other over the last two decades.
I started with ULAs distributed through DHCP, connected to named, which allows hosts do declare their own name and let me access local services as though I had a real domain.
My ISP eventually started supporting IPV6, but only assigned /128, so the ULAs got NAT-6ed out to the real world.
I eventually learned how to request prefix delegation from the ISP and set up SLAAC.
So now, my PIv6 clients have a) their link-local address, b) the ULA, c) a "privacy" SLAAC, and d) a unique SLAAC. All my internal services still refer to the ULAs.
I don't think I'd recommend this system for someone setting up from scratch. The easiest thing would be to go with SLAAC, if you can get prefix delegation, and set your DNS/pihole to send the unique-SLAAC address of any servers you run.
I have that conf: /etc/sysctl.d/01-ipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
But that falls under your exception. It seems to me that IPv6 causes more problems than it solves.
I mean, you can get rid of NAT and subnet your systems in a logical fashion. That's pretty awesome.
You can subnet logically with IPv4.
If you go IPv6 on the internal network you 'win' not having NAT, and exposing all your intrrnal services to the net (which... just why?), but lose the ability to do redundant ISPs/failover/loadbalancing, policy based routing, VPNs... Unless you do IPv6 address translation. Which puts you back to "IPv4+NAT, except more complicated."
IPv6 inside the firewall is more or less entirely pointless.
I use IPv6 local only. Everything else is IPv4. Reason being, my commercial VPN does not support IPv6 and I have reservations about leakage. My ISP already ships with IPv4 & IPv6.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!