8:17 a.m.
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
@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
mount.nfs: trying text-based options 'addr=fd2e:cb3b:f005::ec1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
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
mount.nfs: trying text-based options 'addr=fd2e:cb3b:f005::ec1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
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
mount.nfs: trying text-based options 'addr=fd2e:cb3b:f005::ec1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
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
mount.nfs: trying text-based options 'addr=fd2e:cb3b:f005::ec1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
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
mount.nfs: trying text-based options 'addr=fd2e:cb3b:f005::ec1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
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
mount.nfs: trying text-based options 'addr=fd2e:cb3b:f005::ec1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
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
mount.nfs: trying text-based options 'addr=fd2e:cb3b:f005::ec1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
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
@RobertPC ~]# mount -v -t nfs 192.168.1.239:/mnt/HD/HD_a2/mcstuffy
/mnt/mcstuffy
mount.nfs: timeout set for Mon Jun 21 06:43:30 2021
mount.nfs: trying text-based options
'vers=4.2,addr=192.168.1.239,clientaddr=192.168.1.185'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options
'vers=4,minorversion=1,addr=192.168.1.239,clientaddr=192.168.1.185'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options
'vers=4,addr=192.168.1.239,clientaddr=192.168.1.185'
mount.nfs: mount(2): Protocol not supported
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 49748
What is needed to get the ipv6 connection?
8:49 a.m.
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.
--
Remind me to ignore comments which aren't germane to the thread.
9:06 a.m.
On 6/21/21 9:49 AM, Ed Greshko wrote:
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.
The router shows multiple ipv6 addresses for the device. How to
distinguish which one is actual?
IPv6 Address 2600:1702:4860:9dd0:c210:8c59:6c38:52fd
Type slaac
Valid Lifetime 3600s
Preferred Lifetime 3600s
IPv6 Address 2600:1702:4860:9dd0:21d:60ff:fe35:b813
Type slaac
Valid Lifetime 3600s
Preferred Lifetime 3600s
IPv6 Address fd2e:cb3b:f005::ec1
Type slaac
Valid Lifetime forever
Preferred Lifetime forever
IPv6 Address fe80::1eb5:75df:b84:98d1
Type slaac
Valid Lifetime forever
Preferred Lifetime forever
------------------------------------------------------------------------
9:16 a.m.
On 21/06/2021 22:06, Robert McBroom via users wrote:
On 6/21/21 9:49 AM, Ed Greshko wrote:
> 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.
>
The router shows multiple ipv6 addresses for the device. How to distinguish which one is
actual?
IPv6 Address 2600:1702:4860:9dd0:c210:8c59:6c38:52fd
Type slaac
Valid Lifetime 3600s
Preferred Lifetime 3600s
IPv6 Address 2600:1702:4860:9dd0:21d:60ff:fe35:b813
Type slaac
Valid Lifetime 3600s
Preferred Lifetime 3600s
IPv6 Address fd2e:cb3b:f005::ec1
Type slaac
Valid Lifetime forever
Preferred Lifetime forever
IPv6 Address fe80::1eb5:75df:b84:98d1
Type slaac
Valid Lifetime forever
Preferred Lifetime forever
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Can you not login to 192.168.1.239 and run the "ip add show" command to see what
the address is?
--
Remind me to ignore comments which aren't germane to the thread.
9:47 a.m.
On 6/21/21 10:16 AM, Ed Greshko wrote:
On 21/06/2021 22:06, Robert McBroom via users wrote:
> On 6/21/21 9:49 AM, Ed Greshko wrote:
>> 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.
>>
> The router shows multiple ipv6 addresses for the device. How to
> distinguish which one is actual?
>
> IPv6 Address 2600:1702:4860:9dd0:c210:8c59:6c38:52fd
> Type slaac
> Valid Lifetime 3600s
> Preferred Lifetime 3600s
> IPv6 Address 2600:1702:4860:9dd0:21d:60ff:fe35:b813
> Type slaac
> Valid Lifetime 3600s
> Preferred Lifetime 3600s
> IPv6 Address fd2e:cb3b:f005::ec1
> Type slaac
> Valid Lifetime forever
> Preferred Lifetime forever
> IPv6 Address fe80::1eb5:75df:b84:98d1
> Type slaac
> Valid Lifetime forever
> Preferred Lifetime forever
>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>
>
Can you not login to 192.168.1.239 and run the "ip add show" command
to see what the address is?
Web interface. It shows
IPv6 IP Address
fe80::200:1eb5:75df:b84:98d1 , 2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
exports configuration is "*"
11:35 a.m.
On 21/06/2021 22:47, Robert McBroom via users wrote:
Web interface. It shows
IPv6 IP Address
fe80::200:1eb5:75df:b84:98d1 , 2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
exports configuration is "*"
Then the IPv6 address you want to use is 2600:1702:4860:9dd0:21d:60ff:fe35:b813
--
Remind me to ignore comments which aren't germane to the thread.
11:37 a.m.
On 22/06/2021 00:35, Ed Greshko wrote:
On 21/06/2021 22:47, Robert McBroom via users wrote:
> Web interface. It shows
>
> IPv6 IP Address
>
> fe80::200:1eb5:75df:b84:98d1 , 2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
>
> exports configuration is "*"
Then the IPv6 address you want to use is 2600:1702:4860:9dd0:21d:60ff:fe35:b813
Oh, I forgot to mention that your IPv6 addresses appear to be Dynamically assigned IP
addresses. Meaning they are not "fixed" and may change. Not the best for uses
in a
client/server environment.
--
Remind me to ignore comments which aren't germane to the thread.
11:48 a.m.
On Tue, 22 Jun 2021 00:37:56 +0800
Ed Greshko wrote:
Oh, I forgot to mention that your IPv6 addresses appear to be
Dynamically assigned IP
addresses. Meaning they are not "fixed" and may change. Not the best for uses
in a
client/server environment.
Isn't there some sort of automagic ipv6 name resolution? I've avoided
ever learning anything about ipv6, but I swear I saw something about that
in some overview once.
12:01 p.m.
On 21 Jun 2021, at 17:48, Tom Horsley <horsley1953(a)gmail.com>
wrote:
On Tue, 22 Jun 2021 00:37:56 +0800
Ed Greshko wrote:
> Oh, I forgot to mention that your IPv6 addresses appear to be Dynamically assigned
IP
> addresses. Meaning they are not "fixed" and may change. Not the best for
uses in a
> client/server environment.
Isn't there some sort of automagic ipv6 name resolution? I've avoided
ever learning anything about ipv6, but I swear I saw something about that
in some overview once.
Just as with ipv4 you want a fixed address for servers and its the same with ipv6.
You clearly want DNS to provide a name for the server to avoid using the long address.
But you do not want that address to change after you have done the look up!
Barry
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
6:25 p.m.
On 22/06/2021 00:48, Tom Horsley wrote:
On Tue, 22 Jun 2021 00:37:56 +0800
Ed Greshko wrote:
> Oh, I forgot to mention that your IPv6 addresses appear to be Dynamically assigned
IP
> addresses. Meaning they are not "fixed" and may change. Not the best for
uses in a
> client/server environment.
Isn't there some sort of automagic ipv6 name resolution? I've avoided
ever learning anything about ipv6, but I swear I saw something about that
in some overview once.
Could you define a bit more what you mean by "name resolution"? Or are you
thinking about
the Stateless IP assignment I mention in a different reply?
--
Remind me to ignore comments which aren't germane to the thread.
6:34 p.m.
On Tue, 22 Jun 2021 07:25:23 +0800
Ed Greshko wrote:
Could you define a bit more what you mean by "name
resolution"? Or are you thinking about
the Stateless IP assignment I mention in a different reply?
I have no idea :-). Maybe what I read about had something to do with mdns
providing symbolic names on the local lan? (I don't even know if that
is a real thing :-).
6:43 p.m.
On 22/06/2021 07:34, Tom Horsley wrote:
On Tue, 22 Jun 2021 07:25:23 +0800
Ed Greshko wrote:
> Could you define a bit more what you mean by "name resolution"? Or are you
thinking about
> the Stateless IP assignment I mention in a different reply?
I have no idea :-). Maybe what I read about had something to do with mdns
providing symbolic names on the local lan? (I don't even know if that
is a real thing :-).
Well, mdns is related to use of the .local domain and Avahi/Bonjour. Neither of which I
utilize.
--
Remind me to ignore comments which aren't germane to the thread.
1:36 p.m.
On 6/21/21 12:37 PM, Ed Greshko wrote:
On 22/06/2021 00:35, Ed Greshko wrote:
> On 21/06/2021 22:47, Robert McBroom via users wrote:
>> Web interface. It shows
>>
>> IPv6 IP Address
>>
>> fe80::200:1eb5:75df:b84:98d1 ,
>> 2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
>>
>> exports configuration is "*"
>
> Then the IPv6 address you want to use is
> 2600:1702:4860:9dd0:21d:60ff:fe35:b813
>
Oh, I forgot to mention that your IPv6 addresses appear to be
Dynamically assigned IP
addresses. Meaning they are not "fixed" and may change. Not the best
for uses in a
client/server environment.
Assignment is done by the ISP router. While not fixed they don't change
much. Stable through power failure and reboot for the most part.
2:08 p.m.
On 22/06/2021 02:36, Robert McBroom via users wrote:
On 6/21/21 12:37 PM, Ed Greshko wrote:
> On 22/06/2021 00:35, Ed Greshko wrote:
>> On 21/06/2021 22:47, Robert McBroom via users wrote:
>>> Web interface. It shows
>>>
>>> IPv6 IP Address
>>>
>>> fe80::200:1eb5:75df:b84:98d1 , 2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
>>>
>>> exports configuration is "*"
>>
>> Then the IPv6 address you want to use is 2600:1702:4860:9dd0:21d:60ff:fe35:b813
>>
>
> Oh, I forgot to mention that your IPv6 addresses appear to be Dynamically assigned
IP
> addresses. Meaning they are not "fixed" and may change. Not the best for
uses in a
> client/server environment.
>
Assignment is done by the ISP router. While not fixed they don't change much. Stable
through power failure and reboot for the most part.
There are basically 2 types of IPv6 IP Dynamic assignment techniques. State-full, and
Stateless.
Briefly, State-full is DHCPv6.
While Stateless is a bit more involved. In Stateless the device needing an IP address
receives a Router Announcement which tells it the IP address of the router and subnet
information. From there
a unique IPv6 address is determined.
Given the *huge* IPv6 address space they can both can stay the same for quite some time
but that is not guaranteed.
Not an ideal situation for client/server.
--
Remind me to ignore comments which aren't germane to the thread.
12:46 p.m.
On 6/21/21 8:17 AM, 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
Try putting the IPv6 address inside square brackets.
mount [fd2e:cb3b:f005::ec1]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
--
========================================================================
In Soviet Russia, Google searches you!
========================================================================
10:41 p.m.
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).
12:13 a.m.
On 22/06/2021 11:41, 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).
I got the impression from the OP that the NFS server is not a Fedora system. When I asked
about logging into
the NFS and running the "ip addr show" command the response was "Web
interface. It shows". That doesn't
seem to be what one would do if the NFS server were Fedora based.
--
Remind me to ignore comments which aren't germane to the thread.
12:25 a.m.
On 22/06/2021 11:41, 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 [::]:*
Oh, and BTW, using the same mount command trying to mount a share from my Synology NAS
using the
link IPv6 address of the NAS fails.
That is one of the reasons I feel the OP should be using the actual IPv6 address and not
the link address.
--
Remind me to ignore comments which aren't germane to the thread.
10:55 p.m.
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).
BusyBox v1.30.1 (2020-09-04 02:41:28 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
root@MyCloudEX2Ultra ~ # ss -ln | grep :2049
-sh: ss: not found
root@MyCloudEX2Ultra ~ # firewall-cmd --list-services
-sh: firewall-cmd: not found
root@MyCloudEX2Ultra ~ # help
Built-in commands:
------------------
. : [ [[ alias bg break cd chdir command continue echo eval exec
exit export false fg getopts hash help history jobs kill let
local printf pwd read readonly return set shift source test times
trap true type ulimit umask unalias unset wait
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
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain SSHBFATK (1 references)
target prot opt source destination
LOG all anywhere anywhere limit: avg
5/min burst 5 LOG level info prefix "SSH: Detect brute force atk! "
DROP all anywhere anywhere
root@MyCloudEX2Ultra ~ # cat /etc/hosts
127.0.0.1 localhost localhost.localdomain
192.168.1.239 MyCloudEX2Ultra MyCloudEX2Ultra
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
11:34 p.m.
On 23/06/2021 11:55, 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).
BusyBox v1.30.1 (2020-09-04 02:41:28 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
root@MyCloudEX2Ultra ~ # ss -ln | grep :2049
-sh: ss: not found
root@MyCloudEX2Ultra ~ # firewall-cmd --list-services
-sh: firewall-cmd: not found
root@MyCloudEX2Ultra ~ # help
Built-in commands:
------------------
. : [ [[ alias bg break cd chdir command continue echo eval exec
exit export false fg getopts hash help history jobs kill let
local printf pwd read readonly return set shift source test times
trap true type ulimit umask unalias unset wait
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
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain SSHBFATK (1 references)
target prot opt source destination
LOG all anywhere anywhere limit: avg 5/min burst 5 LOG level info
prefix "SSH: Detect brute force atk! "
DROP all anywhere anywhere
root@MyCloudEX2Ultra ~ # cat /etc/hosts
127.0.0.1 localhost localhost.localdomain
192.168.1.239 MyCloudEX2Ultra MyCloudEX2Ultra
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
And you may also want to run nmap, as root, from your fedora system
nmap -sS -6 The-IPV6-address-here
and just to be sure of IPv4
nmap -sS The-IPV4-address-here
--
Remind me to ignore comments which aren't germane to the thread.
1:54 a.m.
And you may also want to run nmap, as root, from your fedora system
nmap -sS -6 The-IPV6-address-here
and just to be sure of IPv4
nmap -sS The-IPV4-address-here
FWIW,
[root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53
Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:51 CST
Nmap scan report for 2001:b030:112f:2::53
Host is up (0.00039s latency).
PORT STATE SERVICE
2049/tcp filtered nfs
Means the firewall is blocking the port
[root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53
Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:47 CST
Nmap scan report for 2001:b030:112f:2::53
Host is up (0.00018s latency).
PORT STATE SERVICE
2049/tcp closed nfs
Means the firewall is not blocking the port but no service is listening on that port
[root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53
Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:46 CST
Nmap scan report for 2001:b030:112f:2::53
Host is up (0.00013s latency).
PORT STATE SERVICE
2049/tcp open nfs
Means the firewall is not blocking the port and a service is listening on the port
--
Remind me to ignore comments which aren't germane to the thread.
12:58 p.m.
On 6/22/21 11:54 PM, Ed Greshko wrote:
[root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53
Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:47 CST
Nmap scan report for 2001:b030:112f:2::53
Host is up (0.00018s latency).
PORT STATE SERVICE
2049/tcp closed nfs
Means the firewall is not blocking the port but no service is
listening on that port
That's not entirely accurate. If the firewall action is REJECT rather
than DROP, you'll see the same output from nmap. "closed" can mean
either that the port is not open, or that the firewall is blocking
access with a REJECT action.
And nmap isn't necessary to establish this, since the logs already
provided included a "connection refused" response to the IPv6 mount attempt.
6:02 p.m.
On 24/06/2021 01:58, Gordon Messmer wrote:
On 6/22/21 11:54 PM, Ed Greshko wrote:
> [root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53
> Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:47 CST
> Nmap scan report for 2001:b030:112f:2::53
> Host is up (0.00018s latency).
>
> PORT STATE SERVICE
> 2049/tcp closed nfs
>
> Means the firewall is not blocking the port but no service is listening on that port
That's not entirely accurate. If the firewall action is REJECT rather than DROP,
you'll see the same output from nmap. "closed" can mean either that the
port is not open, or that the firewall is blocking access with a REJECT action.
OK, good to know, thanks. I don't think I've encountered that which may explain
my ignorance.
And nmap isn't necessary to establish this, since the logs already provided included
a "connection refused" response to the IPv6 mount attempt.
Sure. But it couldn't hurt. :-)
--
Remind me to ignore comments which aren't germane to the thread.
6:10 p.m.
On 6/25/21 4:02 PM, Ed Greshko wrote:
On 24/06/2021 01:58, Gordon Messmer wrote:
> On 6/22/21 11:54 PM, Ed Greshko wrote:
>> [root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53
>> Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:47 CST
>> Nmap scan report for 2001:b030:112f:2::53
>> Host is up (0.00018s latency).
>>
>> PORT STATE SERVICE
>> 2049/tcp closed nfs
>>
>> Means the firewall is not blocking the port but no service is
>> listening on that port
>
>
> That's not entirely accurate. If the firewall action is REJECT rather
> than DROP, you'll see the same output from nmap. "closed" can mean
> either that the port is not open, or that the firewall is blocking
> access with a REJECT action.
OK, good to know, thanks. I don't think I've encountered that which may
explain my ignorance.
It's very rare. In almost all cases, DROP is the default. So the
"closed" result can be assumed to mean what you said it means.
11:59 p.m.
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.
6:59 a.m.
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?
7:22 a.m.
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?
--
Remind me to ignore comments which aren't germane to the thread.
6:02 p.m.
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.
--
Remind me to ignore comments which aren't germane to the thread.
10:51 p.m.
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.
_______________________________________________
@MyCloudEX2Ultra ~ # netstat -tln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:54553 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:46363 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:36507 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:2812 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:56864 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN
tcp 0 0 192.168.1.239:49154 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9091 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3688 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:53291 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
tcp 0 0 192.168.1.239:5357 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:37969 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7575 0.0.0.0:* LISTEN
tcp6 0 0 ::1:2812 :::* LISTEN
tcp6 0 0 :::34109 :::* LISTEN
tcp6 0 0 :::445 :::* LISTEN
tcp6 0 0 :::8543 :::* LISTEN
tcp6 0 0 :::56864 :::* LISTEN
tcp6 0 0 :::49152 :::* LISTEN
tcp6 0 0 :::8001 :::* LISTEN
tcp6 0 0 :::8002 :::* LISTEN
tcp6 0 0 :::8003 :::* LISTEN
tcp6 0 0 :::6600 :::* LISTEN
tcp6 0 0 :::3689 :::* LISTEN
tcp6 0 0 :::139 :::* LISTEN
tcp6 0 0 fe80::200:c0ff:fe3:5357 :::* LISTEN
tcp6 0 0 :::4430 :::* LISTEN
tcp6 0 0 :::111 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::21 :::* LISTEN
tcp6 0 0 :::22 :::* 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
2:37 a.m.
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.
7:41 a.m.
On 25/06/2021 11:51, Robert McBroom via users wrote:
mount.nfs: requested NFS version or transport protocol is not supported
Is this your server?
https://documents.westerndigital.com/content/dam/doc-library/en_gb/assets...
I couldn't find any "advanced" settings for NFS.
Is there a /etc/nfs.conf on the device?
If so, post that too.
--
Remind me to ignore comments which aren't germane to the thread.
8:13 a.m.
On 6/25/21 8:41 AM, Ed Greshko wrote:
On 25/06/2021 11:51, Robert McBroom via users wrote:
>
> mount.nfs: requested NFS version or transport protocol is not supported
Is this your server?
https://documents.westerndigital.com/content/dam/doc-library/en_gb/assets...
I couldn't find any "advanced" settings for NFS.
Is there a /etc/nfs.conf on the device?
If so, post that too.
That is the device. No /etc/nfs.conf. The web interface settings are
limited. The OS 5 firmware update seems to be five years behind. Windows
centric with some MacOS.
@RobertPC ~]# rpcinfo 2600:1702:4860:9dd0::2d
program version netid address service owner
100000 4 tcp6 ::.0.111 portmapper superuser
100000 3 tcp6 ::.0.111 portmapper superuser
100000 4 udp6 ::.0.111 portmapper superuser
100000 3 udp6 ::.0.111 portmapper superuser
100000 4 tcp 0.0.0.0.0.111 portmapper superuser
100000 3 tcp 0.0.0.0.0.111 portmapper superuser
100000 2 tcp 0.0.0.0.0.111 portmapper superuser
100000 4 udp 0.0.0.0.0.111 portmapper superuser
100000 3 udp 0.0.0.0.0.111 portmapper superuser
100000 2 udp 0.0.0.0.0.111 portmapper superuser
100000 4 local /var/run/rpcbind.sock portmapper superuser
100000 3 local /var/run/rpcbind.sock portmapper superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100227 3 tcp 0.0.0.0.8.1 nfs_acl superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100227 3 udp 0.0.0.0.8.1 nfs_acl superuser
100021 1 udp 0.0.0.0.233.132 nlockmgr superuser
100021 3 udp 0.0.0.0.233.132 nlockmgr superuser
100021 4 udp 0.0.0.0.233.132 nlockmgr superuser
100021 1 tcp 0.0.0.0.148.81 nlockmgr superuser
100021 3 tcp 0.0.0.0.148.81 nlockmgr superuser
100021 4 tcp 0.0.0.0.148.81 nlockmgr superuser
100021 1 udp6 ::.139.111 nlockmgr superuser
100021 3 udp6 ::.139.111 nlockmgr superuser
100021 4 udp6 ::.139.111 nlockmgr superuser
100021 1 tcp6 ::.133.61 nlockmgr superuser
100021 3 tcp6 ::.133.61 nlockmgr superuser
100021 4 tcp6 ::.133.61 nlockmgr superuser
100005 1 udp 0.0.0.0.199.93 mountd superuser
100005 1 tcp 0.0.0.0.142.155 mountd superuser
100005 2 udp 0.0.0.0.143.61 mountd superuser
100005 2 tcp 0.0.0.0.208.43 mountd superuser
100005 3 udp 0.0.0.0.182.82 mountd superuser
100005 3 tcp 0.0.0.0.181.27 mountd superuser
100024 1 udp 0.0.0.0.132.68 status superuser
100024 1 tcp 0.0.0.0.213.25 status superuser
@RobertPC ~]# mount -v -t nfs -o vers=3,proto=udp6
[2600:1702:4860:9dd0::2d]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
mount.nfs: timeout set for Sat Jun 26 09:10:45 2021
mount.nfs: trying text-based options
'vers=3,proto=udp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'vers=3,proto=udp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'vers=3,proto=udp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported
Never tries prog 100005 or a port same as the tcp6 try
8:46 a.m.
On 26/06/2021 21:13, Robert McBroom via users wrote:
@RobertPC ~]# mount -v -t nfs -o vers=3,proto=udp6
[2600:1702:4860:9dd0::2d]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
mount.nfs: timeout set for Sat Jun 26 09:10:45 2021
mount.nfs: trying text-based options
'vers=3,proto=udp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'vers=3,proto=udp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'vers=3,proto=udp6,addr=2600:1702:4860:9dd0::2d'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported
Well, without knowing what the nfs-server uses for a configuration makes it hard to see if
there
is an option that needs changing.
On Fedora systems udp is turned off by default. The nfs.conf has "# udp=n" in
the [nfsd] section.
So, if I try to mount using udp I get....
[root@f34k2 ~]# mount -v -o proto=udp6,vers=3 f33k:/home/egreshko /mnt
mount.nfs: timeout set for Sat Jun 26 21:38:00 2021
mount.nfs: trying text-based options
'proto=udp6,vers=3,addr=2001:b030:112f:2::53'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'proto=udp6,vers=3,addr=2001:b030:112f:2::53'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'proto=udp6,vers=3,addr=2001:b030:112f:2::53'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported
And when I uncomment, change to "udp=y", and restart the server I get..
[root@f34k2 ~]# mount -v -o proto=udp6,vers=3 f33k:/home/egreshko /mnt
mount.nfs: timeout set for Sat Jun 26 21:43:50 2021
mount.nfs: trying text-based options
'proto=udp6,vers=3,addr=2001:b030:112f:2::53'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 2001:b030:112f:2::53 prog 100003 vers 3 prot UDP 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
So, there isn't more to say. The issue is on the server side and I've no idea
about that unit to
look/find a configuration.
You may need to be happy with IPv4. FWIW it is most common, and recommended, to mount
using
version 4 and TCP.
--
Remind me to ignore comments which aren't germane to the thread.
1034
days inactive
1039
days old
33 comments
7 participants
participants (7)
-
Barry Scott -
Ed Greshko -
Gordon Messmer -
Ian Pilcher -
Robert McBroom -
Samuel Sieb -
Tom Horsley