da_cow (she/her)Just do it.
lmr0x61Holy shit, year of the IPv6??
(I know this was 2025)
r00tyThe thing is. Any year can be the year of IPv6. Google is on ipv6, youtube is on ipv6, facebook is on ipv6. Pretty much every datacentre I've used (OK limited to Europe) give you IPv6 for free by default. Deploying a web site to be IPv4 and IPv6 is trivial and people that use automation should be able to quite easily apply ipv6 to those scripts.
It's really just the ISPs (more so in the US as I understand it), lazy IT people and the FUD myths holding us back at this point.
django
carrylex
RustyNova
ReznikIPv6. No. Badly configured IPv6 routers, yes. But that's something that would fix itself if it became the only protocol in use. And most routers now are pretty good at it from what I've seen. But it used to be the case it was easy to find bad routers.
The myth seems to be that NAT provides security. But a good default configuration for consumer routers would give the same security as NAT while providing the advantages and extra security IPv6 provides.
IPv6 usually has privacy extensions enabled. Which means it will generate throwaway IP addresses that rotate regularly for your outgoing connections, these IPs do not accept incoming connections. So someone cannot nmap you to find open ports based on the IP you connected to their server with.
Not to mention that most ISPs give each user more IPs than the whole IPv4 internet has. So, port scanning an entire /64 is not going to be fun.
Good points, the difference being NAT crossing requires something on the inside to enable it, while IP6 security requires the consumer router to be properly configured.
And I disagree with the assumption that badly configured routers wonât exist if IP6 were the default. Bad design doesnât magically go away.
The bottom line is small LANs donât benefit from IP6 today. Large LANS donât benefit because they already have extensive IP4 configuration in place, and attempting to migrate is costly, risky, and without a clear benefit to offset those costs and risks.
Most likely enterprises may use 6 on new networks, but even that is questionable when so many extant products still rely on 4 - you donât want to create a problem for those systems.
In one word: no. In more words: some addressing methods can lead to privacy and security issues, but those arenât widely used anymore.
IPv6 addresses can be assigned to interfaces by several systems. One of those is SLAAC, or stateless address auto-configuration (comparable to APIPA and the 169.254.0.0/16 address space for IPv4). One method by which it generates globally unique routable addresses is by inserting the interfaceâs MAC address into the IPv6 address. Since IPv6 generally doesnât use network address translation (and thus no masquerading), this would advertise your computerâs MAC address to the whole internet. More recently, SLAAC uses pseudorandom temporary (or âprivacyâ) addresses for interfaces, together with a unique network prefix assigned to the customer (analogous to the single public IPv4 address).
Itâs also possible to assign IPv6 addresses statically or by using DHCPv6.
In theory, no.
In practice, yes.
I Cast FistNo idea if it was this one, but I find it amusing
OpenStars
SeductiveTortoiseWell, thatâs how I abacus from now on.
đ¸đđđLess. Than. 1MB. Linus has spoken!
jballs
Boomer Humor DoomergodOh boy I canât wait to tell my parents to go to fff8::ab298:42cab3:187daq::1 to get to their router.
Unless itâs not and then we get alphanumeric soup
Itâll have a QR code printed on it.
That wonât take you to the routerâs web server.
Itâll take you to the play store to download the app. Which requires Play Services and access to your exact location, contacts, storage, call history and messages, just to set up your router.
That wonât take you to the routerâs web server.
Itâll take you to the play store to download the app. Which requires Play Services and access to your exact location, contacts, storage, call history and messages, just to set up your router.
Well you could accept the default generated one, or set it to fe80::1 manually. Don't most good routers now have a DNS server in? So you could make it router.local or something?
I think some even by default make a DNS entry call router.local or similar pointing to themselves. This isn't a real problem and if IPv6 were adopted fully, then all routers would likely come with something like this setup anyway.
DNS never has problems and always works. /s
And neither does DHCP.
mDNS (.local) is a fairly new thing, and not everything supports it well unfortunately.
Tbh, ipv4 is probably just a random string of nonsense to them anyways
IPv4 looks a lot like a phone number, which theyâre used to.
JackbyDevshort somewhat typeable, after 5 retries of âYou know what a fucking period is, donât you???â tech support.
I hate IPv6 so fucking much.
I had to write an address validator and sanitizer once. Never again what the fuck were they thinking with the short forms?
I do like having a lot more addresses, thatâs great. The short forms, embedded ipv4, bridges, etc are confusing as hell. Oh, also, you have to add that all to your email validator script, enjoy!
Magistertrue, sometimes I use 127.1 instead of 127.0.0.1 and I have some coworkers that donât know the 0 is optional and are wtf.
Is this for real
WhiteOakBayouIt is real. The missing spots are filled with zeros so it works out the same.
talYes. Now try 0177.0x1.
Iâm pretty sure that IPv4 address formats are more complicated than IPv6 forms, if you are actually doing RFC-compliant validation.
Iâm gonna stick with DNS
Youâve got traditional DNS (which most things other than your web browser are probably using right now), mDNS (which your system is probably set up to use right now â try reaching another host with a configured hostname on your local network by that), DNS-over-HTTP (which your web browser is probably set up to use), DNS-over-TLS, DNSSEC, and the not-DNS-but-also-part-of-name-resolution /etc/hosts, /etc/nsswitch.confâŚ
Email verification is the validator! Just send that sucker.
So youâre now scared of :: padding oh no.
Also why are you writing an address validator yourself? Shouldnât be there like a bazillion libraries by now? xD
This was like 10 years ago and there wasnât an option that could be used with the system. I canât remember why
thisbenzingringwe can thank the cell phone industrys use of IPv6 in the cell network for saving IPv4 for everyone else
Does anyone have some kind of beginnerâs guide to transition a home network from v4 to v6? Everything I found is way too technical.
Asking here but feel free to direct me to a more appropriate sub
Meh, it doesnât really offer anything for a home network.
And this is why it really hasnât be adopted even by business - thereâs already a network in place that works. Migrating to 6 doesnât offer any meaningful benefit to balance the effort and risk of the change.
Now if youâre an SMB with 3 servers and a handful of computers, would you spend what little IT money you have making this change?
And if youâre an enterprise with a thousand servers and tens of thousands of users, are you making this change?
Imagine the cost of reconfiguring routers, and the outages youâd experience doing this.
Thereâs just no pressing urgency to change, and LOTS of cost and risk to do so.
ikiddAnd if youâre in a larger company, youâre the guy or team that gets blamed for every. goddamn. network. problem. that happens after the transition.
Fuck that.
gizmonicusThis is why, when I want to rile up the networking folks, I send a calendar invite that says âIPv6 transition update?â and hide under my desk.
Youâre already doing great if you just donât disable IPv6. Bonus points if your ISP and your router supports proper dual stack IPv4 + v6, then you can actually connect to the internet using v6! Also, fun fact: the original Nintendo Switch does not support IPv6 at all. Pretty much all other non-ancient consumer stuff should be fine. Check your clients IP address assignments, maybe youâre already using IPv6.