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?
wrote on last edited by [email protected]I’m a protective relay settings engineer at a contractor for lots of power companies. I’m dipping my toes into my first substation automation project. Getting to design the device native files, IPs, and other networking parts from the drawings package of site and device manuals. It’s all SEL equipment with a gateway at the top and local powerWAN, RTAC, annunciators, and relays below. I live thousands of miles from the site, so local testing would be challenging but probably have to fly or something lol. I have been doing some research on how to emulate this is a lab setting when all you have is the RTAC and some relays. Is this something SCADA engineers have to do sometimes? Like if you need to test a scheme when you can’t build it physically first?
-
>Forbidden
>You don't have permission to access this resource.
Awesome.
Obviously. You can only access it in IPv10.
-
I hope nat burns in hell when ipv6 will become standard
mind explaining? All 8 know about Nat is that it sometimes didn't let me play rainbow six siege
-
CGNATs suck ass though, I had to buy a vps just to access my own network outside my home.
Yeah, had the same issue with my ISP, but at least they switched me back to ipv4 after a support call. Didn't want to pay extra for the privilege of not being reachable from the outside anymore.
-
mind explaining? All 8 know about Nat is that it sometimes didn't let me play rainbow six siege
Having multiple hosts under one address for all hosts is annoying. Port forwarding is annoying. Some isps have their own nat and want you to pay additionally for public ip address
-
mind explaining? All 8 know about Nat is that it sometimes didn't let me play rainbow six siege
NAT is like package delivery IRL. If you’re a server and send a package to a client without NAT, that’s like sending a delivery boy to deliver pizza, goes straight from source to destination.
But with NAT it’s like ordering a package online. It first will be delivered to a distribution center, and then a delivery warehouse in your area, and then the courier delivers packages to all people on his route.
It’s way more complex and you now have a whole bunch of points of failure.
-
What is stoping Google from just blocking your entire IP-Block?
Mostly, I'm not big enough to trigger anything there.
Also, since ISPs usually only get a single humongous IPv6 block, it's actually pretty hard to know what is okay to block. Somebody might be on a /48, /56 or /64 network but they might also just have a single IPv6 address. Since you're blocking quintillions of IP addresses with each /64 net, the risk of hitting innocent IPs is high.
Also also, I'm not sure if Google is actually prepared for such a case. Since all the requests coming from Invidious just seem like legit unauthenticated requests, it's hard to flag them on IPv6 when the IPs are fully randomized.
Still, Google is moving towards requiring a login for everything. So I assume that method won't work for much longer.
-
Define "widely".
According to Google 46.09% of their traffic is IPv6 and most servers support it. It's mostly large ISPs dragging their feet.
I think it's just a few domestic US ISPs. The rest of the world has been happily using it for quite some time.
-
Ipv6 took awhile for me to understand. One of the biggest hurdles was how is it secure without NAT.
IPv6 is the natural Internet. Things are either allowed or forbidden to connect.
NAT is just a kludge. -
Any day now brother
It's the year of the ipv6 server
-
Don't worry Ubiquiti has ipv6 issues. You have an excuse.
What issues? I'm pretty much 100% ipv6 on all ubiquity equipment.
-
NAT is like package delivery IRL. If you’re a server and send a package to a client without NAT, that’s like sending a delivery boy to deliver pizza, goes straight from source to destination.
But with NAT it’s like ordering a package online. It first will be delivered to a distribution center, and then a delivery warehouse in your area, and then the courier delivers packages to all people on his route.
It’s way more complex and you now have a whole bunch of points of failure.
That's a great analogy for carrier grade nat.
For regular nat it's like the pizza is able to get all the way to your house but then has no idea who to go to so somebody has to answer the door and then take the pizza from the door to the person who ordered it themselves.
And IPv6 is like the pizza delivery guy just walks right into the house up the steps into your bedroom and hands you the pizza directly.
The best part is they each have the same exact problems you'd have in real life.
-
That's a great analogy for carrier grade nat.
For regular nat it's like the pizza is able to get all the way to your house but then has no idea who to go to so somebody has to answer the door and then take the pizza from the door to the person who ordered it themselves.
And IPv6 is like the pizza delivery guy just walks right into the house up the steps into your bedroom and hands you the pizza directly.
The best part is they each have the same exact problems you'd have in real life.
Why are we eating pizza in the bedroom
-
That's a great analogy for carrier grade nat.
For regular nat it's like the pizza is able to get all the way to your house but then has no idea who to go to so somebody has to answer the door and then take the pizza from the door to the person who ordered it themselves.
And IPv6 is like the pizza delivery guy just walks right into the house up the steps into your bedroom and hands you the pizza directly.
The best part is they each have the same exact problems you'd have in real life.
Perfect, perfect analogy. Like, seriously, I've hardly ever seen an analogy that works so flawlessly where even the implications just line up perfectly.
I am in awe.
-
Why are we eating pizza in the bedroom
I was eating salad in my bedroom 2:30 in the morning today.
Me: Fuck, can't sleep I'm hungry. You want anything?
Wife: yeah, fill up my water bottle and bring me something to eat.I went downstairs, made two loaded salads and brought them up to the bedroom.
I might in fact be getting old.
-
This post did not contain any content.
Also for home network I don’t won’t my IOT to have a real IP to the Internet. Using IPv4 NAT you can have a bit of safety by obscurity
-
Also for home network I don’t won’t my IOT to have a real IP to the Internet. Using IPv4 NAT you can have a bit of safety by obscurity
Its unlikely someone with guess your ipv6 of your iot.
-
I was eating salad in my bedroom 2:30 in the morning today.
Me: Fuck, can't sleep I'm hungry. You want anything?
Wife: yeah, fill up my water bottle and bring me something to eat.I went downstairs, made two loaded salads and brought them up to the bedroom.
I might in fact be getting old.
If you can eat a salad and then lay down without getting an explosion of acid reflux, maybe you aren't old yet
-
The reason IPv6 was originally added to the DOCSIS specs, over 20 years ago, is because Comcast literally exhausted all RFC1918 addresses on their modem management networks.
My favourite feature of IPv6 is networks, and hosts therein, can have multiple prefixes and addresses as a core function. I use it to expose local functions on only ULA addresses, but provide locked down public access when and where needed. Access separation is handled at the IP stack, with IPv4 it’s expected to be handled by a firewall or equivalent.
They kept talking it was because address exaustion, and IANA sold all the remaining blocks they had...
I tested it at the time. Ran nmap ping scan across a block all night with zero results. IANA sold the internet
-
That would imply en existence of display/usb outputs…
We’re essentially talking a bunch of embedded devices talking to each other. You can give them all the dns entries you want, but if they (or the programming environment) don’t support DNS lookup you might as well put your dns server in excel.
The microcomputers (raspberry pi, arduino, whatever) could have a modern network interface and relay the communication to the embedded devices over oldschool serial. But yeah, straight DNS wouldn't work. I like the idea though, gonna start posting my 10 favorite IP addresses on a piece of paper on the fridge. Who needs excel!
