-
Notifications
You must be signed in to change notification settings - Fork 8
3_3 Others
We only looked superficially on implementations apart from Linux and Windows, nevertheless, we sometimes see these systems in the field, so we collected some noteworthy information and are going to share it here.
mountd on FreeBSD reports subnets without a subnet mask.
This can lead to confusion.
For example, showmount -e may return the following result.
/export 10.123.45.0
It could be 10.123.45.0/24, 10.123.45.0/28 but it could also be 10.123.45.0/8 which means that host 10.9.8.7 also has access. In this case, everything after 10. is irrelevant.
In the /etc/exports, the allowed subnets are configured in two ways:
/export1 -network=10.123.45.0/8
/export2 -network=10.123.45.0 -mask 255.0.0.0
This could mean that even if your IP is different from the one that is displayed by showmount, you may still have access to the export if the subnet mask is shorter than expected.
Based on our testing, the TrueNAS UI automatically corrects the address and sets all irrelevant bits of the IP address to 0.
The NFS related services like portmap and mountd on HP-UX support TCP but can only handle one request in each connection.
If you send a second request, the server will terminate the TCP connection.
To avoid this issue, create a new TCP connection for each request or use UDP.
nfs_analyze will detect this and automatically start a new connection for each request.
NetApp servers can be identified by the netapp partner protocol reported by portmap, which has the number 400010.
Older versions may not show any exports when running showmount -e, they only react to mount requests for specific directories.
When performing a NFSv3 READDIRPLUS operation, the server will not return file handles for subdirectories which are also the root directories of other exports.
In order to get the file handles, you have to perform a separate LOOKUP request for these directories.
fuse_nfs does this automatically if the --fix-nested-exports option is specified.