What is the deal with IPv6?

5 months ago by sbeak to c/nostupidquestions

I know that IPv6 was created in 1998 as a future-proofing, to make sure that there will be enough IP addresses in the works for large networks. IPv4 uses 32 bits and is represented with denary (0-9) while IPv6 uses 128 bits, so there are far more possible addresses, and it is represented using hexadecimal (0-9 then A-F).

What I'm wondering is why IPv4 is still so common, even though the number of devices connected to the internet have skyrocketed with more computers, laptops, smartphones, game consoles, embedded systems, etc. all connected! If it was thought that there would be too few available addresses in 1998, surely that has to be a bigger problem in the modern day?

Additionally, why didn't IPv6 replace v4, even after nearly three decades of existing? Is it a technological limitation, cost, or something else?

And online I see many sysadmins online (!) complaining about IPv6 being more difficult to work with. Is this because the addresses are harder to remember, are adaptations of the protocol by manufacturers all different (similar to USB-C), or is there some other problem with IPv6? Or is this a case of a loud angry minority, especially in chat forums where people tend to have more polarised views?

Many devices do support IPv6, but it's not universal like IPv4, despite the standard existing since 1998 and having many advantages. Why is this?

slazer2au 128 points 5 months ago

Because people are slow to fix something unless it is an impending problem.

Take the Y2K bug. Did you know the original person who made the bug was telling people in the 70s that is needs fixing? And it wasn't actually fixed till the second half of the 90s.

2038 is going to be a fun year with all the 32bit clocks overflowing to 1970

path: 0 23916279, hotness: undefined, score: 128, children: 5

NeatNit 83 points 5 months ago

2038 is going to be a fun year with all the 32bit clocks overflowing to 1970

Actually 13 December 1901, since it overflows to negative, not zero.

Other than that, good answer, full marks

path: 0 23916279 23916902, hotness: undefined, score: 83, children: 1

slazer2au 38 points 5 months ago

Right... signed vs unsigned ints.

path: 0 23916279 23916902 23917420, hotness: undefined, score: 38, children: 0

palordrolap 39 points 5 months ago

2038 problems have already started happening in niche cases. I expect things will pick up in pace in a couple of years because 10 years is that sort of period of time that people like to post-date future events by.

That might be enough to scare a few of the hold-outs. Then 2033 will be the next scare and reminder, because five years, etc.

Then probably every year after that until the deadline hits. By that point, the remaining few will be using faketime or something like it to eke out a few more years from whatever ancient hardware they're still running that is too expensive to replace.

