Use IPv6 to "simulate" a private local network?
Is this true, or am I missing something important here? I am planning on using multicast/unicast discovery for distributed services in the private network.
Thanks for any comments!
11 Replies
@nivex:
Or you could set it up now, be used to how it all works, and be ahead of the game.
Except that the "game" is a vague and moving target with no real timeframe for viability and absolutely zero ROI for the foreseeable future.
Using your "idea", the TSA would have been setup and waiting at Kitty Hawk to make Wilbur take his shoes off for a security inspection.
http://forum.linode.com/viewtopic.php?p=39528
The obvious advantage with IPv6 is the fact that you can request an ip pool and simply implement one firewall rule for all linodes within that pool. Simple, secure, easy. It's a lot more complex with IPv4.
I don't see any downside to going with ipv6.
Have fun!
@Guspaz:
You could also use the private IPv4 addresses, you don't need IPv6 or a VPN to do this.
I thought all linodes are in the same LAN? Using IPv4 I won't have my own subnet, hence I'll have to change firewall rules on each server, when I bring new servers up or shut some down. Without either my own subnet, or constantly managing firewall rules, I don't see how I can have secure multicast discovery, or even protect myself against port-sniffing from other linodes.
@nickdan:
The obvious advantage with IPv6 is the fact that you can request an ip pool and simply implement one firewall rule for all linodes within that pool. Simple, secure, easy. It's a lot more complex with IPv4.
Yes that was my thinking. Just needed some reassurance that it's indeed secure…
Thanks
@bryantrv:
Though I believe the traffic on the private network also doesn't count against bandwidth, but ipv6 traffic would. Could be a huge factor.
IPv6 traffic over the private network doesn't count against your bandwidth quota. Seehttp://www.linode.com/IPv6/