Programming

17407 readers

75 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

257

Yearly reminder that github still does not have an IPv6 address (2023) (sopuli.xyz)

submitted 1 year ago by Sibbo@sopuli.xyz to c/programming@programming.dev

56 comments fedilink hide all child comments

Try the following:

$ nslookup github.com
[...]
Non-authoritative answer:
Name:   github.com
Address: 140.82.121.3

you are viewing a single comment's thread
view the rest of the comments

[–] orangeboats@lemmy.world 6 points 1 year ago (1 children)

You can't talk about NAT and then mention speed in the same statement...

The 128-bit IPv6 addresses are just four simple 32-bit integers if you think about it, but with NAT you have juggle around and maintain the (internal IP, internal Port, external IP, external Port, Protocol) tuples all the time. That's a significant overhead. Also, switches typically deal with the Layer 2 stuffs. IP is Layer 3.

See the HN discussion for more information.

It's just easier to do IPv4 in every way

Except when you have to NAT transversal. Then you are in a world of hurt.

[–] astral_avocado@programming.dev 2 points 1 year ago

Well, there's the actual engineer response I was looking for