From: Scott D. <sd...@cl...> - 2012-04-23 15:51:31
|
On Sat, Apr 21, 2012 at 6:17 AM, Fabien Germain <fab...@gm...>wrote: > Hi Scott, hi list ! > > 2012/4/20 Scott Duckworth <sd...@cl...>: > > IPv6 is coming whether we want it or not. Here's some evidence: > > I agree with your arguments, and that IPv6 is a need in MooseFS. But > just one question : > > > Many parts of the world have exhausted their IPv4 address blocks, meaning > > you can only get new IPv4 addresses if they are already allocated to you > or > > from IPv4 scavengers [ > http://en.wikipedia.org/wiki/IPv4_address_exhaustion] > > Why would someone use *public* IPv4 addresses on chunkservers ??? In > our case, we use private IP on a dedicated VLAN for all the cluster, > and several clients have a public IP (to "export" the data), and a > private IP in the MooseFS VLAN. > If somebody wanted to use MooseFS over a WAN, I'm assuming that the chunkservers and master server would need to be reachable from each other and from the clients. This could either be accomplished with a VPN using private IP addresses or directly over the Internet using public IP addresses (hopefully encrypted with IPsec). This would be the case with either IPv4 or IPv6, only that IPv6 doesn't exactly have private address ranges. Regardless of where MooseFS is being used, LAN or WAN, IPv6 will eventually become a consideration. Even though it is WAN that is driving IPv6, I expect it will eventually overcome IPv4 even for internal network traffic. If network administrators are going to have to support IPv6 anyways, why also support IPv4 once everything is reachable via IPv6? At that point IPv4 is just that old rusty protocol that we used to have to use which is now getting in the way. Anybody remember IPX/SPX? [ http://en.wikipedia.org/wiki/IPX/SPX] |