On 21/06/2021 21:17, Robert McBroom via users wrote:
Trying to connect to NAS with nfs using the ipv6 addressing.
@RobertPC ~]#ping fd2e:cb3b:f005::ec1 PING fd2e:cb3b:f005::ec1(fd2e:cb3b:f005::ec1) 56 data bytes 64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=1 ttl=64 time=0.120 ms 64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=2 ttl=64 time=0.100 ms
64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=3 ttl=64 time=0.117 ms
@RobertPC ~]#mount -v -t nfs fd2e:cb3b:f005::ec1:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
mount.nfs: timeout set for Mon Jun 21 06:41:56 2021 mount.nfs: Failed to resolve server fd2e: Name or service not known
mount.nfs: trying text-based options 'vers=4.2,addr=fd2e:cb3b:f005::ec1,clientaddr=fd2e:cb3b:f005::ec1'
mount.nfs: Connection refused
@RobertPC ~]# mount -v -t nfs [fd2e:cb3b:f005::ec1%enp2s0]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy mount.nfs: timeout set for Mon Jun 21 09:18:19 2021 mount.nfs: Failed to resolve server fd2e:cb3b:f005::ec1%enp2s0: Name or service not known
The ipv4 connection works
What is needed to get the ipv6 connection?
You really should be using the "actual" ip6 address and not the link address.