News for hackers. Stuff that matters.
Re:IPv6 Adoption by SwellJoe on Wednesday July 26, 2017 @06:42AM (#14855069)
We added support for IPv6 to Virtualmin projects about a decade ago. Even today, only a tiny percentage of our users ever enable it (this mostly includes our own sites, embarrassingly enough, even though some of our servers in colo do have IPv6 subnets available to them). I should work on making that a thing that happens more by default.

There's a lot of cool things you can do when you don't have to worry about running out of IP addresses. A lot of complex stuff people are doing with cloud meshnets and overlay networks and bridged private networks with port forwarding and such becomes mostly moot if every VM and container can have as many dedicated real IPs as it needs to do its job.

It's also funny/weird to think about how much development effort has gone into stretching IPv4. NAT, port forwarding, SNI (and some hacky other SSL tricks before that to fit multiple SSL sites on one IP), masquerading, tunneling, VPNs, etc. The list is incredibly long and the hours spent on development unfathomable.

Re:IPv6 Adoption by Klathmon on Wednesday July 26, 2017 @08:08AM (#14855455)
I think the big reason that so much effort is put into NAT and other "workarounds" is because those are things "you" can do to solve the problem.

If your upstream provider doesn't support IPV6, you can't do anything to help that besides complain about it and hope they provide it one day.

Re:IPv6 Adoption by chiph on Wednesday July 26, 2017 @09:09AM (#14855869)
One of the places I used to work had a large number of corporate acquisitions. And sure enough, all of the new purchases also used the 10.x.x.x private space. So to get the systems to integrate quickly and meet the schedule, they used NAT. They were likely one of Cisco's largest NAT customers...
Re:IPv6 Adoption by faraggi on Wednesday July 26, 2017 @10:23AM (#14856381)
I'm not very knowledgeable in IPv6 adoption. Why do you think that?
Re:IPv6 Adoption by chiph on Wednesday July 26, 2017 @12:12PM (#14857505)
In this scenario, NAT was required for them to merge their IPv4 networks because of the high chance (almost certainty!) of address space collision.

With IPv6, the chance of address ranges colliding are much lower because of the wider address space, and the upstream provider wasn't supposed to have been handing out duplicate blocks. IPv6 also has it's own private address prefix (ULA) - fdxx:xxxx:xxxx:.... and if two organizations were both using it for internal addresses, there's a increased non-zero chance of a collision if they merge networks.

Re:IPv6 Adoption by stretchwithme on Wednesday July 26, 2017 @02:19PM (#14858722)
Or switch providers. Not that is necessarily practical either.
Re:IPv6 Adoption by oblio on Wednesday July 26, 2017 @09:48AM (#14856138)
Well, the good news is that IPv6 is winning. If Google's stats are accurate - and they probably are - IPv6 went from 1% usage to 16% usage in 5 years (January 2012 - January 2017). And in tech it's all about critical mass. We've passed innovators and early adopters and we're getting closer to early majority. I'd bet that once we're around 30-40% adoption will ramp up since few people want to be considered laggards.

And according to Google's graph I'd say we're about 5 years away from reaching 40%.

Re:IPv6 Adoption by tomjen3 on Wednesday July 26, 2017 @11:29AM (#14857033)
I can buy that argument, but I cannot buy IPv6. I mean that literally, my ISP doesn't offer it. Instead I am given two ipv4 addresses, but because of NAT I only need one - which is of course a total joke.

I would love a network where there are no bridges and every mote of dust (or VM) has an ip, but if I cannot buy the addresses, what good does it do me?

Re:IPv6 Adoption by _ncxu on Wednesday July 26, 2017 @11:35AM (#14857096)
You may not be able to now, but the pressure GP mentioned will also apply to ISPs, and they'll soon start seeing IPv6 as a competitive edge, or at the very least, something to not lag behind in making them lose customers. Especially if there's a "killer app" that makes the switch and ONLY uses IPv6, e.g. say, google.com.
Re:IPv6 Adoption by syncsynchalt on Wednesday July 26, 2017 @04:36PM (#14860074)
As CG-NAT becomes more common, the "killer app" might be improved experience for gamers.
Re:IPv6 Adoption by mrpippy on Wednesday July 26, 2017 @11:37AM (#14857130)
You can get IPv6 connectivity (tunneled over v4) for free: https://tunnelbroker.net
Re:IPv6 Adoption by themind on Wednesday July 26, 2017 @01:05PM (#14858024)
I think you're missing the exponential trend, and it is more likely we'll see 40% adoption within 2-3 years.
Re:IPv6 Adoption by legulere on Wednesday July 26, 2017 @04:56PM (#14860268)
Re:IPv6 Adoption by themind on Wednesday July 26, 2017 @09:27PM (#14861934)
True. Good point.
Re:IPv6 Adoption by gourou on Wednesday July 26, 2017 @10:19AM (#14856342)
I imagine it accounts mostly for Africa and South Asia since they didn't get many IPv4 addresses. They got less addresses than Europe and they're at least 4 times more populated.

So I don't think we're gonna see adoption in Western countries that soon.

Here's an IPv4 map for comparison: https://www.jessevaughn.com/images/ipv4_map_of_the_internet....

Re:IPv6 Adoption by ac29 on Wednesday July 26, 2017 @10:31AM (#14856448)
Nope, the highest rates of adoption are in North America and Europe: https://www.google.com/intl/en/ipv6/statistics.html#20&tab=p...

India, Japan, Brazil, and Australia also rank relatively high.

Keep in mind some of the largest US ISPs (like Comcast) are offering native dual stack now by default. You'd have to go out of your way to disable it.

Edit: Cell phone carriers are a big driver of this as well, both Tmobile and Verizon are majority IPv6 according to [0].

[0] https://en.wikipedia.org/wiki/IPv6_deployment#United_States

Re:IPv6 Adoption by cbhl on Wednesday July 26, 2017 @12:44PM (#14857811)
A big part of that is how quickly people upgrade their cell phones -- on T-mo at least, a device had to support IPv6 and 464XLAT in order to connect to the LTE network.
Re:IPv6 Adoption by jvannistelrooy on Wednesday July 26, 2017 @10:59AM (#14856715)
You could have just looked at the other tap of OP's link to see that IPv6 adoption is highest in the US, and then in Europe. https://www.google.com/intl/en/ipv6/statistics.html#20&tab=p...
Re:IPv6 Adoption by walshemj on Wednesday July 26, 2017 @08:03AM (#14855430)
You could say the same for the effort expended on ipv6 when it was obvious in the 90's that given the explosion of consumer use of the internet that the lack of a migration path from ipv4 was a killer - and that they should have thrown away ipv6 and started again.

BT before you down vote me I used to work in international networking for BT so I know what I am talking about when it comes to interoperability

Re:IPv6 Adoption by mindcrime on Wednesday July 26, 2017 @11:38AM (#14857141)
that the lack of a migration path from ipv4 was a killer - and that they should have thrown away ipv6 and started again

How is it a "killer"? IPv6 is gaining traction now and gaining it rapidly and looks to be a clear trajectory to become ubiquitous. And hacks like NAT allowed enough runway for this to happen. What exactly is the problem?

Re:IPv6 Adoption by collinmanderson on Wednesday July 26, 2017 @10:33PM (#14862249)
Back in the 90's there wasn't a good migration path. A lot of the migration technologies have only come recently. Some examples:

NAT64 - October 2010

DNS64 - April 2011

464XLAT - April 2013

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @08:13AM (#14855480)
So, what would that magical migration path look like, then?
Re:IPv6 Adoption by hn_throwaway_99 on Wednesday July 26, 2017 @08:40AM (#14855674)
This post gives a very good explanation of what a sensible transition plan would have looked like. It mainly starts with IPv4 address space being a subset of IPv6, instead of a totally new address space: http://cr.yp.to/djbdns/ipv6mess.html
Re:IPv6 Adoption by wmf on Wednesday July 26, 2017 @12:57PM (#14857939)
When you work out the details of DJB's "plan" you discover that it's just as messy as IPv6, maybe worse. http://archive.is/eHvKF
Re:IPv6 Adoption by growse on Wednesday July 26, 2017 @08:47AM (#14855705)
IPv4 is a subset of IPv6! They literally invented a way to map from an IPv4 address to IPv6 with a special prefix.
Re:IPv6 Adoption by convolvatron on Wednesday July 26, 2017 @11:10AM (#14856815)
wth happened with that, in the original proposal it was 96 bits of zero, then that was deprecated, and then they added :ffff:0:0 with the same functionality
Re:IPv6 Adoption by wyufro on Wednesday July 26, 2017 @06:38PM (#14861029)
No, they have different functions. Sending to ::1.2.3.4 would send an IPv6-in-IPv4 packet to 1.2.3.4. Using ::ffff:1.2.3.4 tells the OS that you want to send a proper IPv4 packet and no IPv6 is used on the wire.

I don't know why the former was deprecated, but I think almost no OS supported it so might've been just that.

Re:IPv6 Adoption by Avernar on Wednesday July 26, 2017 @07:15PM (#14861232)
The former was depricated because the automatic tunneling transition method was depricated and none of the current IPV6 transition methods use them.

Now some software use those addresses to store IPV4 addresses in the same memory as an IPV6 address.

Re:IPv6 Adoption by dom0 on Wednesday July 26, 2017 @09:46AM (#14856116)
The article itself isn't dated, but for reference

Last-Modified: Sat, 02 Aug 2003 14:27:40 GMT

Re:IPv6 Adoption by hn_throwaway_99 on Wednesday July 26, 2017 @11:17AM (#14856893)
The old date of the article kind of proves my point. It's 14 years later, and we still get huge HN threads around the very-incomplete state of IPv6 transition.
Re:IPv6 Adoption by Asooka on Wednesday July 26, 2017 @08:37AM (#14855649)
For one, all IPv4 addresses could also be IPv6 addresses. There could be a straightforward translation between an IPv4 packet and an IPv6 packet and back just by prepending the address with 0s. You could enable backbone routers to speak only IPv6 and then translate those packets to IPv4 packets only when sending them to the endpoint devices. In short, IPv6 could have been designed as a backwards-compatible extension of IPv4, not a completely new network.
Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @09:16AM (#14855933)
> For one, all IPv4 addresses could also be IPv6 addresses.

You have that today, all IPv4 addresses are also dualstack addresses, which is how IPv6 is normally deployed for the transition.

> There could be a straightforward translation between an IPv4 packet and an IPv6 packet and back just by prepending the address with 0s.

Which doesn't help you anything because it doesn't enable IPv4 hosts to communicate with IPv6 hosts.

> You could enable backbone routers to speak only IPv6 and then translate those packets to IPv4 packets only when sending them to the endpoint devices.

That's called a tunnel, you can have that today.

> IPv6 could have been designed as a backwards-compatible extension of IPv4, not a completely new network.

What exactly is the backwards compatibility if none of that allows IPv4 and IPv6 hosts to interoperate?

Re:IPv6 Adoption by stephen_g on Wednesday July 26, 2017 @09:21AM (#14855969)
That still doesn't work though, because an IPv4 host still can't address an IPv6 host, and an IPv4 router still wouldn't be able to route to an IPv6 network (without hacks far uglier than NAT).

And they couldn't just upgrade every router in every backhaul network to the new protocol at once (assuming what you describe could actually work) - that took a decade, because lots of it used custom silicon for routing and switching.

Re:IPv6 Adoption by growse on Wednesday July 26, 2017 @08:44AM (#14855692)
> For one, all IPv4 addresses could also be IPv6 addresses

You mean how you can map from IPv4 addresses to IPv6 addresses? See RFC4291 section 2.5.5.

https://www.ietf.org/rfc/rfc4291.txt

Re:IPv6 Adoption by jcranmer on Wednesday July 26, 2017 @10:48AM (#14856613)
> There could be a straightforward translation between an IPv4 packet and an IPv6 packet and back just by prepending the address with 0s.

I'm guessing you're unaware that this is what you do right now. The IPv4 address space has a map in IPv6 at ::ffff:0:0/96 for being able to listen to both IPv4 and IPv6 on an IPv6 address space. There's also a few other different maps of the entire IPv4 address space for other mixed IPv4/IPv6 schemes.

The problem with any addressing enhancement to IPv4 is you still have to change every software ever (at the very least, you need to know how to craft new addresses), and you still have to change almost all hardware as well. Maybe you can devise schemes that could let some of the hardware in the middle be IPv6-unaware, but you still have to route the resulting packets to the correct location, which means you'd want to update most of the middle hops anyways.

Re:IPv6 Adoption by dangerlibrary on Wednesday July 26, 2017 @08:38AM (#14855657)
Something more like UTF-8? Largely backwards compatible with old formats (ascii) while still being extensible.
Re:IPv6 Adoption by jcranmer on Wednesday July 26, 2017 @10:28AM (#14856422)
The ASCII->UTF-8 transition is arguably nearly as painful as IPv4->IPv6, and it's still nowhere near complete.

Switching to UTF-8 requires two major steps. The first was making software and interchange systems preserve the 8th bit (it used to be commonly used as a parity bit). For email, this was true only about the mid-to-late 90s--surprisingly recent. The second step, which is still incomplete today, is letting control mechanisms that used to speak only ASCII understand UTF-8 (or something else non-ASCII) reliably. You could only put UTF-8 in C++ or C code as of C++11/C11, for example. Non-ASCII domain names are still problematic, to say nothing of non-ASCII email addresses. In other words, trying to speak UTF-8 to someone who only speaks ASCII is still as problematic as trying to speak IPv6 to someone who only speaks IPv4. We just don't notice it as much because we keep advising people to only speak ASCII in key places.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @10:40AM (#14856541)
> For email, this was true only about the mid-to-late 90s--surprisingly recent.

Actually, email still is not nominally 8-bit transparent (ESMTP 8BITMIME is optional and not supported by all MTAs), but it doesn't need to be, that's what quoted-printable and base64 are for.

Re:IPv6 Adoption by jcranmer on Wednesday July 26, 2017 @10:58AM (#14856698)
The timeframe I'm using is the timeframe where you stop seeing servers mangle 8-bit email. 8BITMIME technically requires converting 8-bit bodies to QP and base64, which is generally not necessary nowadays, and some would argue that software that chooses not to implement that shouldn't advertise 8BITMIME.
Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @11:25AM (#14856985)
> and some would argue that software that chooses not to implement that shouldn't advertise 8BITMIME.

Which is why I wrote that email still nominally isn't 8-bit clean :-)

Yes, in practice, you won't find an MTA that doesn't leave your 8 bit data unharmed, but you do find MTAs that don't advertise 8BITMIME, and so nominally noone should send them 8 bit data ... except everyone does anyway, of course ...

Re:IPv6 Adoption by xvilka on Wednesday July 26, 2017 @02:13PM (#14858668)
One of major blockers of UTF-8 transition is Windows world - the operating system itself, who stubbornly stuck with not even complete UTF-16 support, and also a big amount of software for this OS family without the proper UTF-8 compatibility.
Re:IPv6 Adoption by johncolanduoni on Wednesday July 26, 2017 @09:08AM (#14855865)
The ASCII/UTF-8 backwards compatibility relies on (a) a large subset of data fitting within the constraints of ASCII and (b) most "upstack" applications being able to handle a few garbled/unrecognized characters. How does this map to routing packets on the internet, where the IP header contains time-sensitive metadata needed for delivery and the payload is largely agnostic of the differences?
Re:IPv6 Adoption by zaphoyd on Wednesday July 26, 2017 @10:41AM (#14856552)
Except UFT8 is not backwards compatible with ASCII!

An application written to only understand ASCII will not print non-ASCII UTF-8 characters. That is what you are asking here. It can't be done with ASCII/UTF8. It can't be done with IPv4/IPv6.

Re:IPv6 Adoption by aexaey on Wednesday July 26, 2017 @03:31PM (#14859395)
UTF8 is backward compatible with ASCII just fine - latter is a strict subset of former. It doesn't get more backward-compatible than that!

IPv6, on the other hand, is not at all backward compatible with IPv4 (was never a design goal - magic of OSI stack was supposed to do it's thing). One would argue that incompatibility is in large part responsible for the 6's slow start - even though afterthought bolt-ons eventually did see sunlight - ::ffff:x.x.x.x thing, cornucopia of tunnels and dual-stacks of various degree lite-ness, etc.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @08:04PM (#14861523)
... which means that if of two parties only one understand UTF-8, they have to speak ASCII. ASCII being a subset of UTF-8 does not provide and benefit in that regard, just as IPv4 addresses being a subset of IPv6 addresses wouldn't.
Re:IPv6 Adoption by aexaey on Thursday July 27, 2017 @04:34AM (#14863571)
Let me drill down it for you:

Imagine two endpoints talking a backward compatible pair of standards: A only speaks ASCII, B only speaks UTF-8. Would you think they will be able to communicate at least something?

Now imagine two endpoints talking a not backward compatible pair: A only speaks IPv4, and B only speaks IPv6. Will they be able to communicate, at least something?

See the difference?

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Thursday July 27, 2017 @04:55AM (#14863640)
> Imagine two endpoints talking a backward compatible pair of standards: A only speaks ASCII, B only speaks UTF-8. Would you think they will be able to communicate at least something?

As long as they only speak ASCII, yes.

> Now imagine two endpoints talking a not backward compatible pair: A only speaks IPv4, and B only speaks IPv6. Will they be able to communicate, at least something?

That's why you deploy IPv6 dual-stacked with IPv4. That way, if two parties only speak IPv4, it's completely backwards compatible.

> See the difference?

Sure do I see the difference. What I don't see is how to apply any of that to the v4 to v6 transition in a way that would have any advantage over how it is being done now.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @09:11AM (#14855896)
> Something more like UTF-8? Largely backwards compatible with old formats (ascii) while still being extensible.

Which would work how exactly in the case of IP? So far sounds mostly like "make it backwards compatible by making it backwards compatible".

Re:IPv6 Adoption by aexaey on Wednesday July 26, 2017 @03:55PM (#14859652)
>> Largely backwards compatible

> how exactly in the case of IP?

For example, introduce two special IP options that would act as "page selector" for source and destination addresses respectively. i.e.

  SRC: 1.1.1.1, DST: 2.2.2.2, no options ->
      from 1.1.1.1 to 2.2.2.2
      (backwards-compatible packet, classic IPv4)

  SRC: 1.1.1.1, DST: 2.2.2.2, opt.X: 1.1.1, opt.Y: 2.2.2 ->
      from 1.1.1.1.1.1.1 to 2.2.2.2.2.2.2
      (our faux-IPv6)

  SRC: 1.1.1.1, DST: 2.2.2.2, opt.X: 0.0.0, opt.Y: 2.2.2 ->
      from 1.1.1.1 to 2.2.2.2.2.2.2
      ("old" address communicating with "new" address)
Last example of three is impossible with IPv4/6 dichotomy, and is most important for backward compatibility here - yes, "old" IP holder needs to upgrade their software too[1], but they don't need to get a new IP address, and as a result you don't end up with two isolated "Internets", a.k.a. dual-stack.

Say, for ease of processing on router, require that X and Y would appear only together, in that order, preceding other options (which is a bit of an exception as far as IP options go, but again, a backward-compatible one).

Now, I'm not proposing this seriously of course, but you asked for example - here you go, a plausible, backwards-compatible "IPv4.1", if you like.

[1] All major desktop OS support IPv6 for last 10 years and major mobile OS for last 7. Let's face it - software upgrade turned out (surprisingly) not to be the biggest obstacle.

Re:IPv6 Adoption by teraflop on Wednesday July 26, 2017 @05:44PM (#14860648)
What advantage does that have over IPv6? From a backwards-compatibility perspective, it seems identical.

In order for two hosts to communicate over IPv6, both ends need to have: software that supports IPv6, and the entire network path between them needs to be able to route IPv6 packets. Your proposal is functionally no different: you call the extended address field an "option", but in fact every host is required to understand it.

Re:IPv6 Adoption by aexaey on Thursday July 27, 2017 @04:45AM (#14863605)
I used term "options" here the way it was defined in RFC 791. [1] It's a standard way to extend IPv4 packet header.

[1] https://tools.ietf.org/html/rfc791

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @08:11PM (#14861560)
> Last example of three is impossible with IPv4/6 dichotomy, and is most important for backward compatibility here - yes, "old" IP holder needs to upgrade their software too[1], but they don't need to get a new IP address, and as a result you don't end up with two isolated "Internets", a.k.a. dual-stack.

1. What would be a scenario where hosts using this mechanism could communicate where neither IPv4 nor IPv6 would work?

2. How do new internet participants get addresses under your scheme, if it only expands the number of addresses in existing allocations?

Re:IPv6 Adoption by scurvy on Wednesday July 26, 2017 @10:18AM (#14856335)
Since when is tunneling a response to running out of IPv4 addresses?

Do you mean v6 tunnel brokers? That's a response to not supporting native v6, not running out of v4 space.

Re:IPv6 Adoption by SwellJoe on Wednesday July 26, 2017 @03:32PM (#14859398)
Tunnels are used for all sorts of things, including some that aren't IP-shortage related (but many uses are related to IP shortage; connections between devices on private networks, for instance, and connecting IPv6 networks to IPv4 networks). But, I wasn't saying that all of those technologies only have application in solving IPv4 IP shortages, but they often have had a lot of effort expended on making the work for that purpose, because it's such a pervasive problem.

My point is that the IPv4 IP shortage is like the ocean and we're all fish swiming around in it. We don't see the water because it's all around us. But, it's shaped our thinking about networks in real ways that most people working in the field today have never had an "every device has a unique address" mindset. The inventors of the internet and some of the greatest innovators of networking existed in a world where "every device is addressable". I think that's a major difference in mindset and I think it has consequences.

Re:IPv6 Adoption by Arnt on Wednesday July 26, 2017 @11:12AM (#14856848)
If you have or can get addresses at location A and need some at location B, you can tunnel. Or if you have BGP access you can publish a really long prefix. Both are brittle.
Re:IPv6 Adoption by otabdeveloper1 on Wednesday July 26, 2017 @07:22AM (#14855238)
> NAT, port forwarding, SNI, masquerading, tunneling, VPNs, etc.

All that stuff is mostly done for security purposes, not because we ran out of IP addresses. (And before you reply: yes, it really works and is a valid security tool.)

Re:IPv6 Adoption by SwellJoe on Wednesday July 26, 2017 @03:24PM (#14859316)
The thing is, the security elements of those things are often only marginal and were not the purpose of their existence (in most cases), and they mostly (though not all) boil down to security-through-obscurity.

We're all mostly agreed that security-through-obscurity generally only provides a false sense of security and isn't the real deal. So, what if instead of working around an IP limit with all this complicated technology, the same folks had instead been working on good point-to-point encryption for everything all this time? And, what if all that complexity didn't have to exist in every device? Every line of code increases the likelihood of a security bug, and a network stack with all this extra stuff has a lot of extra lines of code. I dunno if NAT code has been responsible for exploits, but I'd be shocked if it hasn't.

NAT didn't come into common use for security purposes. It just didn't. It came into common use because not every company owns a big enough sub-network for every device to have an IP and no individual household does. It would require completely rewriting history to suggest NAT is and has been used primarily as a security feature.

Certainly, VPNs have a useful purpose other than dealing with the IP shortage of IPv4, but a lot of VPNs at the corporate level are used to tie two private networks together. And, a lot of development has gone into that purpose.

I'm just saying that in a world without a strictly limited set of IPs over the past decade or two, we would likely have a very different looking internet, and I think it'd be a better internet than what we have, because of how much effort has gone into dealing with the complexity of NATted/tunneled/VPNed/etc. networks.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @07:25AM (#14855252)
Please explain the security purpose of four of those six.
Re:IPv6 Adoption by tomjen3 on Wednesday July 26, 2017 @11:33AM (#14857075)
VPNs are easy: you have all your services exposed, then you need to update every one stat when a bug is released and you are screwed if for some reason some of your services uses broken (or no) crypto, and it becomes more of a chore to decide which users gets access to what services.

With VPN you have more time in case of an attack, everything is encrypted by default and you only have to watch one basket of eggs.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @11:47AM (#14857210)
Which is one of six ... not quite "most" in my book.

Yeah, that's the only one where I can see a use for security purposes, but even then, that's not the only reason why it's used.

Re:IPv6 Adoption by otabdeveloper1 on Wednesday July 26, 2017 @07:39AM (#14855312)
Not being to address a corporate or home network computer from the outside is a feature, not a bug. Doubly so for the datacenter. Corporate IT doesn't want random internet hackers accessing sensitive information on the local corporate network.

Yes, you can theoretically migrate everyone to IPv6 and implement some sort of firewall system to block outside access, but now you're effectively duplicating NAT in IPv6. Worse, due to second-system effect you're bound to end up with something even stupider and nastier than the existing stupid and nasty NAT solutions.

Re:IPv6 Adoption by rnhmjoj on Wednesday July 26, 2017 @08:01AM (#14855418)
NAT being a security feature is a myth[1][2][3]. Please stop saying this.

> but now you're effectively duplicating NAT in IPv6

No, you are not. If you set up a firewall there still is no translation in IPv6, and it's not needed because the network is end-to-end connected.

> even stupider and nastier than the existing stupid and nasty NAT solutions.

NAT is expensive for both memory and CPU usage, particularly when there is a large number of hosts, and it's not a security feature by itself. In no way can IPv6 with a simple firewall be worse than NAT.

[1]: https://f5.com/resources/white-papers/the-myth-of-network-ad...

[2]: https://blog.webernetz.net/2013/05/21/why-nat-has-nothing-to...

[3]: https://security.stackexchange.com/a/8773

Re:IPv6 Adoption by otabdeveloper1 on Wednesday July 26, 2017 @08:18AM (#14855521)
> NAT being a security feature is a myth

It isn't. The arguments that it is a 'myth' boil down to arguments that it isn't perfect and doesn't protect against every attack. Well, guess what: no security measure is perfect and no security measure protects against every attack.

At the very least, a secure IPv6 network will need to hide end user addresses somehow, because giving everyone a unique, globally-addressable and trackable ID is a security showstopper.

At this point you're going to wonder if you considered all the contradicting requirements properly in your enthusiasm to roll out the next great shiny technology.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @08:28AM (#14855595)
> It isn't. The arguments that it is a 'myth' boil down to arguments that it isn't perfect and doesn't protect against every attack. Well, guess what: no security measure is perfect and no security measure protects against every attack.

Except NAT provides absolutely no security, and complicates your network setup, thus making it more prone to configuration errors and other attack vectors due to complexity.

> At the very least, a secure IPv6 network will need to hide end user addresses somehow, because giving everyone a unique, globally-addressable and trackable ID is a security showstopper.

That is called privacy extensions. Also, it's pointless if you allow cookies in the browser.

Re:IPv6 Adoption by simias on Wednesday July 26, 2017 @08:34AM (#14855636)
Only Siths deal in absolutes. NAT has the side effect of behaving like a crappy firewall, so it gives you the added security of a crappy firewall. It's not much but it's something.

But in the end I agree that it's a bit silly to use that as an argument in favor of NAT, if you want a firewall then use a firewall. I guess the advantage of NAT is that while you could forget to setup a firewall and not notice, you'll definitely notice it pretty quickly if you have a few computers on your LAN and you don't have a NAT...

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @09:27AM (#14856004)
> NAT has the side effect of behaving like a crappy firewall, so it gives you the added security of a crappy firewall.

No, it doesn't. Unless by "crappy firewall" you mean "a firewall that doesn't firewall".

> I guess the advantage of NAT is that while you could forget to setup a firewall and not notice, you'll definitely notice it pretty quickly if you have a few computers on your LAN and you don't have a NAT...

... and you could then set up a NAT and still forget the firewall. Especially so if you mistakenly believe that NAT provides firewall functionality. There is absolutely nothing that prevents your ISP, and by extension anyone who happens to compromise your ISP('s router) from connecting to your RFC1918 addresses through your NAT gateway if you don't also have a firewall.

Re:IPv6 Adoption by simias on Wednesday July 26, 2017 @09:43AM (#14856105)
You're really splitting hairs here. A NAT prevents direct access from the outside to the LAN, except is certain situations. That's part of a firewall's functionality. It's actually probably the first rule you'd set up on most firewalls, then you'd open select ports as necessary (which you do with port forwarding on NATs). A firewall can do a whole lot more of course, but there is some overlap.

Anyway, I think we're in agreement on the core of the issue, it's just a matter of definition. Praising NATs for security is like praising a snowstorm because it makes it harder to steal my car. I guess some people really like to see the glass half-full.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @10:35AM (#14856487)
> A NAT prevents direct access from the outside to the LAN, except is certain situations.

Well, an unreliable link prevents direct access from the outside to the LAN, except is certain situations!?

Yes, there are certain scenarios of remote access that are prevented by NAT. But they are a lot less than what people generally think. ISPs' networks not being configured particularly securely is not exactly unheard of, from default passwords on routers to broken VLAN setups in FTTC/B/H setups where people could talk directly on the same ethernet to their neighbours' routers. And even if that is all configured perfectly, you still add their network and their staff to your trusted base. That might not be a big concern for home networks, but this subthread was also and in particular about corporate networks, where targeted attacks are much more likely, and in that case, NAT is in no way a "good enough" solution.

Re:IPv6 Adoption by lolc on Wednesday July 26, 2017 @06:14PM (#14860862)
Crossing a router that does NAT is not easy, here's the possible attacks I see:

1. Somebody on the inside is punching holes for you, then you're already inside and even a firewall would not protect against it.

2. You're hijacking existing connections or sending spoofed packets. That's a vector firewalls also have trouble protecting against.

3. The router NAT implementation might have a defect you can exploit. Because NAT isn't intended as a protection measure, it's implementation might be more likely to have flaws than comparable firewall implementations.[1]

In summary, flipping the NAT switch will give you basic protection much as a basic firewall does. That does not make NAT a good technology. But don't dismiss it just because you don't like it.

[1] Though actually in most cases if you fumble the NAT configuration, you won't have any connections at all. Whereas if you fumble your firewall configuration, your gateway might be open both ways and you don't notice. So NAT is easier to get right. It's not simple, it's ugly and easy!

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @08:30PM (#14861657)
I don't dismiss NAT because I don't like it, I am just stating the fact that it does not provide any security, despite what many people, including you, believe.

Your list is missing one point:

4. They just send you a packet addressed to the internal address of one of your devices.

NAT does not prevent inbound connections. A NAT gateway is just a router with additional NAT functionality. When an inbound packet arrives, a NAT gateway will do two things:

1. Check whether the packet belongs to a flow in the table of NATed connections. If so, rewrite the destination address/port to the internal values.

2. Check whether the destination is in the table of port forwardings. If so, add an entry to the table of NATed connections and rewrite the destination port address to the internal values.

Other than that, it's just a router. If it receives a packet from the WAN that is addressed to the LAN, that probable won't match either of those two cases, so it's simply forwarded unchanged.

The only reason why you cannot just send anyone who uses such a NAT gateway a packet to their LAN is because their ISP doesn't route the address range of their LAN to their router. But the ISP or anyone compromising the ISP can just do that.

That is, unless the same device also contains a stateful packet filter firewall. Which you can have without any NAT, with IPv6 just as with IPv4.

NAT does not provide security, really.

Re:IPv6 Adoption by lolc on Monday July 31, 2017 @05:46PM (#14896170)
NAT first and foremost means using private address ranges as opposed to being reachable on a public address. Sure a properly configured firewall would protect against many scenarios where NAT does not. Still, when somebody asks me whether they should flip the NAT switch on their router at home, I will say "yes it protects you". And that's true.

A compromised upstream is a whole other league from most threats. At that point you've got to think about physically hardening your network equipment because the people who attack your ISP's network equipment would probably find it worthwhile to sneak into your home to compromise your network directly.

Re:IPv6 Adoption by pilif on Wednesday July 26, 2017 @10:39AM (#14856529)
> At the very least, a secure IPv6 network will need to hide end user addresses somehow, because giving everyone a unique, globally-addressable and trackable ID is a security showstopper.

this is a solved problem now. All modern OSes either create short-lived temporary addresses or they hash some machine-unique information with the public prefix (that will change in the same frequency as your current V4 address changes).

Re:IPv6 Adoption by Symbiote on Wednesday July 26, 2017 @07:44AM (#14855331)
> some sort of firewall system

It's called a firewall, and you already have one when you use IPv4. The IPv6 one is much simpler, as there's no address translation (NAT).

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @07:50AM (#14855368)
> It's called a firewall, and you already have one when you use IPv4.

Unless you don't. In any case that doesn't have anything to do with the technologies they cited, as a firewall was not listed among them.

Re:IPv6 Adoption by ra1n85 on Wednesday July 26, 2017 @08:18AM (#14855513)
But why use them when you don't have to? There's benefits to operating a network that handles as little state as necessary.

Running internal services on address space that's not routable on the public internet has its advantages. You can do this with IPv6, but not as easily as you can with IPv4.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @08:31AM (#14855616)
> You can do this with IPv6, but not as easily as you can with IPv4.

It's as trivial as not setting up a route for the address range at your inbound router.

Bonus: If you ever discover that you need to have some service globally routable, it's as easy as adding a route. Try that with your IPv4 NAT setup.

Re:IPv6 Adoption by otabdeveloper1 on Wednesday July 26, 2017 @07:58AM (#14855401)
Any such firewall will need to:

a) Mask end-user addresses somehow. You wouldn't want everyone on your corporate network to get a globally unique, trackable ID.

b) Allow outgoing connections in arbitrary ways but forbid random incoming connections.

c) Some sort of central, highly secured network node where your admins can configure this stuff.

At this point you're close to reinventing NAT, except crappier.

Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @08:16AM (#14855498)
> a) Mask end-user addresses somehow. You wouldn't want everyone on your corporate network to get a globally unique, trackable ID.

Everyone on your corporate network has tons of globally unique, trackable IDs. They're called cookies.

Also, there are IPv6 privacy extensions.

> b) Allow outgoing connections in arbitrary ways but forbid random incoming connections.

Just as with IPv4?

> c) Some sort of central, highly secured network node where your admins can configure this stuff.

That's called a firewall. You need one with IPv4 as well.

> At this point you're close to reinventing NAT, except crappier.

None of that has anything to do with NAT.

Re:IPv6 Adoption by mgbmtl on Wednesday July 26, 2017 @08:21AM (#14855542)
On tracking:

- You can use IPv6 privacy extensions to randomize your IP address. Your computer can have a dozen IP addresses at a given moment, using a different one to access different services, as addresses are being rotated.

- Most corporate networks have static IPs. So while a specific IP might be shared with 100 devices, it's usually easy to fingerprint a visitor uniquely.

- There are tons of other ways to track people, other than their IP. Besides, you want to track them across networks, as they move around.

I'm also very sensitive to tracking, but I think at this point you have to start looking at how to improve your privacy with IPv6, sharing/encouraging good privacy-sensitive practices on IPv6.. not spreading FUD.

Re:IPv6 Adoption by Symbiote on Wednesday July 26, 2017 @08:19AM (#14855522)
a) Do you provide privacy plugins to users' web browsers, and require they use them? If not, the concern is close to irrelevant, but there are privacy-minded ways to assign IPv6 addresses.

b) is a basic feature of the crappiest firewall (the free router from my ISP includes it)

c) is a standard feature of a business-level firewall; secure network access (e.g. with a VLAN) is orthogonal to the choice of IP protocol.

Re:IPv6 Adoption by guelo on Wednesday July 26, 2017 @08:19AM (#14855526)
IPV6 firewalls can do NAT in the same way IPV4 ones can.
Re:IPv6 Adoption by p1mrx on Wednesday July 26, 2017 @06:06PM (#14860810)
NAT66 is possible, in the sense that the protocol won't stop you from implementing or using it. But in practice it's relatively rare, because once you have a nearly-unlimited supply of addresses, NAT typically has more drawbacks than benefits.
Re:IPv6 Adoption by ancarda on Wednesday July 26, 2017 @09:56AM (#14856188)
NAT is not a firewall or security solution. For one thing, it can be opened with UPnP.
Re:IPv6 Adoption by zAy0LfpBZLC8mAC on Wednesday July 26, 2017 @07:42AM (#14855324)
> Not being to address a corporate or home network computer from the outside is a feature, not a bug.

What does that have to do with any of the technologies you cited as being used for security purposes?

Re:IPv6 Adoption by belorn on Wednesday July 26, 2017 @11:36AM (#14857119)
The claim that SNI is a security feature is based on the assumption that it is more common to sniff the wire and collect the IP header rather than doing deep package inspection. I don't see this to be true with modern surveillance equipment and raw network taps.

Additionally, you could create a setup where every visitor dynamically get a ip address from a pool (shared between multiple websites) when asked over encrypted dns. This kind of setup would clearly be superior over SNI's plain text issue.