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:
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/public/wd/product/nas/my_cloud/ex2
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
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 S
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/public/wd/product/nas/my_cloud/ex2_ultra/user-manual-my-cloud-expert-seri
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 /r
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: tim
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 13, trying vers=3, prot=6
mount.nfs: trying 192.168.1.239 pro
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 13, trying vers=3, prot=6
mount.nfs: trying 192.168.1.239 prog
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: tim
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 firewa
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 C
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.
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
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:c
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:c
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:c
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
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 s
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 sy
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.
I
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:b81
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 a
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
> On 21 Jun 2021, at 17: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
>
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
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:9
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
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:c
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 da
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
On 21/06/2021 21:17, Robert McBroom via users wrote:
What is needed to get the ipv6 connection?
Oh, and of course, you'll need the appropriate entry in the server's exports
file.
--
Remind me to ignore comments which aren't germane to the thread.
_
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 fd2
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
34 matches
Mail list logo
