Re: Learning ipv6 quirks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 25/06/2021 11:51, Robert McBroom via users wrote:
tcp6       0      0 :::111 :::*                    LISTEN

@RobertPC ~]# mount -v -t nfs -o vers=3,proto=tcp6 [2600:1702:4860:9dd0::2d]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
mount.nfs: timeout set for Thu Jun 24 23:30:20 2021
Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.
mount.nfs: trying text-based options 'vers=3,proto=tcp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options 'vers=3,proto=tcp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options 'vers=3,proto=tcp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported

This tells me the problem is a configuration or limitation on the NFS Server side.

The output of the netstat command showed that port 111 has a listen.  That is the first contact your client makes with
the server.  The server then tells your client what ports to contact to complete the request.

You can see this when I connect to NFS server via IPv6 after the mount process tells me to use
mount.nfs: trying 2001:b030:112f:2::53 prog 100005 vers 3 prot TCP port 20048.  On the server
And I can see that mountd is listening on the port for both tcp6 and tcp.

[root@f33k ~]# netstat -tlnp | grep mountd
tcp        0      0 0.0.0.0:20048           0.0.0.0:* LISTEN      824/rpc.mountd
tcp6       0      0 :::20048                :::* LISTEN      824/rpc.mountd

When you client used the port it was told to it fails.  A server side issue.

You may want to try with....

mount -v -t nfs -o vers=3,proto=udp6 [2600:1702:4860:9dd0::2d]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy

To see if it fails/works.

I would also be interested in the output of

rpcinfo 2600:1702:4860:9dd0::2d

--
Remind me to ignore comments which aren't germane to the thread.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux