this post was submitted on 19 Jun 2024
313 points (85.6% liked)

Programmer Humor

19623 readers
96 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 

Today in our newest take on "older technology is better": why NAT rules!

you are viewing a single comment's thread
view the rest of the comments
[–] gratux@lemmy.blahaj.zone 27 points 5 months ago* (last edited 5 months ago) (37 children)

Yes, but why would you want to? We have enough addresses for the foreseeable future.

[–] jlh@lemmy.jlh.name 15 points 5 months ago* (last edited 5 months ago) (18 children)

1:1 stateless NAT is useful for static IPs. Since all your addresses are otherwise global, if you need to switch providers or give up your /64, then you'll need to re-address your static addresses. Instead, you can give your machines static private IPs, and just translate the prefix when going through NAT. It's a lot less horrible than IPv4 NAT since there's no connection tracking needed.

This is something I probably should have done setting up my home Kubernetes cluster. My current IPv6 prefix is from Hurricane Electric, and if my ISP ever gives me a real IPv6 prefix, I will have to delete the entire cluster and recreate it with the new prefix.

[–] Thiakil@aussie.zone 7 points 5 months ago (17 children)

It should only be needed if your ISP is brain-dead and only gives you a /64 instead of what they should be doing and also giving you a /56 or /48 with prefix delegation (I.e it should be getting both a 64 for the wan interface, and a delegation for routing)

You router should be using that prefix and sticking just a /64 on the lan interface which it advertises appropriately (and you can route the others as you please)

Internal ipv6 should be using site-local ipv6, and if they have internet access they would have both addresses.

[–] Thiakil@aussie.zone 2 points 5 months ago (1 children)

And if you want static ips either use dhcp6 or disable the randomisation of eui64 addresses

[–] jlh@lemmy.jlh.name 2 points 5 months ago (1 children)

I have static IPs for my Kubernetes nodes, and I actually use DHCPv6 for dynamic dns so I can reach any device with a hostname, even though most of my devices don't have static IPs.

The issue is those static IPs are tied to my current ISP, preventing me from changing ISPs without deleting my entire Kubernetes cluster.

[–] Thiakil@aussie.zone 1 points 5 months ago

It certainly looks like you can give it a prefix to assign out, possibly even multiples

load more comments (15 replies)
load more comments (15 replies)
load more comments (33 replies)