this post was submitted on 19 Jan 2024
249 points (99.2% liked)
Technology
59534 readers
3195 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ipv6 is the replacement for ipv4. There now exist networks without ipv4
To expand on this, we have functionally ran out of IPv4 addresses. Meaning IPv6 addresses are required.
Not only that, but ipv6 makes networking easier and less complicated. No longer, needing port forwarding or NAT, amongst other improvements
It's that necessarily a good thing?
I remember suddenly needing a firewall on my PC back in the days of the Blaster worm.
Do we really want all those crappy IoT devices open on all ports to the general internet?
NAT is not security. We aren't talking about replacing friewalls.
I'd be fucked if I had to deal with IPv6 at home. Give me NAT, port forwarding and a dynamic public address that changes.
Slaac does everything for you. You get dynamic public addresses that change (you can disable if you please). Nothing to deal with, just open a firewall port if you want to receive traffic
I want static addresses on my LAN, and addresses I can remember and easily recognize in a list. And I don't want my devices to have unique addresses outside my LAN, especially not static ones. NAT is great.
You can statically number a LAN with fd00::/8 and NAT66 to the internet, if you really want to.
Heck you could set up a ULA or just use a range from your assigned prefix
See, what both of you wrote is completely alien and confusing to me. The look of IPv6 gives me an aneurysm. Let me keep my IPv4. You can run IPv6 on your own LAN. I'm not stopping you.
Roughly speaking, fd00::123 is the IPv6 equivalent of 192.168.0.123
It's a little bit unfamiliar, not the end of the world. It's not complicated and not as nuanced as ipv4 networking. No dhcp necessary anymore on your local network, how good is that? No more trying to hardcode MTU, no strict/open/hairpin/fullcone/etc NAT issues because no NAT, no port forwarding, no fear of IP collisions, less overhead, freedom of many public addresses per interface - host each app on its own public IP address if you desire. Ipv4 over ipv6 is part of the spec so you would never lose ipv4 connectivity. I could go on
Oh I'm sure you can do heaps more with IPv6. And that's great. I'm just saying to me it's super complicated because I have to learn everything from scratch, and again those horrendous long and complicated hex addresses. If I can live my whole life without ever having to type or trying to remember an IPv6 address I'll be a happy guy. IPv4 is super clean and easy at least on the level I'm using it. Those negative things you mention, I've never had to deal with any of that. Except port forwarding, but that's easy and honestly I kinda like how that works for some reason.
But sure, you mention some pretty cool things there with IPv6 that could perhaps come in handy even for me at some point when I start doing more advanced things on my network. So I'll keep that in mind for when that happens. And also, I guess I probably should learn more about IPv6 just to have the knowledge for when I might need it, wherever that may be. But ugh... lol
Nothing stops you doing that with ipv6. NAT is complicated and unnecessary.
My brain stops me from remembering and recognizing IPv6 addresses. I can't deal with long strings of hex. And why are people so against me running IPv4 on my own LAN? Do I make you sad? Do I ruin your day? I love IPv4, and NAT works perfectly fine for me. I'm not doing the translation, my router is.
You don't need to have long addresses, you should be using hostnames and domains anyway. Ipv6 addresses are often simpler than ipv4 ones. E.g. prefix::1 for your router. Prefix::2 for the next device, and so on to Prefix::FFFF for the first 65k machines if you wish to set it up that way. Ipv4 exclusively on your lan ruins my day because I have to maintain servers and software to support users that only use ipv4 and flat out refuse ipv6 connectivity - it's expensive and takes a lot of effort to maintain dual stack support.
Most of the time I do use hostnames, but it doesn't matter what I use as a user if I have a list of addresses I have to look through in log files, or enter addresses for configuration or whatever. My brain works on IPv4. I'm sorry for ruining your day, but I assume, or at least hope, that you get paid for the work. I do not and I have more important and pressing things to do than learn IPv6 and reconfigure my whole network.
Only for the internet, not private space
No shit.
But a private Lan will never need it.
There are 4 billion+ possible IP v4 addresses, nearly 600 million in the current private range.
Show me a private network with 600 million devices.
There's no reason a device that doesn't have a direct internet connection needs IP6.
Ideally, using just IP6 would be simpler, as every device gets a global address. Then you don't need to mess with NAT, port forwarding and all that bullshit. Every device having multiple addresses just complicates things.
A device on your private IPv4 network can send packets directly to
104.21.36.127via NAT. How will it send packets to2606:4700:3033::6815:247f? There's not enough space in the IPv4 header.