Access Synology NFS share over private 10GB lan

T

Tag1735

New Member
Jan 18, 2023
8
0
1
I currently have 2 Proxmox servers and I want to be able to access an NFS share on my Synology NAS but I want it to connect over a separate 10GB network, not my regular 1GB network.

I have a 10GB switch and 10GB nics in the 2 proxmox servers as well as the Synology NAS.
How can I get this to work?
 
At a high level:
- plug new NICs into PVE
- after boot, note the new interface name
- edit /etc/network/interfaces and assign an IP from non-overlapping subnet
- bring the interface up
- assign an IP from same subnet to NAS
- after testing basic connectivity (ping, showmount, etc) - create new storage object in PVE

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
That's what I thought would work. I tried and it didn't work. I gave the NAS 10GB nic 192.168.200.60, the NFS rule for the shared folder 192.168.200.0/24 and on the Proxmox nic I assigned 192.168.200.61. Now I'm using x540-t2 cards on the Proxmox server. I know it works because I connected the nic to my 1GB network - 192.168.2.x and it worked fine.

​

Here is part of my interfaces file:
auto vmbr0
iface vmbr0 inet static
address 192.168.2.41/24
gateway 192.168.2.254
bridge-ports enp4s0f0
bridge-stp off
bridge-fd 0

auto vmbr2
iface vmbr2 inet static
address 192.168.2.0/24
bridge-ports enp4s0f1
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
#Vlan 1

auto vmbr3
iface vmbr3 inet static
address 192.168.10.0/24
bridge-ports enp4s0f2
bridge-stp off
bridge-fd 0
#Vlan 10

auto vmbr1
iface vmbr1 inet static
address 192.168.200.0/24
bridge-ports enp43s0f0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
mtu 1500
#NSFshare on DS2
 
Notations in xxx.xxx.xxx.0/24 are wrong. This would define the typical subnet/ip range from .1 to .254 but not a single IP. For example in vmbr2: 192.168.200.1 (or any other free adress up to .254) without /24 at the end.
 
If I put 192.168.200.1 I still get the red box outline. It will not accept just the IP address.
 
Ok, I have it working if I set it up using my regular 192.168.2.x 1GB home network but it still won't work over the 10GB connection.
Here is how I have the 10GB setup on the Synology and Proxmox
Syn Lan.JPGNFS rule.JPGLinux bridge.JPGAdd NFS share.JPG

When I click the Export window to try to add the share nothing shows up.

Can this have something to do with the MTU?
 
root@pve:~# showmount -e 192.168.200.2
rpc mount export: RPC: Unable to receive; errno = No route to host
root@pve:~# rpcinfo -p 192.168.200.2
192.168.200.2: RPC: Remote system error - No route to host
root@pve:~#
 
Assuming that you were not mistaken when you said "it pings fine", then you possibly have a firewall issue on your NAS.
Can you ssh to NAS? Access its UI (curl -sk https://192.168.200.2) ?

Until the showmount/rpcinfo work, you wont be able to create NFS storage object in PVE.
PVE is using standard Linux NFS tools, which are running on top of standard Linux TCP and UDP stack. Find out what is wrong with that connectivity and everything else will fall inline.

P.S. or may be you added an interface to NAS but the NFS is not listening there. You may need to restart NFS service or reboot the NAS. Check with NAS vendor and their forums what needs to be done to make higher level services aware of the network change.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
It worked fine when I tried using my home network range 192.168.2.x so there can't be any firewall issue.

Yes I can ping it and also SSH to it.

root@pve:~# ping 192.168.200.2
PING 192.168.200.2 (192.168.200.2) 56(84) bytes of data.
64 bytes from 192.168.200.2: icmp_seq=1 ttl=64 time=0.473 ms
64 bytes from 192.168.200.2: icmp_seq=2 ttl=64 time=0.162 ms
64 bytes from 192.168.200.2: icmp_seq=3 ttl=64 time=0.159 ms
64 bytes from 192.168.200.2: icmp_seq=4 ttl=64 time=0.161 ms
64 bytes from 192.168.200.2: icmp_seq=5 ttl=64 time=0.165 ms
64 bytes from 192.168.200.2: icmp_seq=6 ttl=64 time=0.156 ms
^C
--- 192.168.200.2 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5117ms

root@pve:~# ssh admin@192.168.200.2
admin@192.168.200.2's password:

Synology strongly advises you not to run commands as the root user, who has
the highest privileges on the system. Doing so may cause major damages
to the system. Please note that if you choose to proceed, all consequences are
at your own risk.

admin@diskstation2:~$
 
Last edited:
Tag1735 said:
It worked fine when I tried using my home network range 192.168.2.x so there can't be any firewall issue.
Click to expand...
Perhaps not in this case, in general this statement is incorrect. There can always be firewall issues across different networks.

Did you notice P.S. I added to previous post?
bbgeek17 said:
P.S. or may be you added an interface to NAS but the NFS is not listening there. You may need to restart NFS service or reboot the NAS. Check with NAS vendor and their forums what needs to be done to make higher level services aware of the network change.
Click to expand...

From the NAS shell run:
showmount -e 192.168.200.2
rpcinfo -p 192.168.200.2

does that work?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom