We don't talk about IPv5
-
Just my perspective as a controls (SCADA engineer):
I work for a large power company. We have close to 100 sites, each with hundreds of IP devices, and have never had a problem with ipv4. Especially when im out in the field I love being able to check IPs, calculate gateways, etc at a glance. Ipv6 is just completely freaking unreadable.
I see the value of outward-facing ipv6 devices (i.e. devices on the internet), considering we are out of ipv4s. But I don't see why we have to convert private networks to ipv6. Put more bluntly: at least industry, it just isn't gonna happen for decades (if it ever does). Unless you need more IPs it's just worse to work with. And there's a huge amount of inertia- got one singular device that doesn't talk ipv6 at a given generation site? What are you supposed to do?
90% of industrial devices are still 100 Mbit/s.
-
That's nothing that can't be done with a good set of firewalls on IPv6.
This is equipment that uses all statically addressed devices. And ignoring the fact that IPv6 is simply unsupported on most of them, there are duplicate machines that share programs. Regardless of IP version you need NAT anyway if you want to be able to reach each of the duplicates from the plant network.
-
Nah. You're just too stupid to understand the internet is designed to be used with DNS. The people who design these protocols and operate the networks that form the internet have no issues with DNS and don't care that you don't understand.
-
This post did not contain any content.
I'm surprised by the comments here. I use 90% IPv6. For me v4 is only present for retro compatibility. The transition was hard however.
-
90% of industrial devices are still 100 Mbit/s.
I mean that's of the ethenet capable ones... a huge chunk are still serial
-
I'm surprised by the comments here. I use 90% IPv6. For me v4 is only present for retro compatibility. The transition was hard however.
Was?
It's still in progress..
-
I mean that's of the ethenet capable ones... a huge chunk are still serial
And the rest are pure analog
-
This post did not contain any content.
My favorite thing to use IPv6 for is to use the privacy extension to get around IP blocks on YouTube when using alternative front ends. Blocked by Google on my laptop? No problem, let me just get another one of my 4,722,366,482,869,645,213,696 IP addresses.
I have a separate subnet which is IPv6 only and rotates through IP addresses every hour or so just for Indivious, Freetube and PipePipe.
-
CGNATs suck ass though, I had to buy a vps just to access my own network outside my home.
I've recently changed isp and am now hitting CGNAT problems. I have been running Nextcloudpi for years and now I can't access it from outside.
I've trying to understand if I can fix the problem using IPv6 but from what you've said I'm now wondering if a vps is the solution? -
90% of industrial devices are still 100 Mbit/s.
You'll be lucky if you find ethernet on them. RJ45 serial is still pretty common nowadays
-
I've recently changed isp and am now hitting CGNAT problems. I have been running Nextcloudpi for years and now I can't access it from outside.
I've trying to understand if I can fix the problem using IPv6 but from what you've said I'm now wondering if a vps is the solution?My ISP doesn't properly support IPV6, otherwise it should work. I use wireguard to route just my server traffic to the vps.
-
My favorite thing to use IPv6 for is to use the privacy extension to get around IP blocks on YouTube when using alternative front ends. Blocked by Google on my laptop? No problem, let me just get another one of my 4,722,366,482,869,645,213,696 IP addresses.
I have a separate subnet which is IPv6 only and rotates through IP addresses every hour or so just for Indivious, Freetube and PipePipe.
Could you link the privacy extension in question I haven't heard of it
-
Everyone having a static IP is a privacy nightmare.
There's a reason the recommendation in the standard for ipv6 had to be amended (it whatever the mechanic was) so that generated local suffixes aren't static. Before that, we were essentially globally identifiable because just the second half of your v6 address was static.
IPv4 centralization creates far more privacy issues than everyone having a static IP. The solutions are still things like VPNs and onion routing.
-
not sure if you are joking, but any valid IP4 address starting with 127. does the same thing, loopback. 127.0.0.1 is just the standard most people use, you could use 127.127.127.127, or 127.1.1.1 or any random numbers 0 and 254 for the second 2, and 1 and 254 for the last and the effects will be identical.
In fact, it's so standard that there's a bunch of shitty code out there that thinks 127.0.0.1 is the only loopback address.
I'm thinking of a networked Chinese laser cutter that we put on our 10.0.0.0/16 network in the makerspace. It seems to think that 10.0.1.1 and 10.0.2.1 are on different networks. Wouldn't be surprised if it does a similar mistake with loopback addresses.
-
Was?
It's still in progress..
In progress?
I can't even get an IPv6 address, even if I wanted to pay an obscene amount for a business tier.
-
Could you link the privacy extension in question I haven't heard of it
wrote on last edited by [email protected]it's not a browser extension, its a SLAAC thing https://www.internetsociety.org/resources/deploy360/2014/privacy-extensions-for-ipv6-slaac.
TL;DR is that SLAAC used to use part of your device MAC to form it's IP, which would be trackable/fingerprintable. Now devices just pick the last 48-bits at complete random on the assumption that no other device is going to have that specific address out of the 4 quintilion available addresses.
edit the RFC https://datatracker.ietf.org/doc/html/rfc4941
-
How much slack did you have in your 10.* network? Or was it literally 16.7 million devices?
16M devices on one network would almost certainly have major scalability problems all its own. SMB chattiness alone . . . shudder.
-
Could you link the privacy extension in question I haven't heard of it
Sure, it's part of the IPv6 spec:
https://www.internetsociety.org/resources/deploy360/2014/privacy-extensions-for-ipv6-slaac/
-
Just my perspective as a controls (SCADA engineer):
I work for a large power company. We have close to 100 sites, each with hundreds of IP devices, and have never had a problem with ipv4. Especially when im out in the field I love being able to check IPs, calculate gateways, etc at a glance. Ipv6 is just completely freaking unreadable.
I see the value of outward-facing ipv6 devices (i.e. devices on the internet), considering we are out of ipv4s. But I don't see why we have to convert private networks to ipv6. Put more bluntly: at least industry, it just isn't gonna happen for decades (if it ever does). Unless you need more IPs it's just worse to work with. And there's a huge amount of inertia- got one singular device that doesn't talk ipv6 at a given generation site? What are you supposed to do?
If you set up your DNS correctly then you don't even need the IPs. Just give devices unique, human-readable names and maybe do separate sub-domains for each site or something.
-
I mean that's of the ethenet capable ones... a huge chunk are still serial
I was going to say, my friend has to maintain some fucking DOS systems because their ancient embroidery machines only want to talk to software as old as they are, over connections as old as they are.
