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.