Search results

Yes

Oke mis read :) When disabled the NAS is not accessible on the NET-2 (totally nothing). So it's not a solution. It also does not explain why only proxmox 6.0 has problems connecting and Proxmox 5.4 with the latest kernel (see whole discussion) has no problems what so ever. Thanks for giving...

Just looked at the setting. It was already checked so its not gonna work. Does this mean your Proxmox can connect over nfs to your Synology NAS?

@Alwin Got any more ideas to get it working?

With the firewall checkbox checked on the Proxmox 6 VM's network card. It also gives the no route to host

you mean rpcinfo from the NAS to the vm? no that works fine rpcinfo -p 192.168.10.241 program vers proto port service 100000 4 tcp 111 100000 3 tcp 111 100000 2 tcp 111 100000 4 udp 111 100000 3 udp 111 100000 2 udp 111

So shutdown the virtual proxmox 6, disable firewall, boot, test --> Fails "no route to host"

Running on the nodes and the freshly installed virtual one

They also work fine I did say in the post that I had changed the Mac address :)

I did now ;) was getting late yesterday. Everything works fine. Node 3 (less spam as it only has 1 network card) and changed the Mac address root@proxmox3:~# ifconfig enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet)...

Everything works fine, NFS still up and running. Adding a new one also works. On Proxmox 5.4-3 root@proxmox:~# pveversion --verbose proxmox-ve: 5.4-1 (running kernel: 5.0.8-2-pve) pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62) pve-kernel-4.15: 5.3-3 pve-kernel-5.0.8-2-pve: 5.0.8-2...

All nodes have differed, from motherboard to external cards. Not 100% how to do this (never done it before, never needed it) Download code -> compile -> install ? You linked to the ubuntu repo, however those packages can't be installed as they expect a ubuntu kernel

So update: 3 clean installs from the ISO installed on the current proxmox cluster. All have 1 network interface on NET-2 Proxmox 5.3-8 -> Connects to NFS without problems Proxmox 5.4-3 -> Connects to NFS without problems Proxmox 6.0-4-> Does not work, rpcinfo gives no route to host Conclusion...

So looking at everything I'm at the "you are the victim of an overzealous firewall" So all firewalls: - Router --> only blocks outside traffic, and traffic to another subnet. But all traffic within an ip range is allowed. (Also did not change before/during/after the upgrade) - NAS --> disabled...

Great minds thing a like? As I just (like 2 mins ago) installed a ubuntu desktop inside Proxmox with only NET-2 :) The ubuntu machine can see and route to the NAS without issue.

I never did anything with ip tables so this should de default iptables -nvL Chain INPUT (policy ACCEPT 24M packets, 30G bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot...

Ill have a read of the post later today. pve-firewall status: Status: disabled/running

Result the same on all nodes rpcinfo -p 192.168.10.10 192.168.10.10: RPC: Remote system error - No route to host rpcinfo -p 192.168.128.5 program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111...

See my first post for mount commands (first one is linux, second is Proxmox) these are both run on CLI/SSH on the nodes. Tried all the versions, does not make a difference, the "Export" box stays empty on the GUI when using the NET-2 NAS ip 1) Handmade in a text editor 2) NET-2 is the default...

So for testing, installed a virtual Proxmox on my Proxmox, and tried to connect to the NFS there. The test node has the same 2 networks. I added the new IP to the NFS permissions in Synology DSM. - Manual mount works on NET-2 and NET-1 - Proxmox mount does not work on NET-2 Remove NET-1...