On 24/06/2021 19:59, Robert McBroom via users wrote:
With ipv4 the mount is successful with apparently trying alternate port and protocol automatically.
mount.nfs: trying text-based options 'addr=192.168.1.239' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.1.239 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.1.239 prog 100005 vers 3 prot UDP port 37811
Is there a way to tell ipv6 mount to use prot UDP port 37811?
You can try....
[egreshko@meimei ~]$ sudo mount -t nfs -o vers=3 [2001:b030:112f:2::53]:/home/egreshko /mnt
[egreshko@meimei ~]$ df -T | grep nfs nas:/volume1/aux nfs4 5621463168 1996292608 3625170560 36% /aux nas:/volume1/misty nfs4 5621463168 1996292608 3625170560 36% /home/egreshko/misty [2001:b030:112f:2::53]:/home/egreshko nfs 32504832 17629184 14537216 55% /mnt
Have you determined why nfs V4 isn't available?
Oh, BTW, I should have sent the -v version.
[egreshko@meimei ~]$ sudo mount -t nfs -o vers=3 -v [2001:b030:112f:2::53]:/home/egreshko /mnt mount.nfs: timeout set for Fri Jun 25 07:02:41 2021 mount.nfs: trying text-based options 'vers=3,addr=2001:b030:112f:2::53' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 2001:b030:112f:2::53 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 2001:b030:112f:2::53 prog 100005 vers 3 prot UDP port 20048
You really should post examples of IPv6 test which fail and not IPv4 examples which succeed.