It's weird. Personally I've yet to make the jump to IPv6 because it seems too complex, doesn't make sense, so I don't want to spend the mental effort learning it when I have no need to switch.<p>However, looking decades back I realise I felt the same way when first learning about and working with networks. Nothing about it is intuitive. It's all complex, until it isn't through repetition and familiarity.<p>That said, I still don't want to spend the mental effort on IPv6 yet. I'll deal with it when I have a need for it.
How does this:<p>> With IPv4, when your router connects to your ISP, you get one public address for the WAN, and you use a picked private address like 192.168.0.0/24 for your LAN. With IPv6, <i>since you want a globally routable address for hosts on your LAN also</i>, you need to ask the ISP for a routable prefix.<p>jive with this:<p>> You want to use these ULA for all your LAN communication. If you want to reach your printer or a media server, put their ULAs in the DNS and not the globally routable one.<p>Why have globally-routable IPv6 addresses if you're not going to use them?<p>I was put off initially by the first quoted paragraph because while the hard-outside-chewy-center security model is not a <i>strong</i> model, it is easy to reason about especially when you have very heterogeneous devices on your home LAN, including ones you don't control the OS of. I <i>like</i> using private addresses for my home LAN and even if I had an IPv4 /24, I wouldn't give addresses from it to machines on my LAN.<p>I use wireguard to access things on my LAN, with a somewhat-janky split-horizen DNS setup where the DNS server is on my LAN, so I have to be connected to wireguard to even resolve the names.
I think there are problems with ULA.<p><a href="https://blogs.infoblox.com/ipv6-coe/ula-is-broken-in-dual-stack-networks/" rel="nofollow">https://blogs.infoblox.com/ipv6-coe/ula-is-broken-in-dual-st...</a><p>I've seen some of that - that said I can't figure out how I'm supposed to do DNS registration with GUA addresses. The only way I know to register addresses in DNS is with DHCP. Should I just have my IPv6 DHCP server advertise the GUA addreses? Is there some other way to do this?<p>I'm actually genuinely confused about this.
Site local is useful to know about, even if it is technically deprecated. I explained it [1] for a test-setup that has no actual IPv6 connectivity.<p>Without a non-link-local IPv6 address, resolvers will often omit IPv6 addresses in their response.<p>Another big difference between IPv4 and IPv6 is in the localhost address scheme.<p>IPv4: 127.0.0.1/8 - 24 bits of free addresses
IPv6: ::1/128 - no free addresses<p>Many people won’t care about this but some local hacks make use the localhost address space for fun and profit.<p>[1] <a href="https://github.com/suntong/dbab/pull/10#issuecomment-1603857583">https://github.com/suntong/dbab/pull/10#issuecomment-1603857...</a>
I'm a home ipv4 admin. What I or someone similar would need is the last part that shows how you set up a basic network with some local addresses I care about and a few I want to expose publicly. It's nice that the guide includes the concepts, but the first thing anyone will want to do is just make it work.<p>Step 2 says to set up ULAs. Are these static or dynamic? It says "don't pick numbers." If dynamic, how does step 5 work? If static, what about visitors in my house?<p>Step 3 mentions a LAN DNS. Where do I set that up? I don't recall my router having that option somewhere, and I'd rather not rely on a machine for it.
> After your router connects to your ISP, the router can ask for prefix delegation.<p>Some providers (eg: Starlink, when I last checked and a Calyx WiFi hotspot) will only advertise a prefix. I was forced to figure out a way to bring the /64 that is in front of my router (Linux iptables) and expose it to a LAN behind my router. It looks something like [1]<p>Depending on your setup, there may be an easier solution.<p>[1] <a href="http://imoverclocked.blogspot.com/2022/05/ipv6-wifi-access-point-nftables-and.html" rel="nofollow">http://imoverclocked.blogspot.com/2022/05/ipv6-wifi-access-p...</a>
If you want to run authoritative DNS on your home network and have AAAA lookups for local machines, how do you go about this? Assign the DNS entry just to the ULA of each host?
Can someone elaborate on this:<p><i>For a given prefix, the interface will always pick the same identifier, (in fact, the eui-64 algorithm will pick the same identifier across multiple prefixes)</i><p>How does the algorithm typically work? Is there a loss of privacy since identifiers are reused across prefixes? If I replace my NIC or install a different OS on my machine will the address change?
I've just got back into building a homelab after a multiyear break. I think I last worked on such a project in 2017. In the time between then and now, I still don't know why I would want to utilize IPv6 on my home network. And my network is necessarily more complicated than most users by extension of the homelab (switches, hypervisors, VM's, etc).<p>I imagine I might be able to go looking for an answer to why I'd want this, but I would have expected the case to have been made casually by now if it had any utility in my home. I never stopped reading technology and computing sites during my sabbatical, though they did become more mainstream. Yet I still have no clue why I'd want this on a home network. This seems like a solution in need of a problem (in the home – I'm not discounting the utility on a global scale).
There are definitely easier ways to get IPv6 if you don't want to deal with the networking.<p>I feel like I'm doing a lot of plugging of IPv6.rs [1], but I guess that's a testament to just how much demand there is for IPv6.<p>[1] <a href="https://ipv6.rs" rel="nofollow">https://ipv6.rs</a>