Now currently I’m not in the workforce, but in the past from my work experience, apprenticeship and temp roles, I’ve always seen ipv4 and not ipv6!
Hell, my ISP seems to exclusively use ipv4 (unless behind nats they’re using ipv6)
Do you think a lot of people stick with the earlier iteration because they have been so familiar with it for a long time?
When you look at a ipv6, it looks menacing with a long string of letters and numbers compared to the more simpler often.
I am aware the IP bucket has gone dry and they gotta bring in a new IP cow with a even bigger bucket, but what do you think? Do you yourself or your firm use ipv4 or 6?
Mostly I’m scared I’ll write a firewall rule incorrectly and suddenly expose a bunch of internal infrastructure I thought wasn’t exposed.
Cloud infra engineer here.
Answer: I don’t think about it. Nothing fully supports it, so we pretend it doesn’t exist.
That’s exactly my experience with it.
Some certificates are even annoyed by IPv6 and they won’t install until i remove any trace of it from the DNS. This should also pretty much be the only occasion I’m forced to deal with IPv6, instead of glancing over it while working on the server configs.
Which is why “nothing” supports it
Well if you want to be the one who retrofits google cloud to support it more widely, go to town. But I’m sure as hell not going to bother, I have other work to do. And also I don’t work at google.
People still use IPv4 because companies are slow to adopt new technologies. They see it as a huge money drain and if there is not a visible or tangible benefit to it then they won’t invest in it. IPv6 is definitely a growing technology, it’s just taking it’s sweet time. For reference, currently the IPv4 has just under a million routes in the global routing table while IPv6 has ~216K routes. About 5 years ago it was something like 100K for IPv6 and not much has changed for IPv4.
I personally do not like the addressing of IPv6. It’s not just the length, but now you have to use colons instead of period to separate the octets which leads to extra key strokes since I have to hold shift to type in a colon. It’s a minor thing, but when networking is your bread and butter it adds up.
There are also some other concerns with IPv6. Since IPv6 tries to simplify routing by doing things like getting rid of NATing it also opens us up to more remote attacks. It used to be harder to target a specific user or PC that’s behind a NATed IP but now everything is out in the open. I’m sure things will get better as more and more people use it and there will be changes made to the protocol however. It’s just the natural evolution of technology.
I am very surprised to hear your ISP is not using IPv6. Seems like they’re a little behind the times. Unless they just don’t offer it to residential customers, which is still a bit behind the times too I guess.
Iv6 doesn’t try to simplify routing and remove nat. that’s just how things work. Nat is a workaround for ipv4.
Ipv6 is around since 1998. that’s not slow to adopt, at that point it is just plain refusal from some because of the costs you mentionend
Ipv6 does simplify routing. It has less headers and therefore less overheard. IPv6 addressed the necessity of NAT by adding an obscene amount of possible IPs. Removing the necessity of NAT also simplifies routing as it’s less that the router has to do.
Ipv6 as a concept was drafted in the 90s. It didn’t start actually being seriously used until ~2006/7ish.
IPv6 addressed the necessity of NAT by adding an obscene amount of possible IPs
that is correct but doesn’t change the fact that nat came afterwards as a workaround und now the ip stack goes back to it’s roots without a nat workaround.
It didn’t start actually being seriously used until ~2006/7ish.
true but still nowadays it isn’t even slow anymore just refusal
that is correct but doesn’t change the fact that nat came afterwards as a workaround und now the ip stack goes back to it’s roots without a nat workaround.
And the end result is a simplification for routing.
true but still nowadays it isn’t even slow anymore just refusal
That’s just the pace of large scale adoption of new technology. Look at some of the technologies the banking and financial industry uses as an example (ISO 8583 is a great example). ISP’s still support T1 circuits as well.
There are other benefits of NAT, besides address range. Putting devices behind a NAT is hugely beneficial for privacy and security.
NAT is not a security feature. Your firewall blocks incoming traffic, not NAT. It introduces new complexity that now needs to be solved.
In corpo environments you have to struggle with NAT traversal for VoIP communication.
In home networks “smart” devices attempt to solve it with shit like uPnP and suddenly you get bigger holes in your network security than before. You could find countless home network printers on shodan because of this. Even though (or maybe because) they were “behind” NAT.
IPv6 has temporary IPs for privacy reasons. NAT is NOT a firewall. Setting up a real firewall is more secure and gives you more control without things like UPNP and NAT-PMP.
Time isn’t the only factor for adoption. Between the adoption of IPv4 and IPv6, the networking stack shifted away from network companies like Novell to the OSes like Windows, which delayed IPv6 support until Vista.
When IPv4 was adopted, the networking industry was a competitive space. When IPv6 came around, it was becoming stagnant, much like Internet Explorer. It wasn’t until Windows Vista that IPv6 became an option, Windows 7 for professionals to consider it, and another few years later for it to actually deployable in a secure manner (and that’s still questionable).
Most IT support and developers can even play with IPv6 during the early 2000s because our operating systems and network stacks didn’t support it. Meanwhile, there was a boom of Internet connected devices that only supported IPv4. There are a few other things that affected adoption, but it really was a pretty bad time for IPv6 migration. It’s a little better now, but “better” still isn’t very good.
IPv6 has a policy of throwing more address space at stuff to make routing simpler, though.
IPv4 will individually route tiny slices of address space all over the world, IPv6 just assigns a massive chunk of space in the first place and calls it a day.
Repeat after me kids:
NAT 👏 is 👏 not 👏 a 👏 security 👏 feature
I think djb was right, over twenty years ago: The IPv6 mess
The IPv6 designers made a fundamental conceptual mistake: they designed the IPv6 address space as an alternative to the IPv4 address space, rather than an extension to the IPv4 address space.
There was an alternative proposal that was backward-compatible with IPv4, but I’ve forgotten the name now.
Oh man, that would have been so great. Think of all the networking stacks that could have just been silently upgraded. Just some letters/numbers appended to the front or back. If you only get x bytes then prepend with zeroes. Adoption would have been mostly transparent.
Yup. For those that don’t know, that’s essentially how utf-8 works -
forgotten the name
I’m gonna guess… IPv5That wasn’t it. I wanna say “IPvX”, but my web search comes up empty, so it must have been something else.
I think IPv4+ is what you’re thinking of
We turn it off in our office. It doesn’t benefit us.
You could also make the argument that ipv4 through NAT is better for privacy since it obfuscate what, and how many devices are connected to where.
When I was first looking into IPv6, people were talking about how you can self-assign an address by simply wrapping an IPv6 address around your MAC address. But that practice seems to have fallen out of favour, and I’m guessing the reason is, as you say, the whole privacy thing? There’s a lot of pushback these days against any tech that makes it easier to fingerprint your connection.
That was so insane - “we need a unique number, let’s just use the MAC” - it was like people didn’t even think through any of the implications when making ipv6 address schemes.
Similar with the address proposals that ignored the need to minimise the size of core internet routing tables.
That proposal was made when every computer hooked straight into the internet without a firewall. Every device already had a unique IP address that was globally routable and you needed to race to a firewall download page before a scanner would infect your computer (you had about five minutes, much less if you had the network cable plugged in during setup).
The routing table size reduction has always been stupid. The protocol should not be adjusted to help the penny pinchers save on RAM. And the same problem happened to IPv4 a few years ago, because nobody learned their lesson.
With modern IPv6 (say, Windows 7 or later?) IPv6 privacy extensions solve this problem. Basically, you get a whole bunch of addresses. One based on your MAC address so you can port forward/allow incoming connections in the firewall, and then a bunch of rotating random addresses used for outgoing connections. People that know your prefix and MAC address can find your listening PC, but websites won’t get your MAC address.
As for fingerprinting, thanks to NAT slipstreaming you can choose between “video calling software breaks” and “every malicious ad can access any port on your device” or in some extreme cases “every malicious ad can access any device in your network”. Some websites have also been caught scanning IPv4 networks to figure out where your router lives using standard Javascript, so your IPv4 network isn’t any better protected. At least with IPv6 a website can’t take ten seconds to scan 255 addresses and figure out how many devices are on your network!
Noobie question, wouldn’t the ISP decide what your outgoing IPv6 address is? Like they do with IPv4? I mean no matter how many times I restart my router, my public IP remains the same so I always thought it was assigned by them.
They assign a prefix. For IPv4 this is usually a /32, or 1 single address, though it’s possible to assign larger ranges. I’ve seen businesses with a /28 on IPv4 for example.
The end device picks what IP addresses within the prefix are used for what. For instance, the server rack may use three IP addresses, the office one, and maybe the IoT network also gets one.
With IPv6 you should be getting a /56 or a /48. In other words, they pick the first 48 to 56 bits of your IP addresses, basically leaving 80 to 72 bytes for the end device to distribute amongst itself. You could give the first device address one and start counting up if you wanted to, but that’d come with the annoying edge case of needing to track what numbers are already in use. If you like a false sense of control, DHCPv6 is what manages this.
SLAAC (the “everything works by default” approach) requires a /64 (64 bits of local address space), so if you want to do routing (say, attach a wireless access point or a second router) and you don’t want to do IPv4 hacks that hide IP addresses from each other, you need a few networks. That’s why you get 8 to 16 bits of network space, so you can assign 256 to 65536 networks yourself in case you have weird requirements.
If your ISP assigns you 2003:123:def:abc::/48, then you can pick whether you want to assign 2003:123:def:abc::beef:cafe or any random address that starts with the ISP prefix. You have enough space to give every connection of every device on every WiFi network its own IP address every second of the day, but usually addresses are rotated only once per day.
The ISP picking the address range does come with a huge downside, and that’s that you can’t really use internal IP addresses anymore. To fix that, you can set up a so-called ULA. That’s basically a service anywhere on the network that shouts “hey, if you can’t, you can pick any address from fdef:abc:abc:abc::/96”. By default, devices will pick two addresses (one based on the MAC address and a temporary one), and you can use the one based on the MAC address to plug into your local DNS server.
That way, even if you switch ISPs to one that only does IPv4, you can still use a Pi-Hole at fdef:abc:abc:abc::123:456:789 as your DNS server. These ULAs are completely local, so they can’t be reached from the internet.
Though, just to be sure, you should generate a random ULA prefix (there’s an algorithm in the standard, but there are sites to do it for you) just in case you have bad luck and connect to someone else’s wifi who also thought it’d be funny to put devices on fdef:cafe:babe:b00b::/96.
For reference, in the US, Comcast only gives up to a /60 for residential connections. It’s still fine for most use cases, but it does feel a bit like doing a bit of penny pinching when you’re wondering if you have enough /64’s for how your network is going to be set up.
The standards bodies used to recommend /48 as a default and have scaled down to /56. Anything smaller makes sense for stuff like servers but there’s no good reason to do it. I guess penny-pinching is a reason, but it’s not the norm.
If all else fails, hurricane electric will hand out /48s for free, you just can’t use them to watch things like Netflix.
Yeah, fortunately, for my own use cases, /60 is enough, but I can’t think of a good reason for Comcast to not give out /56 since they’re pretty cheap compared to IPv4.
IPv6 has privacy addresses, though. Stuff on my network generates a new random address every day and uses that address for outgoing connections, so you can’t really track individual devices inside my network.
You can just look at what addresses from that range have left the network in any given 24 hour window.
If AAAA is constantly reaching our to aussie.zone one day, and the next day AAAB is reaching out to that address you can pretty easily connect the dots.
But privacy addresses aren’t incremented numbers. And it doesn’t really matter if you can connect the dots, every /64 is the same as a single IPv4 address anyway. Especially for something like Lemmy where the browser will maintain a QUIC connection for ages if you want to track sessions. Besides, you have the session cookies to associate the other end even if they turn off WiFi and move to mobile data.
It fixes must about every gripe I have with IPv4. It closes the hidden security holes NAT introduces. It pretty much configures itself. It allows you to use multiple Xboxes or Playstations within the same network and play online without faffing about! You can also disable the firewall entirely and basically never get scanned because scanning 2^64 addresses to find one computer is infeasible for bots (though you shouldn’t).
The addresses are longer, that’s for sure. But you shouldn’t be remembering those anyway. That’s why DNS exists! If you don’t have a local DNS server for some reason, just use mDNS, every device supports it out of the box. yourcomputersname.local will work in place of an IP address in just about everything since Windows Vista.
IPv6 was severely underdeveloped when the Necromancy Address Translation kept IPv4 usable twenty years ago, but we’re beyond that now. We have been for a while, actually.
Unfortunately, a lot of network people are the type that learned how networks worked in school forty years ago and decided that this is the way things are and they should never change again. That’s how you get things like “TLS 1.3 pretends to be a TLS 1.2 session resumption or half the internet will break” and “only port 80 and 443 are usable on the internet”. They even brought DHCP back when IPv6 works perfectly fine without it! At least Google did the right thing and refused to play ball with that malarkey in Android.
The whole address reserve argument never helped much. Super expensive cloud providers are now charging extra for IPv4 addresses but if you’re using Amazon AWS you’re used to paying through the nose anyway. CGNAT is a much worse problem, with thousands or hundreds of thousands of people sharing the same IPv4 address and basically being forced to solve CAPTCHAs all day because one of their IP coinhabitors has a virus.
As the comments here show, plenty of people can’t be bothered. That’s fine, legacy websites and devices can just use IPv4, that’s the beauty of it.
CGNAT is a feature – organizations tracing an IP back to source have to play bingo with a host of households who may / may not have downloaded that 1 torrent.
If organisations track your IP back, they can get your ISP to give them your contact details. CGNAT doesn’t protect you from carriers and legal means.
Govt, sure. Law firms running sting operations sure as hell can’t
Depends on where you live, I suppose. Here they sure can.
Just annoyed when I need to specify port when using IPv6. Needs to add square bracket to workaround ambiguity of colon is kinda bad. How can they decide to use colon instead of another special character??
I have IPv6 at home, at work, on my phone, and my hotspot. I have them on my websites and servers. IPv6 is everywhere for me. I use it all the time. Most people do and don’t even realize it.
IPv4 still reigns supreme on a LAN, because you’re never going to run out of addresses, even if you’re running an enterprise company. IPv6 subnets are usually handed out to routers, so DHCPv6 can manage that address space and you don’t need to know anything unless you’re forwarding ports on IPv6.
For the Internet, just use hostnames. There’s literally zero reason to memorize a WAN address when it could be an A/AAAA record.
Company currently uses IPv6! For awhile firewall rules kept biting us as we’d realize something worked in ipv4 but not IPv6 but now I forget it’s even a thing really.
I once paid for a vpc host that was exclusively IPv6 and was shocked how many things broke. I was using it for a discord bot and the discord api didn’t even properly support IPv6 …
IPv6 is now twice as old as IPv4 was when IPv6 was introduced. 20 years ago I worried about needing to support it. Now I don’t even think about it at all.
If you’ve never thought about it, there’s a good chance your actually using it. ISPs around the world have been turning on IPv6 for their customers. About half the internet is using IPv6 these days, so there’s a 50/50 chance you’re part of that.
I suspect my cellphone does, but not my work or home internet.
You can always check https://ifconfig.co if you want to be sure.
a teammate implemented it because he thought it would be a good resume project. it added more maintenance work to a lot of pieces, forever. there is no measurable benefit to the business
Both my employer and my home ISP use IPv6 since many years now and so does all my own stuff, it’s wonderfully convenient to have a globally unique address for everything that I connect to the network.
I try to force everything to use IPv6. It’s a huge pain to support IPv4 as a selfhoster. I never had to specify an IP manually, DNS exists for a reason.
IPv6 was “just around the corner” when I was studying 20+ years ago. I kept a tunnel up until the brokers shut down.
I’ve been hosting some big (partly proprietary) services for work, and we’ve been IPv6 compatible for a decade.
My ISP finally gave me native IPv6 earlier this year, which gave me the push to make sure my personal hosting does IPv6 as well. Seems like most big players services support it today. It’s nice to not have the overhead that CGNAT brings.
IPv6 got a bit of a bad reputation when operating systems defaulted to 6to4 translation but never actually managed to work.
A lot of networks were designed with ipv4 and NAT in mind. There really isn’t a cost benefit to migrate all your DHCP scopes, VLANs, Subnets, and firewall rules to IPv6 and then also migrate 1000’s of endpoints to it.
Much cheaper to just disable ipv6 entirely on the internal network (to prevent attacks using a rogue dhcpv6 server etc) and only use ipv6 on your WAN connections if you have to use it.
