&gt; With the reality of v6 being so dramatically different, I have on about three separate occasions sat down to try to understand what I need to do in order to have v6 on my home network and each time I just give up after a few hours of reading.<p>I don&#x27;t mean to offend you, but I think that that suggests that you don&#x27;t understand IPv4 either.<p>IPv6 isn&#x27;t really all that different from IPv4--with one major exception: All of the workarounds for the shortcomings of IPv4 that dominate local networks nowadays are not needed anymore, actually making networks so much simpler again.<p>Now, many people who have learned IP networking in such environments in the last ten years or so (and I suspect you are one of those) seem to think that those workarounds are what defines IPv4 and then are confused by IPv6&#x27;s lack of those workarounds, thinking that those are missing features.<p>Maybe you think that your &quot;internal network&quot; is in some way fundamentally different from &quot;the internet&quot; and that a router is a device that connects those two to give your local network &quot;access to the internet&quot;? That is a common misunderstanding caused by NAT. The internet without NAT, be it IPv4 or IPv6, doesn&#x27;t know any distinction between &quot;internal&quot; or &quot;external&quot; networks. It is all one network, the internet. Your LAN is not somehow &quot;connected to the internet&quot;, it is itself part of the internet. Your home router (without NAT) is no different in function than any other router on the internet: It is connected to more than one transmission medium and thus allows devices on one medium to reach devices connected to another medium, possibly transitively through yet another (series of) routers. And it&#x27;s completely symmetrical in that regard: It allows devices on your LAN to send packets to devices outside your LAN (say one of Google&#x27;s webservers), but equally allows devices outside your LAN to send packets to devices on your LAN (say a webserver on your laptop).<p>So, the most important thing you may have to completely unlearn is the idea of &quot;private addresses&quot; and &quot;NAT&quot; and &quot;port forwarding&quot;. You don&#x27;t get one address from your provider, you get a huge subnet with quadrillions of addresses that you can use to assign addresses to your devices, similar to the early days of IPv4. Your laptop gets an IPv6 address that is no different in function than the IPv6 address of Google&#x27;s webserver.<p>Other than that, details and terms differ, but the general concepts of IPv6 aren&#x27;t all that different from IPv4. ARP is now NDP, DHCP is now SLAAC (or maybe still DHCPv6 if you like), ...<p>Now, if you think that it seems problematic to have &quot;public addresses&quot; on your &quot;private network&quot;: It&#x27;s not, that&#x27;s purely psychology. Yes, a stateful packetfilter at boundaries to other, non-trustworthy, networks might still be a good idea, just as with IPv4, whether you were using NAT or not. If anything, having one global address space makes things much less complicated, and thus more difficult to screw things up.<p>Once you get the hang of it, you will love it and start wondering why you ever considered NAT a reasonable idea. Ever had the problem that you had multiple machines behind a NAT offering the same service that you needed to access from the outside, so you had to put one of them on a different port on &quot;the public address&quot;? Ever tried to access a port-forwarded service from the network behind the NAT and had it either fail because of lack of hairpin NAT, or it was slow because of the bottleneck that was the hairpin NAT? All those problems simply vanish, never to return.