10 ms·
IPv6 excuse bingo
- antirez 9y ago17) Nobody wants to do work without some actual immediate local reward (in time and space, since IPv6 is surely beneficial from the POV of the world at large), potentially creating N problems. IPv6 should be studied as an emblematic case of mistake in the approach of the introduction of a new technology.
- Waterluvian 9y agoYeah I did a bunch of AWS stuff for a new project at the startup I'm at. I tried for five minutes to get ipv6 working across all my VPC stuff. Didn't work. Wouldn't provide immediate benefit. Moved on real quickly.
- aodin 9y agoIf you use terraform, I put together this example project for AWS + IPv6: https://github.com/aodin/aws-ipv6 https://github.com/aodin/aws-ipv6
- devit 9y agoIs there any alternative approach that would be more effective?
- kazinator 9y agoA sane extension to IPv4 using 64 bit addresses, and not disturbing anything unrelated to address space exhaustion: not replacing ARP with the ICMP-based neighbor bullshit (so that you now need an IP address to get an IP address) and so on. https://en.wikipedia.org/wiki/Second-system_effect https://en.wikipedia.org/wiki/Second-system_effect Even the use of colons in the textual IP address notation is moronic. The colon is already used in a notation for port numbers: 1.2.3.4:567. Under IPv6, you have to use square brackets around the address if it is followed by colon-delimited port number. Ugh! A 64 bit extension to IP can just use a four-part dotted address, where the parts are 16 bit decimals. Or perhaps an 8 part dotted address. A range of zeros can be two consecutive dots: 10..1 would be 10.0.0.0.0.0.0.1.
- joquarky 9y agoThey should have just extended IPv4 similar to how UTF-8 works.
- supertrope 9y agoWhich would still require everyone to buy new routers.
- deleted 9y ago[deleted]
- kazinator 9y agoPeople bought several generations of new routers since work on IPv6 began in the early 1990's. If that work had been sanely scoped, we'd all be using IPv6 by now. People bought new routers, for example, because of faster ethernet and fibre. Faster switching, more ports. Bigger routing tables. At the last hop, also due to Wi-Fi and rounds of newer Wi-Fi. A smart upgrade to IP could have been hammered out by a team of half a dozen skilled engineers well before Y2K rolled in.
- Dagger2 9y agoWe already have the best upgrade that's actually possible given the design of IPv4 -- the fundamental problem is a combination of the pigeonhole principle (which means there's no way to allow unmodified v4-only hosts to talk to v6 hosts) and the fact that there's nobody in a position to force people to use the necessary modifications. As a result, we end up with several generations of hardware that support everything necessary but where the people who wrote the config for them are too lazy to actually turn it on.
- supertrope 9y agoUpgrading to 64-bit address space would also require a rip and replace of all carrier routers, customer CPEs, and re-writing of software. We might as well take advantage of a compatibility breaking upgrade to fit in all of the other upgrades.
- FrozenVoid 9y agoIronically, their excuses make sense in context. Not all people will find technical superiority as a good argument(Linux vs Windows), as any doubt or excuse will be judged as another benefit of maintaining the status quo. The cost of switching is a real thing, they don't feel the Ipv4 exhaustion pressure personally and the old thing works. And there are some unfortunate details in IPv6 deployment decisions that make switching harder or costly enough, just enough to use alternatives fixes(like NAT) or maintain some cludge to route IPv6 without actually supporting it(read https://en.wikipedia.org/wiki/6to4 https://en.wikipedia.org/wiki/6to4 ).
- danpalmer 9y agoThe strongest rejection of these that I've seen so far is that BT in the UK rolled out IPv6 to all of their residential customers over a year ago now, and have had it in some form for several years. BT are huge, very slow moving, not very efficient, not considered "cool", not considered to be cutting edge in any way, and most of their residential customers have no idea what IPv6 is. Technically inclined customers who care about this sort of stuff, or early adopters are very unlikely to use BT. If they can do it, anyone can.
- antirez 9y agoThis is a good case study, however it is worth to note that internet providers are among the ones getting something back from switching to IPv6.
- pbhjpbhj 9y agoWhat do they get back?
- toast0 9y agoIf you're using CGNAT to work around not having an IPv4 address for each user, then rolling out IPv6 reduces load on your CGNAT system to the extent that your users can and do move traffic to IPv6. Many popular sites support it, so there can be a pretty big shift.
- supertrope 9y agoNot having to buy IPv4 addresses. CG-NAT infrastructure expenses scale up with customer base. If most of their traffic is end to end IPv6 that's a savings. End point machines like cable modems, TV decoders, VoIP adapters/IP phones, all need their own IP address; service providers with more than 16.7 million managed devices attached need IPv6.
- pbhjpbhj 9y agoBut do the ongoing CGNAT expenses outweigh the potential expenses of transitioning? I'm with one of, if not the, largest UK ISP and am pretty sure they're not IPv6 ready because their routers have no mention of it (Huawei router firmware updates presumably needed). BT have upgraded the physical infrastructure so I'd expect we'd be there already if there were easy savings.
- natch 9y ago“We are doing just fine with NAT.”
- floatboth 9y ago"NAT gives you privacy!" :D I mean, I like how sharing my IPv4 address with neighbors under cgNAT makes e.g. torrent monitoring sites (was on HN some time ago?) mix several people's downloads together into one list lol… but with actual data analysis it shouldn't be hard to separate my activity and the neighbors'
- bewo001 9y agoAnd telcos are usually required to keep track of cgNAT assignments to comply with legal interception laws.
- Dagger2 9y agoIn the end this indeed doesn't really help you much, because the ISP just ends up maintaining a giant database with records of every single connection that they can use to figure out who did what. And who pays the bill for that? You do.
- floatboth 9y agoWell, e.g. a random forum admin from overseas doesn't really have access to my ISP's database.
- simias 9y agoThe number one excuse in my opinion is: you can't only support IPv6 if you make a service that can interact with anything IPv4, so the real question is not "should I use IPv6 or IPv4?" but rather "Should I use IPv6 and IPv4 or just IPv4?" Clearly all other things being equal supporting only one stack is easier than two. It's a shame though, at work I've decided to go full IPv6 for one of our software solutions because I'm only talking "to myself" and it's amazing to have so much flexibility in your addressing. Need a unique IP in a distributed system? Just stick your MAC in there and you're good to go. Need a private network prefix that won't clash with anybody, anywhere? Use RFC 4193 and you're good to go.
- weavie 9y agoHow much extra work was it to add in IPv6?
- X-Istence 9y agoNot op, but when I went through the exercise, the only difference was that I changed the type of socket I was creating, and I used `getaddrinfo()` to get a list of addresses to bind to vs just binding to a single entity. There really isn't a whole lot of work that needs to be done to support IPv6 in an application, especially new build.
- simias 9y agoIt was a brand new design so I just used IPv6 from the ground up, there were no adaptation/rewrite involved. The main cost was the time spent reading the various IPv6 RFCs to make sure I understood the details (it mostly mapped well to my IPv4 knowledge but there are differences). Beyond that it was smooth sailing, although I'm regularly annoyed that common tools are rather clunky when dealing with numerical IPv6 addresses. For instance Firefox requires that I put [] around the IP for it to treat it like an IPv6. SSH on the other hand does not understand the address between brackets. On the other hand SCP does requires the brackets (since it uses a : to delimit the path) which is even more annoying than Firefox because zsh treats [] like a match pattern. It's just small things but it does hurt usability. Oh and ZeroMQ didn't support IPv6 in their experimental UDP implementation so that was some additional work.
- khamoud 9y agoNit: the site should be serving all of its assets over https.
- nikanj 9y agoOtherwise someone could eavesdrop this publicly available material, or MITM the content for the benefit of...why? This new https craze is like demanding seals of authenticity from posters on lamp posts.
- JackCh 9y ago>"MITM the content for the benefit of...why?" To insert advertisements or "helpful" messages (https://tools.ietf.org/html/rfc6108 https://tools.ietf.org/html/rfc6108)
- teddyh 9y agoSee also RFC 7258, “Pervasive Monitoring Is an Attack” https://tools.ietf.org/html/rfc7258 https://tools.ietf.org/html/rfc7258
- Sylos 9y agoThey could inject malicious code or even just ads into those http assets and therefore compromise the https connection. I also don't necessarily think that we need https for everything, but it's better to err on the safe side and if you're gonna start doing it, then you should do it properly.
- hartator 9y agoI feel the issue is more about benefits than how easy it is to set up. The why matters more.
- cjensen 9y ago"Customer sites routinely have IPv6 disabled on all their systems by their cargo cultist sysadmins"
- vortico 9y agoWell, these sound like great excuses to not switch to ipv6.
- rhacker 9y agoLOL, that's actually quite true.
- Angostura 9y ago"I can't remember IP addresses that long"
- nneonneo 9y agoMy favorite part of this site has got to be the crying double-colon logo! I do wish IPv6 would come sooner, but it's going to take a real extrinsic reason (e.g. catastrophe) for true mass adoption to happen quickly. Otherwise it's just going to happen slow-as-ever.
- krallja 9y agoBingo is a 5x5 grid, not 4x4. At best, this is "bino". And you're missing the free space square in the middle.
- deleted 9y ago[deleted]
- sly010 9y agoWhen it comes to tech migrations I see 3 types of stories. 1. Create "new technology" that is a backward compatible or even drop in replacement for old technologies. Good examples of this is Web technologies, TLS, Linux APIs, bitcoin soft forks etc. This however makes "new technology" vastly more complicated both in concept and in implementation. e.g. writing a conforming web browser from scratch is impossible today. 2. Create "new technologies" that are parallel redesigns and are made "how they should be". The intent is to simplify the technology and fix problems discovered in previous versions. The plan is to run things parallel until people _voluntarily_ switch to "new tech" because it's better. Examples of this is python 2 vs python 3, IPv6, etc. 3. A third approach I guess is making backward compatibility a tool, like it's done with all ANYTHING->ES5 compilers. (Sidenote: python2to3 tool should have been python3to2 instead)
- pas 9y agoSo we don't have PI address space, but that'd probably cost some dough. Anyway, our hosting provider wants money to give us a v6 prefix. And that's probably because the RIRs and LIRs also charge a fee. And I don't understand why wouldn't they allocate prefixes for free to those who already have v4 leases. Or maybe someone just wants to fleece us.
- yuchi 9y agoI’m always in for some laughs, don’t get me wrong. But if there’s something I hate is a list of bad examples (such as “falsehoods programmers think") where there’s no reference to an explanation of why each of those is a bad example. If you can’t formulate why it‘s a bad example then there’s no way it will be spreaded knowledge.
- JdeBP 9y agoYou didn't follow the hyperlinks, then. (-:
- 49bc 9y agoIt's missing a square: "Switching to IPv6 doesn't provide us any material benefit."
- Sylos 9y agoThe tiles change as you reload. It's in there like this: There's no ROI (return on investment) on deploying IPv6.
- wvenable 9y agoI had to disable IPv6 on my LAN because many things didn't work or didn't work reliably.
- ryandrake 9y agoMind sharing an example? Not that I don’t believe you, but I’m fully IPV6 on my (admittedly small) home LAN and have IPV6 upstream to my ISP (thank you, Comcast), and everything I need works well. I’d love to know what you had trouble with, simply to verify for myself that I’m not unknowingly broken!
- wvenable 9y agoI'm sure it's highly dependent on the equipment. My ISP's router allows you to control the DNS settings for IPv4 but not for IPv6. So I could not reliably re-point the DNS servers. The router also gives the ability add local DNS names for lan addresses and that literally just doesn't work when IPv6 is enabled. Connecting to a Chromecast from iOS devices was also more hit and miss when IPv6 was enabled. Actually iOS devices seem to have a lot of LAN connectivity issues in general even though they had full access to the Internet. Again, this could be a router issue.
- mitchty 9y agoI also have had no issues with a fully dual stack ipv4 and ipv6 network on Comcast. I however do run my own firewall/router, its just a silly openbsd box with some pf firewall rules. I wouldn't trust any vendor router anyway. Never had issues with ipv6 internally with ios devices either. They're some of the most active ipv6 devices as well with the happy eyeballs or whatever change they seem to prefer ipv6.
- wvenable 9y agoI previously didn't have any choice but to use the ISP's router but I recently got fiber and now I'm no longer limited to the router they provide. I might splurge and buy a good one. I used to run my own PC-based router a long time ago but when it became impossible to use with my ISP I dropped it.
- shmerl 9y ago> There's no ROI on deploying IPv6 That's Verizon.
- SadWebDeveloper 9y agoMissed one: Waiting for IPv6.1 to revert everything back to like IPv4 but with four extra digits.
- SadWebDeveloper 9y agoSeriously speaking... not a single sysadmin is going to spend time deploying IPv6 for future-proofing while IPv4 is fully maintained and supported. Best push we can make IPv6 happen is to force all Operating Systems to ditch IPv4 support in favor of IPv6 on their next major version and just play the wait game but nobody is going to do that.
- 4bpp 9y agoIt's slightly curious to see one of these for a (to my best understanding) not particularly politicised as of yet topic, but maybe it is worth reasserting that "I anticipated your argument and put it on a bingo board!" is not a useful or productive counterargument. (cf. Scott Alexander's old post on this tactic in the culture war context: https://web.archive.org/web/20180311015052/https://squid314.livejournal.com/329561.html https://web.archive.org/web/20180311015052/https://squid314....)
- JdeBP 9y agoThis discussion has been going around and around for roughly 20 years. Anticipating arguments is almost certainly not involved here. (-: