Hacker News Reader

> A /64 can't be subnetted any more (one host, NO VMs!).

Why not directly bind all VMs to laptop's NIC? This way, they can get IP from the same /64 subnet. On firewall, only enable public access to those VMs that are needed.

I do have a home lab, but every VM is directly bridged to NIC and gets its IP from home router. So a single /64 is sufficient for me.

View on HN

Sometimes it's fine to do that, other times it isn't. If you plan to test network topology, firewalls, you can't do that. If you plan to run untrusted VMs, you also can't do that.

I'd use a unique local address network (/32) for this

https://tools.ietf.org/html/rfc4193

That's fine for some scenarios, but in general for my use cases, I wouldn't, because most often I want my VMs to be accessible from the Internet.

At this point I'd argue your case is a bit special and you may need special arrangements. If it is that critical for you to have a gazillion of IoT devices and untrusted VMs accessible from the internet via IPv6, get a /48 tunnel from he.net

To be fair, his special case just works on IPv4, but not on IPv6. So it’s a regression in functionality without the right prefix size.

Reply on news.ycombinator.com