this post was submitted on 16 Aug 2025
571 points (93.1% liked)
linuxmemes
26793 readers
760 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've encountered way too many administrators and network admins who swear that "IPv6 does nothing but cause trouble" but the truth is, the trouble it's causing is because you can't half-implement IPv6. You either roll it out to the whole network or you don't, and the longer you kick that can down the road the harder it's going to be.
Basically too many professionals who haven't learned a new technology since 2005 and refuse to try new things keep holding the world back
Can't even attempt to learn it if my ISP won't provide addresses though.
Not been able to use it to even try, but doesn't IPv6 not have subnets at all? No 192.168.1.1 on your local network with a different public facing 85.136.52.142 (and with NAT444 you also have ISP facing 10.183.23.6). So does your ISP provide you a range of IPv6 addresses?
Correct, the ISP would assign you a /56 of public IPs that all share a prefix which you can slice and dice into however you see fit. All devices receive a publicly routable IP which your router/firewall would limit access to. So no running out of IPs ever, no network/IP collisions if you have to connect to another private network, etc.
A single IPv6 prefix has 2^64 addresses
Why can't you just use it on your local network? Don't need ISP for that.
I will happily enable and use it once doing so doesn't break any of my connectivity.
I'm not managing an enterprise network, it's just my home, but my ISP doesn't support IPv6 so that's one extra layer of complexity right off the hop. On top of that internal services switch which previously required no manual configuration just seem to randomly not work.
IPv6 is not going to see widespread adoption unless it can be implemented completely transparently for the end user, full stop.
IPv6 is widely adopted
I don't even have an ipv6 address, my ISP doesn't provide them yet. Not much to do about it then lol.
You can maybe change ISP
I wish I could but I'm afraid it's not possible at this address and it's not something I'm going to move for
I think what those admins really mean to say is "We don't need any of the benefits of IPv6, so IPv4 works just fine and making the large scale change is trouble.", when you already got your DHCP, NAT, Firewall and stuff up and things do work as expected then you don't really need NDP or SLAAC.
The issue for me is when I have it enabled and try to connect to a site that doesn't support it fully (same thing / half assed) and the site doesn't work properly. For home its my wife and kids that complain, when its the office then everyone complains. I get the blame for failed connections or things not working right when a fully compliant IPv6 site works just fine.
Now I am not perfect so It could be me but I have read up and learned as much as possible. No expert but I did deploy DHCPv6 in a test environment. However there is no reason as of yet to deploy DHCPv6 locally since the address space is so wide. Just saying Its possible that the issue is me but from my understanding its like the U.S.A. switching to metric. Parts of us tried it but others didn't and thus we failed as a giant group.
I think there needs to be a big ass push and force everyone to switch as the same time. I know some of the old devices may not work however those devices have to be 20+ years by now.
If it ain't broke...
^ the admin holding the entire world back
Imagine arguing that 'solutions' like NAT444 isn't broke as fuck
Well... yeah, why wouldn't that be "broke as fuck"?
I always bring it up when the network is experiencing problems that they wouldn't have with IPv6. Running out of IPs in a given scope, increasing costs of public IPs, etc.
"IPv4 is running out of IP addresses so therefore every local network needs to move to IPv6" is a full clown move.
IPv6 is literally designed to solve the scalability issues with IPv6
First of all, enterprises usually have at least one public IP (the one I work at right now has more public IPs than they have server VMs)
Secondly enterprises have big enough and complex enough networks to see other benefits of IPv6. For example IPv4 has some problems when broadcast domains are too large, so your internal network sizes are artificially limited when following best practices. Without private networks you don't have to worry about IP collisions between different private networks that you have to route between (comes up more than you'd think!) etc etc.