Re:Ask HN: What will IPV6 migration actually look like?
by NetStrikeForce on Tuesday March 08, 2016 @07:36PM
(#11249996)
You can avoid RFC1918 overlapping issues by using some overlay networking solution like Wormhole[1], which uses the CGNAT reserved IP space to build a virtual network between your servers, regardless of their location.
This pain point is one of the reasons we've built Wormhole.
Re:Ask HN: What will IPV6 migration actually look like?
by yeukhon on Friday March 04, 2016 @05:43PM
(#11227354)
Well, public services are not. ELB for example. If AWS continues to grow, I think they will eventually exhaust their IPv4 blocks and this is an issue they can't ignore.
Re:Ask HN: What will IPV6 migration actually look like?
by barlo on Friday March 04, 2016 @05:50PM
(#11227383)
ELBs in EC2 Classic support IPv6, but not ELBs in VPCs, as of now at least. You may already have known this but I figured I'd point it out for others: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel...
VPC gives you your own entire rfc1918 space per region, which tho can be a pain to deal with overlap if you have site-to-site VPN, is enough for basically anyone.