Live data from Hacker News

IPv6-only Network based on Jool

taoshu.in

11–20 of 37 posts

Re: IPv6-only Network based on Jool

#11
NAT64 covers most of the cases. However, in my homelab experiements I very quickly found out that IPv4 literal addresses are a bit problematic for me.

There are ways to fix that with 464XLAT/CLAT, but I never got around to deploying it.

These days I'm just running dual-stack, with no NAT64. I hate NAT with a burning passion, so adding another layer of stateful NAT is a bit of a net negative in my eyes.

Someday I'll go full IPv6 on my home network with 464XLAT. And then I'll realize that some stupid IoT device or something is not CLAT aware. Obviously there are solutions around that too, but they require an intermediate device.

Re: IPv6-only Network based on Jool

#12

Not sure I entirely agree with : "Here is the classical topology of home network." ... "And all the LAN hosts have one /64 IPv6 prefix." Are people really deploying IPv6 like this? Rather than a /64 to a vlan? (Personally, in the home, I'm just using DHCPv6-PD to delegate a different /64 to each VLAN).

Who has multiple VLANs in a home network??

I don't think an average home user even knows what a VLAN is.

This, on the other hand, is Hacker News.

Re: IPv6-only Network based on Jool

#13
The UK IPv6 Council has a bunch of videos on running IPv6-mostly/only networks:

* https://www.youtube.com/@ukipv6council468/videos

This includes at academic institutions where it's basically all BYOD so they have to deal with a more 'random' assortment of systems:

* https://www.youtube.com/watch?v=2B-liebzcOM

And enterprise networks, like Jen Linkova at Google:

* https://www.youtube.com/watch?v=hb98hAb5_W8

Jen also had a presentation recently (2024-11) at RIPE87, "Mission Possible: How Google Plans to Turn Off IPv4!", where they've managed to reclaim 300K IPv4 addresses:

* https://www.youtube.com/watch?v=UTRsi6mbAWM

She's currently co-chair of the IETF IPv6 Maintenance (6man) working group.

Re: IPv6-only Network based on Jool

#14

NAT64 covers most of the cases. However, in my homelab experiements I very quickly found out that IPv4 literal addresses are a bit problematic for me. There are ways to fix that with 464XLAT/CLAT, but I never got around to deploying it. These days I'm just running dual-stack, with no NAT64. I hate NAT with a burning passion, so adding another layer of stateful NAT is a bit of a net negative in my eyes. Someday I'll g…

If you have NAT64, DNS64 and use “IPv6-mostly” option 108 on DHCP, then CLAT will be activated on supporting devices automatically - and then you can turn the dhcpv4 off when you see no leases on it :-)

By now there is a fair amount of material, eg:

https://indico.cern.ch/event/1274792/contributions/5444353/a...

Re: IPv6-only Network based on Jool

#15
See also perhaps "IPv6-mostly on OpenWRT" from RIPE 87:

* https://www.youtube.com/watch?v=GZ6pxh6ukCg

* https://ripe87.ripe.net/archives/video/1136/

* https://ripe87.ripe.net/wp-content/uploads/presentations/8-I...

Ansible roles:

* https://github.com/oskar456/ansible-openwrt-ipv6-mostly

Re: IPv6-only Network based on Jool

#16

Not sure I entirely agree with : "Here is the classical topology of home network." ... "And all the LAN hosts have one /64 IPv6 prefix." Are people really deploying IPv6 like this? Rather than a /64 to a vlan? (Personally, in the home, I'm just using DHCPv6-PD to delegate a different /64 to each VLAN).

Who has multiple VLANs in a home network??

I have my main VLAN, a guest VLAN, and one for any 'smart'/IoT devices that need to connect to cloud services. Each is firewalled from each other and each has its own separate WiFi SSID.

Not just because the IoT devices are prone to attack because they may not get many updates, but also because they often need 2.4 GHz or may only support WPA 2. So my main network can be WPA3 only and 5 GHz only but the other networks are more lenient.

Re: IPv6-only Network based on Jool

#17

Not sure I entirely agree with : "Here is the classical topology of home network." ... "And all the LAN hosts have one /64 IPv6 prefix." Are people really deploying IPv6 like this? Rather than a /64 to a vlan? (Personally, in the home, I'm just using DHCPv6-PD to delegate a different /64 to each VLAN).

Who has multiple VLANs in a home network??

My router configures a VLAN for guest network access, and that's a normal consumer Fritz!Box. I think other brands do the same.

People may not know they're running a VLAN, but VLANs aren't uncommon either.

Re: IPv6-only Network based on Jool

#18
post #8

Not sure I entirely agree with : "Here is the classical topology of home network." ... "And all the LAN hosts have one /64 IPv6 prefix." Are people really deploying IPv6 like this? Rather than a /64 to a vlan? (Personally, in the home, I'm just using DHCPv6-PD to delegate a different /64 to each VLAN).

Or maybe a "classical" (I assume author meant "typical"?) home network does not have multiple VLANs.

Agreed.

But the topology given in the article shows three separate, non-overlapping /64s, one for each host/router. (Although one would assume that the router at least must have an interface in each subnet, even if that's not what the diagram shows).

One might hope these would be on separate VLANs, as overlaying multiple subnets on one VLAN would be a bit iffy. I've not spotted anything in the article other than the diagram to detail interface configs.

Re: IPv6-only Network based on Jool

#20

Earlier quoted context omitted.

Who has multiple VLANs in a home network??

I don't think an average home user even knows what a VLAN is. This, on the other hand, is Hacker News.

HN has a surprisingly low level of network knowledge compared to sites a generation ago (slashdot etc)
Post reply on HN