NFS will not connect via dedicated NIC/VLAN

[gck303]

I have a new proxmox host (v8.2.7). I want to connect it via a dedicated 10Gbe network to my Synology NAS using a 192.168.70.x address which has a VLAN 70 (defined by the network switch).

Proxmox will not cannot to the NFS share via .70 address. My understanding is that it should just work without any further config.

The network is all configured correctly configured and the NAS is available on the correct VLAN. PIngs are all routered correctly via the intended nic (ens36). I have checked many more things and everything seems okay.

What is it I am missing?

Thanks, George

 

[LnxBil]

What is it I am missing?

to post error messagesso that we can help you

Have you configured the firewall?

 

[gck303]

The firewall in proxmox is not configured. I have not touched it since it I installed the host.

The route works out to both fine:

root@neptune:/etc/network# traceroute 192.168.70.41
traceroute to 192.168.70.41 (192.168.70.41), 30 hops max, 60 byte packets
 1  192.168.70.65 (192.168.70.65)  3084.654 ms !H  3084.624 ms !H  3084.615 ms !H
root@neptune:/etc/network# traceroute 192.168.0.41
traceroute to 192.168.0.41 (192.168.0.41), 30 hops max, 60 byte packets
 1  192.168.0.41 (192.168.0.41)  1.039 ms  1.012 ms  0.999 ms

But... the telnet to the port does not. When I rcpinfo I do not get any open ports.

root@neptune:/etc/network# rpcinfo -p  192.168.70.42
192.168.70.42: RPC: Remote system error - No route to host
root@neptune:/etc/network# rpcinfo -p  192.168.0.42
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp    892  mountd
    100005    1   tcp    892  mountd
    100005    2   udp    892  mountd
    100005    2   tcp    892  mountd
    100005    3   udp    892  mountd
    100005    3   tcp    892  mountd
    100024    1   udp    662  status
    100024    1   tcp    662  status
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp   4045  nlockmgr
    100021    3   udp   4045  nlockmgr
    100021    4   udp   4045  nlockmgr
    100021    1   tcp   4045  nlockmgr
    100021    3   tcp   4045  nlockmgr
    100021    4   tcp   4045  nlockmgr

But I do not have any firewalls active. At least, not that I am aware of.

 

[alexskysilk]

root@neptune:/etc/network# traceroute 192.168.70.41

root@neptune:/etc/network# rpcinfo -p 192.168.70.42

 

[bbgeek17]

traceroute 192.168.70.41 traceroute to 192.168.70.41 (192.168.70.41), 30 hops max, 60 byte packets 1 192.168.70.65 (192.168.70.65) 3084.654 ms !H 3084.624 ms !H 3084.615 ms !H

a 3 second timing means things are misconfigured... In fact, it most likely means that things have timed out along the way. I would suspect your switch/VLAN configuration first.

!H means host is not reachable via ICMP.

After the trip time, some additional annotation can be printed: !H, !N, or !P (host, network or protocol unreachable), !S (source route failed), !F (fragmentation needed), !X (communication administratively prohibited),
!V (host precedence violation), !C (precedence cutoff in effect), or !<num> (ICMP unreachable code <num>). If almost all the probes result in some kind of unreachable, traceroute will give up and exit.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[LnxBil]

Full ack to @bbgeek17, but why are we tracerouting stuff and talking about routing ... isn't the connection purely local in the same subnet and routing is not involved? I mean yes, we saw the icmp errors, but a simple ping would have sufficed to see the problem.

 

[bbgeek17]

but why are we tracerouting stuff

I was just responding to OP's statement that:

The route works out to both fine:

I agree that this is just basic network troubleshooting. As always, start reducing complexity and systematically check for good communication.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[gck303]

Yeah.... so I think that there was a problem with the Synology. I rebooted it and it kid of went away.

Piece of junk.