IP Filtering NFSv4 doesn't block the mount, results in input/output error on file access
Description
Scenario: NFS enabled with NFSv4 checked NFS IP filtering enabled Attempt to mount NFS mount from a VM with a non-whitelisted IP address NFS mount is successful, but results in input/output error when attempting to read the files within the mounted directory
With NFSv3, it's obvious that you are blocked because of the "connection refused" error. With NFSv4, it's not obvious at all what's happening. This was frustrating to troubleshoot because I forgot the IP change I made. Obviously that's my fault, but figured I'd mention it here in case this should be designed to block the mount entirely similar to NFSv3.
Problem/Justification
None
Impact
None
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Show:
Kris Moore
January 16, 2020 at 4:35 PM
Nick,
After looking into this, it appears this is the expected behavior with NFSv4, which is quite different in implementation from NFSv3. We'll be passing on this, unless upstream NFS developers want to make changes from that side.
Scenario:
NFS enabled with NFSv4 checked
NFS IP filtering enabled
Attempt to mount NFS mount from a VM with a non-whitelisted IP address
NFS mount is successful, but results in input/output error when attempting to read the files within the mounted directory
With NFSv3, it's obvious that you are blocked because of the "connection refused" error. With NFSv4, it's not obvious at all what's happening. This was frustrating to troubleshoot because I forgot the IP change I made. Obviously that's my fault, but figured I'd mention it here in case this should be designed to block the mount entirely similar to NFSv3.