News for hackers. Stuff that matters.
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.