Why must NFS authorized networks be unique?

Status
Not open for further replies.

Neek

Dabbler
Joined
Feb 10, 2014
Messages
43
I have just setup FreeNAS 9.2.1, and I'm trying to migrate my setup from a Netgear ReadyNAS.

One issue I've hit is that I've got multiple discrete NFS shares which I'd like to expose to my network (e.g. /mnt/vol1/share1, /mnt/vol1/share2, etc.). If I don't set the "authorized networks" parameter, I get a permission denied error. If I set it to something like "192.168.0.1/24" for each of the shares, only one works, and upon setting the next one, I see this error:

The network 192.168.0.1/24 is already being shared and cannot be used twice for the same filesystem

Any ideas why this is? It is documented as a limitation in the docs for NFS ( http://doc.freenas.org/index.php/Unix_(NFS)_Shares), but I'm still unclear why the limitation exists. I have not seen that before when exporting NFS shares on Linux. Is this unique to FreeBSD? FreeNAS only? Or is Linux not quite follow some standard?

Am I required to create datasets as wrappers around each share? That seems like unnecessary overhead.

Thanks!
 
Status
Not open for further replies.
Top