Add checks for NFS overlapping networks

Description

When creating complex NFS shares the freenas ui will not let you create overlapping NFS share settings for the same export.

For example:

export /mnt/tank/export to all machines on the subnet 192.168.0.0/24 as read only.

export /mnt/tank/export to administrator.localdomain (192,168.0.2) on the same subnet as read/write.

When doing this from the ui you are presented with a error stating you cannot overlap the NFS shares.

Generic error from the ui:

The network and host must be unique per share and per filesystem or
directory. Since :file:`/etc/exports` does not act like an ACL, the
rule to apply is undefined among overlapping networks or when using
the same share with multiple hosts.

Now if we manually create the shares ourselves it works without issue applying the correct permissions.

If we check the man page for freebsd exports : https://www.freebsd.org/cgi/man.cgi?exports(5)

We are presented with examples showing this exact usage:

/u2 -maproot=root friends
/u2 -alldirs -network cis-net -mask cis-mask
The file system rooted at
/u2
is exported to the hosts in ``friends '' with root mapped to UID and groups associated with ``root' '; it is exported to all hosts on network ``cis-net' ' allowing mounts at any directory within /u2.

Things means the ui would need to be changed to allow overlapping networks in NFS shares to allow more complex sharing without having to manually edit the exports file.

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Bug Clerk August 6, 2019 at 2:40 PM

Bug Clerk August 6, 2019 at 2:24 PM

Joe Maloney August 6, 2019 at 1:47 PM
Edited

Automation caught API failure during the second attempt to test before release push. 

Bug Clerk July 25, 2019 at 5:07 PM
Edited

Bug Clerk July 10, 2019 at 3:18 PM

Complete
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Affects versions

Priority

More fields

Katalon Platform

Created June 21, 2019 at 5:35 PM
Updated July 1, 2022 at 4:35 PM
Resolved August 7, 2019 at 8:11 PM