|
how do I secure the maprfs? meaning A. how can I setup that maprfs is accessible only to the local lan(ie bound only to the internal network ips) B. if a cluster is available on wan, require some user password authentication |
|
It doesn't hurt to start with a firewall:
In this case, 192.168.10-12 are imaginary cluster nodes. You probably want to leave off the rule for port 8443 on nodes that don't run the web console. Put your firewall commands in a script and run it from /etc/rc.local. It's very important to control the hosts that can connect to the NFS filesystem, a firewall is just one way to do it. I don't know the correct way to limit specific hosts that can connect to the NFS server in the mapr config files. so maprfs will automaticlly bind to all interfaces?I cannot limit the mapr system to bind only to the internal network?(ie eth0)
(07 Nov '11, 23:57)
sirpy
Set the env var MAPR_SUBNETS to the subnets you want mapr to use. Format is the usual subnet notation using a.b.c.d/shift. A list of subnets (upto 4) can be specified by separating them by commas (no spaces), like so:
Set the above env var in both /etc/environment, as well as /etc/init.d/mapr-warden. By default (ie, when MAPR_SUBNETS is not set), mapr uses all the interfaces on the box.
(08 Nov '11, 00:09)
MC Srivas ♦♦
|