SOLVED nfs shares networks and hosts

[Ofloo]

Usually when I've used nfs in the past, I assume first match is most greedy and will set those flags but for some reason that's not the case.

example:

/mnt/lake/dir -alldirs -mapall="root" -network 10.0.0.10/32
/mnt/lake/dir -alldirs -ro -network 10.0.0.0/24

I would assume the if 10.0.0.10/32 mounts a share it would get read/write access why isn't that so? I've tried changing the order but that doesn't do much, why is this or better yet how do I solve this?

 

[Patrick M. Hausen]

Use just the IP address without the /32 and remove the -network.

i don't know from the top of my head if "statements in order" or "more specific" is supposed to work like you intend but you should first fix your syntax and specify hosts as hosts.

Chapter 32. Network Servers

This chapter covers some of the more frequently used network services on UNIX systems

www.freebsd.org

 

[Ofloo]

Did that same thing happens, I initially started with hosts but then moved to networks.

/mnt/lake/dir -alldirs -mapall="root" 10.0.0.10
/mnt/lake/dir -alldirs -ro -network 10.0.0.0/24

 

[Ofloo]

My bad just found out what was wrong, been so focused on nfs that i didn't notice the whole pool was in read-only.