I'm on FreeNAS 11.3-U4.1, and I have an NFS share configured (/mnt/vdev_mirror0/shared_media) which I can't mount (NFS share configuration: https://i.imgur.com/oyVgNdo.png).
I'm trying to mount the share on a CentOS 7 server, but trying to mount it from the bind address I have configured (192.168.160.10/24), the mount command just hangs for a few minutes before finally timing out.
I tried binding the NFS service to the same address as the web GUI (192.168.120.200/24), and I was able to mount the share. However, it's not a firewall issue - I've confirmed that I can connect to the desired bind address on port 2049/tcp+udp and port 111/tcp+udp (https://i.imgur.com/XctH5aK.png).
My networking config (https://i.imgur.com/oyVgNdo.png, and static route config: https://i.imgur.com/BYSfj2m.png) is:
* Web GUI bound to interface re0 on 192.168.120.200/24
* NFS service configured to bind to 192.168.160.10/24, which is an LACP interface (lagg0) comprised of physical interfaces em0 and em1
Here is my NFS service configuration: https://i.imgur.com/e6lOXBU.png (I've tried removing the entries from Authorized networks to allow any host to mount it, but with no change in behaviour).
I have a hardware (stateful) firewall separating the NFS client and the FreeNAS server, and I've verified that it's allowing the connection through (which is confirmed by the fact that I can connect to the NFS bind address with netcat).
As mentioned above, if I add 192.168.120.200/24 as a bind address for the NFS service (https://i.imgur.com/bNcMTeV.png), I can mount the share just fine, as can be seen here: https://i.imgur.com/5zUcdG5.png.
Can anyone help me to find out why I can't mount the share from my desired interface?
I'm trying to mount the share on a CentOS 7 server, but trying to mount it from the bind address I have configured (192.168.160.10/24), the mount command just hangs for a few minutes before finally timing out.
I tried binding the NFS service to the same address as the web GUI (192.168.120.200/24), and I was able to mount the share. However, it's not a firewall issue - I've confirmed that I can connect to the desired bind address on port 2049/tcp+udp and port 111/tcp+udp (https://i.imgur.com/XctH5aK.png).
My networking config (https://i.imgur.com/oyVgNdo.png, and static route config: https://i.imgur.com/BYSfj2m.png) is:
* Web GUI bound to interface re0 on 192.168.120.200/24
* NFS service configured to bind to 192.168.160.10/24, which is an LACP interface (lagg0) comprised of physical interfaces em0 and em1
Here is my NFS service configuration: https://i.imgur.com/e6lOXBU.png (I've tried removing the entries from Authorized networks to allow any host to mount it, but with no change in behaviour).
I have a hardware (stateful) firewall separating the NFS client and the FreeNAS server, and I've verified that it's allowing the connection through (which is confirmed by the fact that I can connect to the NFS bind address with netcat).
As mentioned above, if I add 192.168.120.200/24 as a bind address for the NFS service (https://i.imgur.com/bNcMTeV.png), I can mount the share just fine, as can be seen here: https://i.imgur.com/5zUcdG5.png.
Can anyone help me to find out why I can't mount the share from my desired interface?