Re: [Moosefs-users] Having a client outside of the "mfs network" using NAT

[Ricardo J. B. <ric...@da...>]

El Vie 22 Julio 2011, Kef escribió:
> Hello !
>
> I have some difficulties to configure my chunk servers and a client.
> The two chunks server (and the master) are in the same network (a private
> network in 192.168.0.X). All this servers share the same public IP address
> and are accessible from the outside using NAT.
>
> I have a client which is outside the network. It can mount the filesystem a
> write to it, but it can't download the files (and after some delay, a "ls
> -la" displays a size of 0 for each file).
>
> Is it possible to use MFS with NAT, where my chunks server are in the same
> network as my master server (they are connected to the master server using
> the public adress IP, the 9420 port is redirected to the master server)
> with a client outside of the network ?

I don't think you can, at least not easily.

From the docs [1]:

"Note: It's important which local IP address mfschunkserver uses to connect to 
mfsmaster. This address is passed by mfsmaster to MFS clients (mfsmount) and 
other chunkservers to communicate with the chunkserver, so it must be 
remotely accessible. Thus master address (MASTER_HOST) must be set to such 
for which chunkserver will use proper local address to connect - usually 
belonging to the same network as all MFS clients and other chunkservers. 
Generally loopback addres (localhost, 127.0.0.1) can't be used as 
MASTER_HOST, as it would make the chunkserver inaccessible for any other host 
(such configuration would work only on single machine running all of 
mfsmaster, mfschunkserver and mfsmount)."


[1] http://www.moosefs.org/reference-guide.html

Cheers.
-- 
Ricardo J. Barberis
Senior SysAdmin / ITI
Dattatec.com :: Soluciones de Web Hosting
Tu Hosting hecho Simple!