Live data from Hacker News

Tell HN: Hacker News now supports IPv6

news.ycombinator.com

281–290 of 396 posts

Re: Tell HN: Hacker News now supports IPv6

#281
post #182

I am so surprised by the hate for IPv6 in this thread. I have been deploying IPv6 for more than ten years and it really improve many situations (beside larger addresses). I have to admit, there is a learning curve. But I want to encourage everybody involved in configuring computers to learn. Also I want to rent about Cisco not using /64 for link local by default, thus being incompatible with BSD systems. Link local m…

> I have been deploying IPv6 for more than ten years and it really improve many situations (beside larger addresses).

for most people, it is transparent and doesn't improve anything... ipv6 could be disabled on their router and everything would be the same (I actually used to disable ipv6 at router level to avoid inadvertently leaking data on ipv6)

Re: Tell HN: Hacker News now supports IPv6

#282
post #182

I am so surprised by the hate for IPv6 in this thread. I have been deploying IPv6 for more than ten years and it really improve many situations (beside larger addresses). I have to admit, there is a learning curve. But I want to encourage everybody involved in configuring computers to learn. Also I want to rent about Cisco not using /64 for link local by default, thus being incompatible with BSD systems. Link local m…

Stuff on the Internet breaks if I enable IPv6 on my Google Fiber router (been that way since I first got Fiber years ago—though I think Amazon works with it enabled now, which it didn’t before).

My T-Mobile connection issues an IPv6 address but fails online “is my IPv6 working?” tests.

I enjoy it on my private networks but simply can’t rely on it on the Internet yet.

Re: Tell HN: Hacker News now supports IPv6

#284

Earlier quoted context omitted.

> IPv6 will rid us from the abomination of domestic NAT. But won't that also have disadvantages? NAT obscures which natural person is responsible for any given household traffic, which makes user tracking and surveillance harder.

> obscures which natural person is responsible for any given household traffic IPv6 has roughly the same level of privacy; your client device's IPv6 address changes every few hours. Yes there's a minor loss since an association can be made during those hours, but arguably with the generally low number of people sharing a household internet connection I don't think it's a huge difference.

If mobile internet carriers get a specific IPv6 address slice and do what they already do with phone numbers, you could have a mobile non-changing IPv6 routed roughly efficiently, that globally.

Actually, this should be a base service of mobile internet. The various carrier peerings will define how "efficiently" your traffic is routed (realtime audio/video...).

The blocker is the billing scheme I guess (as usual...).

Re: Tell HN: Hacker News now supports IPv6

#285

Earlier quoted context omitted.

Clearly that is not sufficient enough for a variety of reasons else we wouldn’t be having this conversation in the first place

What problem is not solved by various DNS and local-addressing options, but is solvable by some other aliasing scheme that isn't DNS under another name, and can you outline how a better aliasing scheme would work? Background and current options, as I'm aware of them: "IPv6 addresses are too difficult" objectors don't seem to want a solution to the ease-of-use problem that leverages aliases, because DNS is that. They…

Solved you say? So how do I set up DNS for LAN hosts that under IPv4 would have static private addresses?

Under IPv6, you run into problems long before DNS - trying to assign static addresses as DHCPv6 is an afterthought, also whole setup has to be robust somehow when the whole network prefix changes.

Re: Tell HN: Hacker News now supports IPv6

#286
post #246

Earlier quoted context omitted.

Can you even begin to imagine a use case that could come close to exhausting an IP space that is perfectly capable of assigning a /60 subnet to every single grain of sand on earth? That subnet is large enough to then assign an IP address to every individual atom in that grain of sand. For comparison, if we wanted to assign every living person on Earth a grain of sand, we would only need a few cubic feet of it (less t…

> Can you even begin to imagine a use case that could come close to exhausting an IP space that is perfectly capable of assigning a /60 subnet to every single grain of sand on earth? As parent said, I'm sure people made the exact same argument about IPv4 back in the day, but comparing it to something else. And when IPv16 finally appears in the future, people will yet again make exactly the same argument.

> As parent said, I'm sure people made the exact same argument about IPv4 back in the day, but comparing it to something else.

You're ignoring the sheer scale of this question. We don't have enough raw materials on this planet, or likely in the observable universe, to produce enough devices that would consume that many IPs.

We could colonize 1 billion planets.

Each of those planets could have 100 billion people.

Each of those 100 billion people could own 1 billion "things" that could be considered "networked devices".

Each of those "things" could consume 1 billion IPs.

We could have all that, and we would still have 70% of the IPv6 space left.

> The decision to put a 32-bit address space on there was the result of a year’s battle among a bunch of engineers who couldn’t make up their minds about 32, 128 or variable length. And after a year of fighting I said — I’m now at ARPA, I’m running the program, I’m paying for this stuff and using American tax dollars — and I wanted some progress because we didn’t know if this is going to work. So I said 32 bits, it is enough for an experiment, it is 4.3 billion terminations — even the defense department doesn’t need 4.3 billion of anything and it couldn’t afford to buy 4.3 billion edge devices to do a test anyway. So at the time I thought we were doing a experiment to prove the technology and that if it worked we’d have an opportunity to do a production version of it. Well — [laughter] — it just escaped! — it got out and people started to use it and then it became a commercial thing.

- https://www.youtube.com/watch?v=mZo69JQoLb8&t=816s

They were contemplating 128 bits addresses all the way back then, but settled on 32 bits as a mere proof of concept that got out of hand.

Re: Tell HN: Hacker News now supports IPv6

#287
post #88

Earlier quoted context omitted.

Shitty ISPs will always give you as little as they can get away with. If the software enforces /64, they'll you /64. Raise the limit to /128 and they'll give you /128. At least with the current state of affairs, you have the option to use ND Proxy instead of NAT66.

Doesn't AWS currently hand out /128?

If you create a v6 VPC you can choose /44-/60. Subnets can be between /44-/64.

Re: Tell HN: Hacker News now supports IPv6

#288
post #182

I am so surprised by the hate for IPv6 in this thread. I have been deploying IPv6 for more than ten years and it really improve many situations (beside larger addresses). I have to admit, there is a learning curve. But I want to encourage everybody involved in configuring computers to learn. Also I want to rent about Cisco not using /64 for link local by default, thus being incompatible with BSD systems. Link local m…

I don't hate IPv6, but I am putting off switching my network to it for as long as I can get away with.

There's nothing I do that IPv6 makes better, and switching to it is a very large and painful task, so delaying that switch until it's required doesn't seem unreasonable.

Re: Tell HN: Hacker News now supports IPv6

#290

Earlier quoted context omitted.

For a practical demonstration: That's the reason decimal IPs work, too - i.e. http://3520653007/ is the same as http://209.216.230.207/ (and both will go to HN) - it's all just nice formating for our human brains. Nothing would stop us from formatting IPv6 the IPv4 way except the monstrous length of the resulting address.

Wow learned something new today. What's interesting is that the decimal representation looks more like a phone number which people would be used to. Interesting that IP addresses as they are written today was the format that won, as a kid before learning how computers worked I always found it weird how 255 was the highest number in each group.

Its often challenging enough for people to do CIDR subnet calculations in their head when its broken out into octets. I'd have just given up on networking entirely if the standard was to use decimal notation.
Post reply on HN