Fun fact, and possible hint: Setting the date back 28 years on such hardware could work in a pinch, since the calendar from 2010 to 2037 is identical to that from 2038 to 2065. All weekdays and leap days fall on the same dates. (Easter and other moveable feasts don't, however.)

path: 0 23916279 23916508, hotness: undefined, score: 39, children: 0

iknewitwhenisawit 23 points 5 months ago

I learned to program in the 1980s. I promise you that for most programs written then the coder was like, "Two digit year, of course. Why waste so many bytes with a four digit year? Nobody will be using this software in 15 years!" And probably 95% of the time they were right....

path: 0 23916279 23917712, hotness: undefined, score: 23, children: 0

joel_feila 5 points 5 months ago

well good to know I don't live to year 10k to see the next clock problem

path: 0 23916279 23926287, hotness: undefined, score: 5, children: 0

Dirk 66 points 5 months ago

Why is this?

Most corporations have the inertia of a rock when it comes to changes. There is no real reason behind it. Implementing IPv6 is a no-brainer. Same with NATing legacy systems so they can continue using IPv4.

Instead of manually juggling IP addresses, properly set up environments use hostnames and handle DNS automatically.

It’s basically “we/I don’t see any short-term benefit from it, it causes some setup work, and it is not important because everything still works”.

path: 0 23915931, hotness: undefined, score: 66, children: 5

tburkhol 39 points 5 months ago

Basically the same reason the US hasn't switched to metric.

path: 0 23915931 23916053, hotness: undefined, score: 39, children: 1

W98BSoD 0 points 5 months ago

Metric System Thriving In Nation's Inner Cities

path: 0 23915931 23916053 23928590, hotness: undefined, score: 0, children: 0

Dojan 9 points 5 months ago

Absolutely this. Just kicking the rock down the road, and they’ll scramble to fix it once it causes issues.

path: 0 23915931 23916021, hotness: undefined, score: 9, children: 0

prole 5 points 5 months ago

There is no real reason behind it

Money. The reason is always money.

path: 0 23915931 23919140, hotness: undefined, score: 5, children: 0

originalucifer 2 points 5 months ago

It’s basically “we/I don’t see any short-term benefit from it, it causes some setup work, and it is not important because everything still works”.

this is it and why the u.s. is such garbage. everything is all about the next quarter bottom line. there is zero long term planning, "if it aint broke, dont fix it' is freakin king... at least at the small business level.... which is most of them!

path: 0 23915931 23917717, hotness: undefined, score: 2, children: 0

Robert7301201 40 points 5 months ago

The first and biggest reason is network effects. If nobody else is using IPv6, then there's little benefit to switching. Corporations and governments are always resource constrained and there's not really a business case for switching just because it might be necessary someday. Being that corporations and governments are the ones providing the vast majority of services on the internet, that means there's not as much reason for switching for end users as well.

Part of the reason that switching didn't end up being necessary was that NAT did a really good job of solving the address problem. NAT let you have an internal network behind a single IP address which vastly reduced the amount of public IPs necessary. Even most people in tech probably wouldn't realize that the concept of public vs internal network didn't exist back in the day. Everything connected to the Internet had a publically reachable IP. When even that wasn't enough, they just did it again and had CGNAT, carrier grade NAT. Now you could have multiple households and businesses behind a single IP.

The final reason is that IPv6 is just different from IPv4. Things like router advertisements and SLAAC require you to learn new things and rethink how you do things. What doesn't help matters is that until you get everyone switched over to IPv6, you still have to support IPv4 in some way. Dual stack, where you run both IPv4 and IPv6 in parallel, is the most compatible way, but it's also the most complicated to administrate. There are ways for an IPv6-only network to communicate with IPv4 clients, such as NAT64, but they each have their own caveats. These differences can result in small annoyances to administrators that add up, such as like you mentioned that IPv6 addresses are just not as memorable as IPv4. The natural fix for this is DNS. But like I said, that requires you to rethink your network. DNS goes from being a nice to have to being essential even for small networks.

Despite all these issues, IPv6 adoption is still marching along. France, India, and Germany have some of the highest rates of IPv6 capable devices, at 83.97%, 78.81%, and 74.30%. (IPv6 Adoption) Globally, we're sitting around just under 50%. (Google IPv6 Tracker) Some sectors also have higher adoption rates. Mobile carriers are mostly IPv6-only these days. A lot of residential routers also ship with IPv6 enabled.

path: 0 23918120, hotness: undefined, score: 40, children: 5

kent_eh 22 points 5 months ago

Mobile carriers are mostly IPv6-only these days.

I was going to point that out as well.

Your phone is probably on an IP6 network right now.

And it will be NATted to an IP4 address when it leaves the carrier's network to interact with the public internet.

path: 0 23918120 23918512, hotness: undefined, score: 22, children: 3

grue 7 points 5 months ago

Does that mean you can use IP6 to connect despite CGNAT, or do the ISPs that use it tend to firewall off the IP6 connections anyway?

path: 0 23918120 23918512 23919047, hotness: undefined, score: 7, children: 2

Robert7301201 6 points 5 months ago

If your ISP supports IPv6, then yes, you can use IPv6 to get a publicly reachable address when you would otherwise be unable to due to being behind a CGNAT. If your ISP does not support IPv6, you are out of luck. There are methods to translate between IPv4 and IPv6, but they require a public IPv4 address.

My friend switched to Starlink recently and was disappointed to find out he can't host Minecraft servers and such due to CGNAT. Luckily, Starlink does support IPv6, so he was able to host his servers that way. The caveat is that we have to be IPv6 capable to join his server.

path: 0 23918120 23918512 23919047 23919950, hotness: undefined, score: 6, children: 1

HiTekRedNek 1 point 5 months ago

So I have Starlink. I run a full suite of self hosted servers at home. I can access them from my workplace, which is an ipv4-only network setup.

How? I have a virtual private server (VPS) that is connected to my home network over VPN, and I connect to the IPv4 address that the server has, which is then forwarded over the VPN to my home network.

It's a bit of work to set up, but works just fine for most things.

path: 0 23918120 23918512 23919047 23919950 23935014, hotness: undefined, score: 1, children: 0

joel_feila 3 points 5 months ago

I remember my first class on NAT. The teacher said "this was not meant to be a security feature but that one use for it".

path: 0 23918120 23926233, hotness: undefined, score: 3, children: 0

litchralee 28 points 5 months ago

In a nutshell: https://github.com/...

path: 0 23920139, hotness: undefined, score: 28, children: 1

Danitos 19 points 5 months ago

Blog author is also one of the authors of IPv6. Very neat, thanks for sharing!

path: 0 23920139 23920441, hotness: undefined, score: 19, children: 0

joel_feila 28 points 5 months ago

we did a few tricks to get more use out of ipv4 address. take 192.168.100.1 that is a private ipv4 address it can not connect directly to the internet. Most home routers will have a single public ipv4 address and assign some private address to each device connected to it. So now each home can have 1 device with 192.168.100.1. This means we kept using ipv4 for a long time after ipv6 came out.

Second updating all the old routers and switches. At this point in time it is unlikely you will find a router in the wild that can't use ipv6. Someone let me know the last time you found a device on some job site. But it took a while to get there because its expensive to replace them and no one was going to cough the massive amount of money to get it done in just a year or two.

Here is a full ipv6 address 2001:0db8:85a3:0000:0000:8a2e:0370:7334, yes it can be shortened to 2001:db8:85a3::8a2e:370:7334. That's still a pain to type out and yes it did make a mistake just typing that one address. It is just more error prone to write and type out ipv6 addresses.

path: 0 23926213, hotness: undefined, score: 28, children: 2

maturelemontree 6 points 5 months ago

Yeah I did networking on Navy ships which used technology from the 60s. We checked a certain devices software and it was originally booted in 1962. Still, everything was IPv6 capable.

path: 0 23926213 23932963, hotness: undefined, score: 6, children: 0

Ephera 1 point 5 months ago

Yeah, I always thought the typing thing was just people coming up with silly reasons, because they don't like change, but when you do networking stuff, you actually need to type out IP addresses rather often.

Either because you need to manually set a new address. Or because you can't reach the device via network until you've typed in its IP address, so can't copy-paste it then either.

path: 0 23926213 23947427, hotness: undefined, score: 1, children: 0

inkblade 23 points 5 months ago

Maybe because a 128-bit hexadecimal address is impossible to memorise. I know all (6) my IPV4 addresses.

path: 0 23915959, hotness: undefined, score: 23, children: 12

DavidGA 53 points 5 months ago

If only there was some kind of system to give IP addresses easy to remember names.

path: 0 23915959 23916142, hotness: undefined, score: 53, children: 8

whaleross 31 points 5 months ago

And give in to big DNS? What's next? Multiple services per server? Insanity!

This was proudly coded in Notepad.

path: 0 23915959 23916142 23916219, hotness: undefined, score: 31, children: 1

Archer 16 points 5 months ago

hostfile gang rise up… after manually distributing the latest DNS updates out of band

path: 0 23915959 23916142 23916219 23916314, hotness: undefined, score: 16, children: 0

4am 14 points 5 months ago

Or maybe we could like, shorten the big addresses and not need to remember the parts we’re not using yet

There’s no place like ::1

path: 0 23915959 23916142 23916608, hotness: undefined, score: 14, children: 0

kbobabob 4 points 5 months ago

Yeah? You plan to setup, host, and maintain a local DNS server?

Been there, done that. No thanks.

path: 0 23915959 23916142 23917234, hotness: undefined, score: 4, children: 3

JasonDJ 6 points 5 months ago

IPv6 on a small network can just use mDNS just fine. Larger networks, you would have a DNS server anyways.

path: 0 23915959 23916142 23917234 23917519, hotness: undefined, score: 6, children: 0

napkin2020 1 point 5 months ago

If you selfhost, chances are you selfhost something like pihole. I myself use TechnitiumDNS and it also serves .lan hosts as well.

Works like charm. 10/10 would recommend.

path: 0 23915959 23916142 23917234 23953655, hotness: undefined, score: 1, children: 0

UndergroundParking 1 point 5 months ago

Skill issue

path: 0 23915959 23916142 23917234 23933975, hotness: undefined, score: 1, children: 0

Serinus 3 points 5 months ago

And as long as it works perfectly every time, we're set!

path: 0 23915959 23916142 23917412, hotness: undefined, score: 3, children: 0

Kazel 8 points 5 months ago

Fd00::1|fd00::2 etc...

path: 0 23915959 23916604, hotness: undefined, score: 8, children: 1

inkblade 1 point 5 months ago

Did not know that this could be gone...

path: 0 23915959 23916604 23917043, hotness: undefined, score: 1, children: 0

fishsayhelo 4 points 5 months ago

nah. when stating hex addresses, its customary to leave out any 0 components. means address is often just feab:aeae:1625:: ( latter 2 colons indicate rest is zeroed)

path: 0 23915959 23925970, hotness: undefined, score: 4, children: 0

False 17 points 5 months ago

V4 is easier to work with (not using long hex addresses and it's concepts are more familiar) and works fine for most everyone's use cases. So if it ain't broke don't fix it and low return on investment for most businesses. If you switch you have you do some awkward stuff where you maintain both.

What are these many advantages you speak of, other than global address space? If I'm an average business and may need one to three external ipv4 addresses, which are around $30/yr each, how much labor is it going to cost to migrate and when will I break even? Surely my sysadmin's time is better spent on things like security hardening?

path: 0 23916433, hotness: undefined, score: 17, children: 11

originalucifer 9 points 5 months ago

how much labor is it going to cost to migrate and when will I break even? Surely my sysadmin's time is better spent on things like security hardening?

this is the reason right here.

theres literally no economic pressure for last mile users to give a shit about v6. v4 is so mature (and really the nat ecosystem around it) that its just dirt simple to get basic or crazy shit running quickly. v6? ha

path: 0 23916433 23917582, hotness: undefined, score: 9, children: 0

Randelung 5 points 5 months ago

One of the main issues I think is holding IPv6 back is that we keep needing to memorize IPs and type them by hand. 192.168.0.16, 172.16.0.0/12, and 10.0.0.0/8 are easy to remember, and usually it's just the last number that's important, anyway, because we all use 192.168.1.0/24 by default.

But then IPv6 comes along with /48 prefixes and endless numbers to read, analyze (same subnet? typos?), memorize or write down. Ain't nobody got time for that.

IPv6 would have to integrate some sort of DNS resolver on a network level so that people can work with computer names. That would make the hostname actually relevant and not have every Windows be called DESKTOP-W38D6M5P. If you already have a separate DNS service, it's only the registration step that has slightly more friction, but still.

E: I guess you could argue that it's a UI problem. IPv6 has neighbor discovery and the UI can just show a list to choose from. Still no hostnames, though. Is configuration part of a layer's responsibility?

path: 0 23916433 23917653, hotness: undefined, score: 5, children: 7

AA5B 5 points 5 months ago

because we all use 192.168.1.0/24 by default.

This is a bigger deal than you may think. Those of us stubborn enough to use one of the other defined internal network ranges already hit more obstacles than we should, and that difference should be trivial to non-existent.

For me the latest is a smart home device that hard-coded 192.168.1.x, so I am not able to connect it to my network

path: 0 23916433 23917653 23919927, hotness: undefined, score: 5, children: 1

False 2 points 5 months ago

Most network devices can have multiple IPs. Assign 192.168.1.1 to your router (in addition to your normal one) and it should probably start routing traffic to that device

path: 0 23916433 23917653 23919927 23921376, hotness: undefined, score: 2, children: 0

False 2 points 5 months ago

Is configuration part of a layer's responsibility?

You should see the unfinished proposal for ipv8. The authors think yes to a large degree, though not how you're thinking.

https://www.ietf.org/...

path: 0 23916433 23917653 23921352, hotness: undefined, score: 2, children: 2

TheButtonJustSpins 2 points 5 months ago

I wish they would say that IPv8 is a proper superset of IPv4 and not that IPv4 is a proper subset of IPv8, just because they're building IPv8 on top of the existing IPv4.

path: 0 23916433 23917653 23921352 23928858, hotness: undefined, score: 2, children: 0

mech 2 points 5 months ago

This sounds like they realize v6 sucked and want to build something you can just plug into a v4 network.

path: 0 23916433 23917653 23921352 23925642, hotness: undefined, score: 2, children: 0

PaintedSnail 1 point 5 months ago

Without a central server, hostname resolution is handled with mDNS. It is designed to do exactly what you're asking: allow you to resolve hostnames to IP addresses without a DNS server. A node simply broadcasts (multicasts) a request for who has a name, and whichever node has it responds with their IP.

path: 0 23916433 23917653 23928176, hotness: undefined, score: 1, children: 1

Randelung 1 point 5 months ago

Whenever I've come across mDNS it was unstable and not installed. Bonjour was distributed with iTunes and sucked (15y ago). I could see mDNS supplying additional info for a configuration tool, but the IP layer remains reliant on IPs.

What bugs me is that IPv6 has built-in neighbor discovery that almost does what mDNS does, which could just have included a hostname... It's a replacement for ARP and only ARP.

path: 0 23916433 23917653 23928176 23932778, hotness: undefined, score: 1, children: 0

antlion 1 point 5 months ago

I would love if standard IP addresses used hex by default. C0.A8.1.1 or 7F.0.0.1

path: 0 23916433 23919118, hotness: undefined, score: 1, children: 1

twkm 2 points 5 months ago

They are: ping 0xC0.0xA8.1.1 or 0x7F.1

Standard scanf number parsing is generally used though some OSes reject that.

path: 0 23916433 23919118 23924359, hotness: undefined, score: 2, children: 0

dhork 17 points 5 months ago

I think people are missing a main point here. There is nothing wrong with IPv4, it works. It just can't scale globally anymore, it doesn't have enough space.

If you are running a worldwide network with millions of nodes, IPv6 is essential. But for things that are smaller than that, it becomes less essential. But what's the best metric for adoption, how many small offices or home labs adopt it? Or how many large, worldwide networks?

path: 0 23916916, hotness: undefined, score: 17, children: 3

dbtng 23 points 5 months ago

When IPv6 was created, NAT technologies had not yet really developed yet. That development stretched out the utility of IPv4 and allowed it to be perfectly sufficient even today. Back then, you bought a public IP for every node on your network. Seems crazy now, because you can put an entire enterprise behind one IP.

IPv6 was created to allow that same provisioning concept of every node having a public IP. Well, we don't really need that anymore. So we relegate IPv6 usage to machines like cell phones, but if a human has to utilize the address, we give em an IPv4.

path: 0 23916916 23916994, hotness: undefined, score: 23, children: 1

SmoothLiquidation 20 points 5 months ago

IPv6 was created to allow that same provisioning concept of every node having a public IP. Well, we don't really need that anymore.

I’m my home lab I don’t want every node to have an external IP. I like that NAT forces me to provision holes for specific purposes and between reverse proxy and limited port forwarding I get all of the functionality that I need.

I know I can get similar security using firewall rules and DNS but it is hard to want to replace something that just works.

path: 0 23916916 23916994 23917753, hotness: undefined, score: 20, children: 0

Swedneck 2 points 5 months ago

i, uh, would say that constitutes a problem

path: 0 23916916 23922108, hotness: undefined, score: 2, children: 0

pryre 13 points 5 months ago

I think you might be underestimating uptake. Google suggests upwards of 50% usage. Also I'm fairly certain that a lot of residential infrastructure has been slowly moving to IPv6 in Australia at least. Not an overnight process, but it's happening. Over here we have a lot of newer mobile plans offering IPv6 as well.

I think a big holdback is that a lot of larger corporations will still use IPv4/NAT setups at the top level, even if all of the hardware in the network supports it. "If it's not broke don't fix it." The result is huge amounts of daily traffic coming from these institutions being IPv4 by default, with all devices in WiFi, etc, being lumped into the same group.

path: 0 23916125, hotness: undefined, score: 13, children: 1

zzffyfajzkzhnsweqm 4 points 5 months ago

I love australia for it. We had to support IPv6 because some of your clients were IPv6 only. And I think this is a good thing. Some push is neccessary.

path: 0 23916125 23916435, hotness: undefined, score: 4, children: 0

carrylex 12 points 5 months ago

surely that has to be a bigger problem in the modern day?

The problem already exists. We have run out of IPv4 addresses for years now and e. g. cloud computing/VPS providers have started charging additional fees for IPv4 addresses.

path: 0 23921730, hotness: undefined, score: 12, children: 0

Pipea 10 points 5 months ago

Inertia. IPv4 still works, every service on the internet still available over it. You can just be lazy and things will be ok.

Complexity. IPv6 is complex in the areas where v4 sucks. Ran out of address space? Here's a lot more address space. Multiple routers offering multiple routes? Just grab them all, have as many addresses as you want. No method to find peers on the same subnet? Here's like three methods to find peers on the subnet. All this is stuff you gotta learn!

Workarounds. Initially, ISPs thought that people turned their PC off at night and they'd get the IP address back. Then, they were leaving multiple devices on all day! So they came up with a hack that pretends everyone is behind one IP address, now all your devices are just one IP. But that IP still stays up and occupied all the time, they're not getting it back, so they put all their customers under another (CG)NAT. It's just NAT all the way down whenever they run out, and this way they never run out.

path: 0 23935498, hotness: undefined, score: 10, children: 2

filcuk 3 points 5 months ago

I still don't understand IPv4 fully after all these years, I'm not sure I'll ever bother with v6 for my hone network.

path: 0 23935498 23937512, hotness: undefined, score: 3, children: 1

bss03 3 points 5 months ago

I'm just too used to setting up DHCP and including the single gateway address in that.

Setting up a routing advertisement daemon and just letting devices use their (MAC-derived) automatic IPv6 address is significantly different, so I haven't learned it yet.

It also doesn't help that I've never been under an ISP that provided IPv6 connectivity, so I'd only be able to connect to IPv4 external endpoints anyway, unless I separate got a 6-in-4 tunnel service of smth.

path: 0 23935498 23937512 23937721, hotness: undefined, score: 3, children: 0

bjoern_tantau 8 points 5 months ago

For me personally it's unfamiliarity. Technically all my devices and networks use IPv6. But I just enabled it in my router and used my hosting company's configuration.

But one of my servers at home should be reachable from the internet but that is only through IPv4. Configuring port forwarding through my router was intuitive and straight forward. But for IPv6 I have to allow the port to be open, but I don't want it to be the standard port so I have to configure the corresponding service on the machine itself to listen with a specific port on a specific address. But I have no idea what each of the addresses it has mean.

I think some of them are purely internal, some temporary, some less so. And if I ever found out what to use I would then have to configure my DynDNS, which is currently just pointing to the public IPv6 address of my router but not to the server I would want to reach.

I could learn all these things. But I just can't be bothered because the IPv4 stuff still works.

path: 0 23916280, hotness: undefined, score: 8, children: 1

orgrinrt 5 points 5 months ago

At least you have ipv6 as an option..

I will switch the second it becomes available here. Won’t hold my breath though…

path: 0 23916280 23916497, hotness: undefined, score: 5, children: 0

Zwuzelmaus 7 points 5 months ago

Additionally, why didn't IPv6 replace v4

Same reasons why electric vehicles have not replaced gas powered vehicles (yet).

The engine is not easily exchangeable, and there are still enough people who build, and people who buy the older models.

path: 0 23916387, hotness: undefined, score: 7, children: 2

originalucifer 1 point 5 months ago

but the analogy fails to scale. you cant nat gasoline

v6 solves a problem no one seems to have yet, and so no one is buying into. money talks and v4 isnt financially painful.

path: 0 23916387 23917622, hotness: undefined, score: 1, children: 1

Zwuzelmaus 2 points 5 months ago

v6 solves a problem no one seems to have yet

Very wrong.

path: 0 23916387 23917622 23929050, hotness: undefined, score: 2, children: 0

carrylex 6 points 5 months ago

The main reason is money.

Some companies don't want to do additional work and IPv4 is "good enough" (although it isn't) so they do nothing and we are stuck with it.

path: 0 23921693, hotness: undefined, score: 6, children: 1

joel_feila 2 points 5 months ago

I mean company is worth a few billion and last week at work they considered having a metal tool box to prop open the router room door "good enough". I'm not in IT, but I was to walk in and write down the ip addresses and try to ping them from my workstation which just let open the command prompt. I literally said "WHY AM I ALLOWED TO DO THIS"

path: 0 23921693 23926273, hotness: undefined, score: 2, children: 0

Treczoks 6 points 5 months ago

There are a number of points:

If you build a networking devices, you have to have IPV4. You may or better should have IPV6, too, but without IPV4, you'll have a bad start.

If you build an embedded system, like an "internet of things" sensor or actor, memory is at premium, so having to take care of a small and a large IP stack might be challenging.

Some systems are old that their software libraries don't even offer an IPV6 option.

My current project uses IPV4 only, because I don't need anything fancy. I just span a 10/8 network with 10.0.0.1 being the server. No routing, not even DNS. Using IPV6 for that application would be wasted.

path: 0 23922560, hotness: undefined, score: 6, children: 0

ChaoticNeutralCzech 5 points 5 months ago

denary

Yes, that's technically the correct 10th term in the Latin-based unary-binary-ternary-... sequence but nobody calls it that... I wondered what your mother tongue is but I couldn't find a language in which the preferred name for "decimal system" would use den- rather than dec-, dek-, des- or a completely different word. Not to mention you avoided senidenary for obvious reasons...

path: 0 23917479, hotness: undefined, score: 5, children: 3

sbeak 1 point 5 months ago

I dunno, I use the two terms interchangeably. Both describe the same thing and you get the idea with both words. "Senidenary" is much less common than "hexadecimal", so the latter is preferred. But to be fair, it is kind if weird I used denary then hexadecimal. English is strange, it's many languages in a trenchcoat.

path: 0 23917479 23918406, hotness: undefined, score: 1, children: 2

psycotica0 3 points 5 months ago

Hmm. I've been in math, computer science, and computer programming for 20 years in English (Canada) and I've never heard "denary". It's cute, but never once heard anyone say it. So they're not interchangeable to me 😛

path: 0 23917479 23918406 23932883, hotness: undefined, score: 3, children: 1

sbeak 1 point 5 months ago

Yeah I do computer science too, and decimal is more common. But denary is still thrown around, at least in the media I consume.

path: 0 23917479 23918406 23932883 23934958, hotness: undefined, score: 1, children: 0

quick_snail 4 points 5 months ago

Lots of servers these days run only on IPv6

path: 0 23928432, hotness: undefined, score: 4, children: 2

floquant 1 point 5 months ago

On the LAN side sure, but I don't think many people would make a public website/webapp "true single stack". If there's a network appliance "terminating" the IPv6 connection and "NATting" it over IPv4 that's a terrible hack that is even worse than not having it at all imho

Unless you're talking about the link-local fe80 addresses, but those are basically sparkly MAC addresses

path: 0 23928432 23937785, hotness: undefined, score: 1, children: 1

quick_snail 2 points 5 months ago

On WAN. Often hosting providers charge extra for ipv4 addresses, so many servers just don't get them anymore

path: 0 23928432 23937785 23944767, hotness: undefined, score: 2, children: 0

dbtng 3 points 5 months ago

Every cell phone and a shit-ton of IoT runs on IPv6. There's a lot of phones out there. I bet you even have one, no? You are using IPv6 right now.

But if you really want to know why, first learn how to count in binary. It's gonna be much harder than you expected.
Then learn how to count in hex. Boy, that's fun.
Now convert them back and forth. Yay, what a good time!

This is a byte. Starting from the right, each place doubles. No, its not backwards, it just feels that way.
1111 1111
128 | 64 | 32 | 16 | 8 | 4 | 2 | 1
Add up the places. You can write any number from 0 to 255 this way.

You've seen that 255 number a lot. Maybe this dotted decimal notation will look familiar.
255.255.255.0
For this number (a subnet mask) each of the first three positions is maxed out, and zero is ... zero.

Let's write it in binary.
1111 1111 . 1111 1111 . 1111 1111 . 0000 0000
Does your head hurt yet? It will.

Now let's convert it to hex.
Ya you got it. It's base-16 integers. So you hit 10 and start counting in alpha.
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 A
11 B
12 C
13 D
14 E
15 F

This is a nibble. It's half a byte. Ya, that's a little funny some nerd farted out one day.
1 1 1 1
8 | 4 | 2 | 1
The max value of a nibble is ... 15.
And 15 is ... F

Split the byte into nibbles. Convert the two nibbles to hex.
1 1 1 1 1 1 1 1
(15) (15)
FF

So let's do the whole subnet mask.
255.255.255.0
1111 1111 . 1111 1111 . 1111 1111 . 0000 0000
(15) (15) . (15) (15) . (15) (15) . (0) (0)
FF:FF:FF:00

And that, my friend, is some of the very simplest hex math you are likely to see.
In order to convert it from a number you understand, you have to run through binary, chop it in half, and recreate it as hex.
It gets much more complex than this, and that's just basic numerical manipulation.

This is already too long, and I haven't even written an IPv6 number yet.
We are just managing single digits here.

Why don't people like IPv6? Well, its hard.

path: 0 23916588, hotness: undefined, score: 3, children: 8

Whelks_chance 8 points 5 months ago

What's the use case for a human ever having to do this manually?

path: 0 23916588 23917422, hotness: undefined, score: 8, children: 7

originalucifer 4 points 5 months ago

its not about the doing. its about understanding the underlying data that forms the structure

path: 0 23916588 23917422 23917498, hotness: undefined, score: 4, children: 1

dbtng 1 point 5 months ago

The 'doing' part is more important that you indicate.

path: 0 23916588 23917422 23917498 23921085, hotness: undefined, score: 1, children: 0

Randelung 3 points 5 months ago

It's easy once you get used to it. But yes, imo still needing to manually handle IPs is a major failure of IPv6. We recognized we needed many and therefore long addresses, but we forgot the human in the process.

path: 0 23916588 23917422 23917725, hotness: undefined, score: 3, children: 3

Whelks_chance 2 points 5 months ago

This still only talks about the how, I don't see why anyone would ever need to do these operations. Other than copy pasting them around for configuration purposes, why does it matter what form they take?

path: 0 23916588 23917422 23917725 23920683, hotness: undefined, score: 2, children: 2

Randelung 1 point 5 months ago

That's what I'm saying. Currently you copy paste if possible or read it off a screen if not. Then you carry it to a network partner. See printers and static IPs.

path: 0 23916588 23917422 23917725 23920683 23922049, hotness: undefined, score: 1, children: 0

dbtng 1 point 5 months ago

Well, for 25 years of my career I got by using the subnet cheat sheet. (https://www.aelius.com/njh/subnet_sheet.html)
And then I got passed over for a couple jobs and decided to get the CCNA.
These skills are requisite. Mandatory. You ain't passing without demonstrating competency in the above dance of digits.
I can write that entire subnet chart out from scratch and first principles now.

path: 0 23916588 23917422 23917725 23920683 23921073, hotness: undefined, score: 1, children: 0

dbtng 1 point 5 months ago

Glad you asked. Gives me a chance to address the unexpected (??!) downvotes.
Maybe I made someone feel dumb? I can only hope. :]

I'm a network engineer. I recently passed the Cisco CCNA. About 20% of the test was subnetting and IPv6.
These skills are core to building networks, and you must demonstrate competency with the raw numerical manipulation.

path: 0 23916588 23917422 23920975, hotness: undefined, score: 1, children: 0

fizzle 3 points 5 months ago

Last time I looked into this i think my ISP hadn't assigned a range or whatever theyre supposed to do.

I also didnt understand how it works but didnt invest any time trying to figure it out.

I think basically it hasn't been necessary so I just haven't implemented it.

path: 0 23916509, hotness: undefined, score: 3, children: 1

Lodespawn 3 points 5 months ago

Man my ISP won't even give me a fixed IPv6 address, like even if I wanted to pay for it, can't have one, ridiculous

path: 0 23916509 23916566, hotness: undefined, score: 3, children: 0

KiwiTB 3 points 5 months ago

Ipv6 is widely used, but it can be used along side ipv4 so until ipv4 because unused it'll be there

path: 0 23916464, hotness: undefined, score: 3, children: 0

thenextguy -3 points 5 months ago

FYI, there’s a new proposal for IPv8 to address the issues with ipv6.

The main benefit seems to be that it is a superset of IPv4, so all existing addresses remain valid.

It also has some questionable ‘enhancements’ like requiring DNS records in order to allow routing.

path: 0 23919120, hotness: undefined, score: -3, children: 4

mholiv 10 points 5 months ago

Ipv8 isn’t a real proposal being taken seriously by anyone just fyi. The original white paper was AI slop with full on hallucinated sources.

path: 0 23919120 23919665, hotness: undefined, score: 10, children: 0

spicehoarder 3 points 5 months ago

Let's just adopt the whole superset thing and have ipv4.1 or something. Those are some pretty rancid enhancements.

path: 0 23919120 23919281, hotness: undefined, score: 3, children: 0

eatham 2 points 5 months ago

Just so you know that's a joke

path: 0 23919120 23925473, hotness: undefined, score: 2, children: 1

thenextguy 2 points 5 months ago

Color me fooled.

https://www.simonpainter.com/ipv8-april-fools/

path: 0 23919120 23925473 23925800, hotness: undefined, score: 2, children: 0

Greg -11 points 5 months ago

path: 0 23916040, hotness: undefined, score: -11, children: 2

4am 10 points 5 months ago

IPv6 has the same level of security as IPv4.

If you mean to say that IPv4 NAT provides security, well please never work on any networks that I need to use.

path: 0 23916040 23916642, hotness: undefined, score: 10, children: 1

nightwatch_admin 1 point 5 months ago

Excuse me! Do you have a moment to talk about our Lord and Saviour, Unique Local Addresses? You too can have NAT issues on your modern addressing system!

path: 0 23916040 23916642 23916860, hotness: undefined, score: 1, children: 0

nostupidquestions

nostupidquestions

@lemmy.world

login for more options

No such thing. Ask away!

!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)

Rule 1- All posts must be legitimate questions. All post titles must include a question.

All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.

Rule 2- Your question subject cannot be illegal or NSFW material.

Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.

Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.

Rule 4- No self promotion or upvote-farming of any kind.

That's it.

Rule 5- No baiting or sealioning or promoting an agenda.

Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.

Rule 6- Regarding META posts and joke questions.

Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.

On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.

If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.

Rule 7- You can't intentionally annoy, mock, or harass other members.

If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.

Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.

Rule 8- All comments should try to stay relevant to their parent content.

Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.

Rule 10- Majority of bots aren't allowed to participate here. This includes using AI responses and summaries.

Credits

Our breathtaking icon was bestowed upon us by @Cevilia!

The greatest banner of all time: by @TheOneWithTheHair!

go to feed...

nostupidquestions

nostupidquestions

@lemmy.world

login for more options

No such thing. Ask away!

!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)

Rule 1- All posts must be legitimate questions. All post titles must include a question.

All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.

Rule 2- Your question subject cannot be illegal or NSFW material.

Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.

Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.

Rule 4- No self promotion or upvote-farming of any kind.

That's it.

Rule 5- No baiting or sealioning or promoting an agenda.

Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.

Rule 6- Regarding META posts and joke questions.

Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.

On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.

If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.

Rule 7- You can't intentionally annoy, mock, or harass other members.

If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.

Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.

Rule 8- All comments should try to stay relevant to their parent content.

Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.

Rule 10- Majority of bots aren't allowed to participate here. This includes using AI responses and summaries.

Credits

Our breathtaking icon was bestowed upon us by @Cevilia!

The greatest banner of all time: by @TheOneWithTheHair!

go to feed...