Re: Learning ipv6 quirks

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

 



On 6/23/21 12:59 AM, Gordon Messmer wrote:
On 6/22/21 8:55 PM, Robert McBroom via users wrote:
On 6/21/21 11:41 PM, Gordon Messmer wrote:
On 6/21/21 6:17 AM, Robert McBroom via users wrote:
@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:42:25 2021
mount.nfs: trying text-based options 'vers=4.2,addr=fd2e:cb3b:f005::ec1,clientaddr=fd2e:cb3b:f005::ec1'
mount.nfs: mount(2): Connection refused

1: Is the nfs port open on ipv6?  Use "ss -ln | grep :2049" and look for a listening port with an IPv6 address, like:
    tcp    LISTEN     0      64     [::]:2049 [::]:*
2: Does your firewall allow access to port 2049 on IPv6?  Use "firewall-cmd --list-services" and look for "nfs", or use "ip6tables -L" and look for the input chain for your default zone (possibly IN_public_allow).

root@MyCloudEX2Ultra ~ # ss -ln | grep :2049
-sh: ss: not found


In that case you probably only have busybox's netstat, and I don't know what flags it supports.  Try "netstat -tln" and if that doesn't work maybe "netstat -ln" to get a list of the listening ports.


root@MyCloudEX2Ultra ~ # ip6tables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
           tcp      anywhere             anywhere tcp dpt:22 state NEW recent: SET name: SSH side: source mask: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff SSHBFATK   tcp      anywhere             anywhere tcp dpt:22 state NEW recent: UPDATE seconds: 600 hit_count: 201 name: SSH side: source mask: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff


The system's input chain should allow NFS traffic on IPv6 by virtue of the ACCEPT policy.  That suggests that the NFS service isn't listening on an IPv6 network socket.

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?
_______________________________________________
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