- Minor
In order to improve performance between some of my servers and Unraid I setup the server vlan in unraid and assigned Unraid a static IP on the vlan subnet. While the primary interface is on a different subnet.
So now my main ethernet interface is reachable in ip: 10.0.0.20
And I have a vlan setup with ip: 10.10.10.100 as well
Mounting a share using 10.0.0.20 goes fine however trying to mount the same share on the same machine using 10.10.10.100 times out.
Checking exports I found the shares are exported to both 10.0.0.20 and 10.10.10.100:
showmount --exports 10.0.0.20
Export list for 10.0.0.20:
/mnt/user/proxmox 10.10.10.9,10.10.10.7,10.10.10.6,10.10.10.5
showmount --exports 10.10.10.100
Export list for 10.10.10.100:
/mnt/user/proxmox 10.10.10.9,10.10.10.7,10.10.10.6,10.10.10.5
So it seems NFS is exporting the shares as they should. However, when I do a port scan with netmap it seems the NFS service is either not listening or the port is closed on ip 10.10.10.100
Scan from 10.0.0.20 shows:
139/tcp open netbios-ssn Samba smbd 4.6.2
445/tcp open netbios-ssn Samba smbd 4.6.2
2049/tcp open nfs 3-4 (RPC #100003)
3551/tcp open apcupsd apcupsd
3702/tcp open tcpwrapped
5355/tcp open tcpwrapped
Scan from 10.10.10.100 shows:
139/tcp open netbios-ssn Samba smbd 4.6.2
445/tcp open netbios-ssn Samba smbd 4.6.2
3551/tcp open apcupsd apcupsd
3702/tcp open tcpwrapped
5355/tcp open tcpwrapped
As can be seen port 2049/tcp is not responding on 10.10.10.100 while it is responding on 10.0.0.20
As the folders are exported in NFS and Samba seems to be working properly on both IP's I can only assume this is not intended behavior.
Hence filing a bug report.