News for hackers. Stuff that matters.
Re:IPv6 Support for EC2 Instances in Virtual Private Clouds by openasocket on Thursday December 01, 2016 @07:26PM (#13084948)
Might be a dumb question, but why would you want or need more than one IP address for an instance? It's not like more addresses will let you download/upload things faster. Maybe if you want to run multiple web servers on port 80 and give each one a different IP address, but how often do people do that, especially more than 8 times over?
Re:IPv6 Support for EC2 Instances in Virtual Private Clouds by derefr on Thursday December 01, 2016 @07:34PM (#13084973)
Picture running something like Docker on a box, where each container gets its own IPv6 address—with services on their proper ports—instead of mashing a bunch of NATed ports together under the host's IP.

Or, moreover (and this is a bit of a pipe-dream, but it's something I've been hacking on to make possible) picture running something like an Erlang node on a box, where each Erlang process gets its own IPv6 address, fully Internet-routable. This effectively makes Erlang into an SDN vswitch for ephemeral, featherweight virtual machines (which would be oddly similar to AWS's just-announced "Lambda@Edge".)

Re:IPv6 Support for EC2 Instances in Virtual Private Clouds by auganov on Thursday December 01, 2016 @08:33PM (#13085248)
Quantity changes the quality here. IPv6 address space being so large, we can afford to give everyone a virtually infinite number of addresses. Which in turn enables everything to be globally routable. I never cared about IPv6 much. Once I grasped it I am actually so so excited about it.
Re:IPv6 Support for EC2 Instances in Virtual Private Clouds by rajivm on Thursday December 01, 2016 @07:35PM (#13084979)
When you're running services in containers on the machine and want to have them be directly networkable without another overlay network.
Re:IPv6 Support for EC2 Instances in Virtual Private Clouds by kstrauser on Thursday December 01, 2016 @07:35PM (#13084977)
You'd more likely want them for outbound connections. On modern OSes, the IPv6 stack periodically calculates a new IP (see https://tools.ietf.org/html/rfc4941). Think of it as a kind of one-time-use address, so remote machines can't say "hey, I got a download request from this IP last week. I should try to hack it today!"
Re:IPv6 Support for EC2 Instances in Virtual Private Clouds by meddlepal on Thursday December 01, 2016 @07:41PM (#13085017)
Containers. IP per container.