Re: [Dorset] Changed IP address lost NAS, but........
Hi Tim, > My Linux box is the only NFS connections. ... > > would is save to remove the 192.168.1.1/24 entry? Yes, I think so. - Those entries are only for NFS exports. - You think only one machine is an NFS client. - You don't have any machines on the 192.168.1/24 network. -- Cheers, Ralph. -- Next meeting: Online, Jitsi, Tuesday, 2024-02-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Changed IP address lost NAS, but........
On 24/01/2024 15:20, Ralph Corderoy wrote: Hi Tim, What is the IP address of the Linux machine? It is a 192.168.18/24? ‘ip a’ will show the address of each network interface. ‘showmount -e 192.168.18.150’ may be a useful test as well as ‘rpcinfo 192.168.18.150’. ... $ ip a ... 2: enp0s25: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 3c:97:0e:a2:0f:e8 brd ff:ff:ff:ff:ff:ff inet 192.168.18.34/24 brd 192.168.18.255 scope global dynamic noprefixroute enp0s25 valid_lft 43835sec preferred_lft 43835sec inet6 2a0e:cb01:8c:7400:3ed0:59ac:9748:6714/64 scope global dynamic noprefixroute valid_lft 477sec preferred_lft 477sec inet6 fe80::9e5b:2313:8e2c:e6e/64 scope link noprefixroute valid_lft forever preferred_lft forever So the IPv4 address of your NX1 laptop is 192.168.18.34/24. That's in your new 192.168.18/24 network, which is good. $ showmount -e clnt_create: RPC: Program not registered No, my showmount command included an IP address. and this for the ssh terminal admin@diskstation:~$ showmount -e /Volume1/Data 192.168.1.1/24 Ah, good. If the NAS is 192.168.18.150 then you've effectively done the showmount I was after by running it on 150 itself. But I still suggest you do ‘showmount -e 192.168.18.150’ from NX1 to confirm it gives the same result. Is this the /etc/exports we were are looking for? It's a subset of what would be in it. I think the NAS, 192.168.18.150, AKA diskstation, is reporting through showmount that /Volume1/Data may be mounted by 192.168.1.1/24. I'm not quite sure why the last byte of 1 is there given the /24 masks it off. 192.168.1.0/24 looks to be equivalent to me. But your laptop, NX1, is 192.168.18.34/24 which is a different network. The NAS won't let a 192.168.18/24 mount it as it's not 192.168.1/24. So you need to check your other machines which can mount it are using NFS rather than something else which has its own different set of checks. And if it's only the NFS machine having problems then alter the NAS to allow NFS mounts from 192.168.18/24 instead of 192.168.1/24. Sorry for the delay in replying. So went onto the Nas and looked at the NFS entries, found an entry for 192.168.1.1/24, so I added a second entry 192.169.18.1/24. I had to reboot the NAS but once rebooted I was able to login. My Linux box is the only NFS connections. So assuming I have checked my windows boxes can access the Nas of (think there some form of Smaba used< I am not sure), would is save to remove the 192.168.1.1/24 entry? Regards Tim H -- Next meeting: Online, Jitsi, Tuesday, 2024-02-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Changed IP address lost NAS, but........
Hi Tim, > > What is the IP address of the Linux machine? It is a 192.168.18/24? > > ‘ip a’ will show the address of each network interface. > > > > ‘showmount -e 192.168.18.150’ may be a useful test as well as > > ‘rpcinfo 192.168.18.150’. ... > $ ip a ... > 2: enp0s25: mtu 1500 qdisc fq_codel state > UP group default qlen 1000 > link/ether 3c:97:0e:a2:0f:e8 brd ff:ff:ff:ff:ff:ff > inet 192.168.18.34/24 brd 192.168.18.255 scope global dynamic > noprefixroute enp0s25 > valid_lft 43835sec preferred_lft 43835sec > inet6 2a0e:cb01:8c:7400:3ed0:59ac:9748:6714/64 scope global dynamic > noprefixroute > valid_lft 477sec preferred_lft 477sec > inet6 fe80::9e5b:2313:8e2c:e6e/64 scope link noprefixroute > valid_lft forever preferred_lft forever So the IPv4 address of your NX1 laptop is 192.168.18.34/24. That's in your new 192.168.18/24 network, which is good. > $ showmount -e > clnt_create: RPC: Program not registered No, my showmount command included an IP address. > and this for the ssh terminal > > admin@diskstation:~$ showmount -e > /Volume1/Data 192.168.1.1/24 Ah, good. If the NAS is 192.168.18.150 then you've effectively done the showmount I was after by running it on 150 itself. But I still suggest you do ‘showmount -e 192.168.18.150’ from NX1 to confirm it gives the same result. > Is this the /etc/exports we were are looking for? It's a subset of what would be in it. I think the NAS, 192.168.18.150, AKA diskstation, is reporting through showmount that /Volume1/Data may be mounted by 192.168.1.1/24. I'm not quite sure why the last byte of 1 is there given the /24 masks it off. 192.168.1.0/24 looks to be equivalent to me. But your laptop, NX1, is 192.168.18.34/24 which is a different network. The NAS won't let a 192.168.18/24 mount it as it's not 192.168.1/24. So you need to check your other machines which can mount it are using NFS rather than something else which has its own different set of checks. And if it's only the NFS machine having problems then alter the NAS to allow NFS mounts from 192.168.18/24 instead of 192.168.1/24. -- Cheers, Ralph. -- Next meeting: Online, Jitsi, Tuesday, 2024-02-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Changed IP address lost NAS, but........
On 22/01/2024 09:50, Ralph Corderoy wrote: Hi Tim, I have checked through all the relevant network settings on the NAS and they are reporting the correct IP and Gateway Address. The NAS may have the equivalent of /etc/exports which can limit the IP addresses which can mount. $ mount /media/nas mount.nfs: access denied by server while mounting 192.168.18.150:/volume1/Data What is the IP address of the Linux machine? It is a 192.168.18/24? ‘ip a’ will show the address of each network interface. ‘showmount -e 192.168.18.150’ may be a useful test as well as ‘rpcinfo 192.168.18.150’. Thank you both for you suggestions Here the results from a couple of tests mit@NX1:~$ showmount -e clnt_create: RPC: Program not registered mit@NX1:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s25: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 3c:97:0e:a2:0f:e8 brd ff:ff:ff:ff:ff:ff inet 192.168.18.34/24 brd 192.168.18.255 scope global dynamic noprefixroute enp0s25 valid_lft 43835sec preferred_lft 43835sec inet6 2a0e:cb01:8c:7400:3ed0:59ac:9748:6714/64 scope global dynamic noprefixroute valid_lft 477sec preferred_lft 477sec inet6 fe80::9e5b:2313:8e2c:e6e/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wwan0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 42:ac:92:51:9b:6b brd ff:ff:ff:ff:ff:ff 4: wlp3s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 6c:88:14:a0:3d:d8 brd ff:ff:ff:ff:ff:ff Now I can ssh onto the the NAS (using Putty for linux), I can login but thats as far as I get. SSH is supposed to allow the basic commands like ls, but when I try I get nothing from command it just return the promtp. I have logged is an a normal user and an admin but that makes not difference, also tried sudo in ssh but again made not difference. I did get this from my laptop mit@NX1:~$ showmount -e clnt_create: RPC: Program not registered and this for the ssh terminal admin@diskstation:~$ showmount -e /Volume1/Data 192.168.1.1/24 Is this the /etc/exports we were are looking for? Finally it@NX1:~$ rpcinfo 192.168.18.150 program version netid address service owner 10 4 tcp6 ::.0.111 portmapper superuser 10 3 tcp6 ::.0.111 portmapper superuser 10 4 udp6 ::.0.111 portmapper superuser 10 3 udp6 ::.0.111 portmapper superuser 10 4 tcp 0.0.0.0.0.111 portmapper superuser 10 3 tcp 0.0.0.0.0.111 portmapper superuser 10 2 tcp 0.0.0.0.0.111 portmapper superuser 10 4 udp 0.0.0.0.0.111 portmapper superuser 10 3 udp 0.0.0.0.0.111 portmapper superuser 10 2 udp 0.0.0.0.0.111 portmapper superuser 10 4 local /var/run/rpcbind.sock portmapper superuser 10 3 local /var/run/rpcbind.sock portmapper superuser 15 1 udp 0.0.0.0.3.124 mountd superuser 15 1 tcp 0.0.0.0.3.124 mountd superuser 15 1 udp6 ::.3.124 mountd superuser 15 1 tcp6 ::.3.124 mountd superuser 15 2 udp 0.0.0.0.3.124 mountd superuser 15 2 tcp 0.0.0.0.3.124 mountd superuser 15 2 udp6 ::.3.124 mountd superuser 15 2 tcp6 ::.3.124 mountd superuser 15 3 udp 0.0.0.0.3.124 mountd superuser 15 3 tcp 0.0.0.0.3.124 mountd superuser 15 3 udp6 ::.3.124 mountd superuser 15 3 tcp6 ::.3.124 mountd superuser 13 2 tcp 0.0.0.0.8.1 nfs superuser 13 3 tcp 0.0.0.0.8.1 nfs superuser 13 4 tcp 0.0.0.0.8.1 nfs superuser 13 2 udp 0.0.0.0.8.1 nfs superuser 13 3 udp 0.0.0.0.8.1 nfs superuser 13 2 tcp6 ::.8.1 nfs superuser 13 3 tcp6 ::.8.1 nfs superuser 13 4 tcp6 ::.8.1 nfs superuser 13 2 udp6 ::.8.1 nfs superuser 13 3 udp6 ::.8.1 nfs superuser 100021 1 udp 0.0.0.0.173.221 nlockmgr superuser 100021 3 udp 0.0.0.0.173.221
Re: [Dorset] Changed IP address lost NAS, but........
Hi Tim, > I have checked through all the relevant network settings on the NAS > and they are reporting the correct IP and Gateway Address. The NAS may have the equivalent of /etc/exports which can limit the IP addresses which can mount. > $ mount /media/nas > mount.nfs: access denied by server while mounting > 192.168.18.150:/volume1/Data What is the IP address of the Linux machine? It is a 192.168.18/24? ‘ip a’ will show the address of each network interface. ‘showmount -e 192.168.18.150’ may be a useful test as well as ‘rpcinfo 192.168.18.150’. -- Cheers, Ralph. -- Next meeting: Online, Jitsi, Tuesday, 2024-02-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Changed IP address lost NAS, but........
Hi, Have you checked the /etc/exports file on the NAS? It's the list of NFS clients allowed access, mine looks something like this. # /etc/exports: NFS file systems being exported. See exports(5). # /home 192.168.42.162(rw,no_subtree_check,no_root_squash) /home 192.168.42.163(rw,no_subtree_check,no_root_squash) On Sun, Jan 21 at 09:01, Tim wrote: > I have recently changed my Internet Provider and that provider supplied > me with a Linksys Mesh Router with Wifi 6 ... > My line is the fstab file looks like this > > 192.168.18.150:/volume1/Data /media/nas nfs > users,rw,_netdev 0 0 -- Bob Dunlop -- Next meeting: Online, Jitsi, Tuesday, 2024-02-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
[Dorset] Changed IP address lost NAS, but........
I have recently changed my Internet Provider and that provider supplied me with a Linksys Mesh Router with Wifi 6 Just for personal preference and because everybody and his dog stays with the default 192.168.1.0/24 range I changed the range to 192.168.18.0. There are 4 PC's that access the NAS 2 x Win10 1 x Win 11 and 1 X Linux (Mint). All the windows PC and see and access the NAS without issue, I am unable to mount the NAS in Linux, although I can access the Web access page from my Linux box. The old NAS IP address was static 192.168.1.150 The New NAS IP Address is static 192.168.18.150 I have checked through all the relevant network settings on the NAS and they are reporting the correct IP and Gateway Address. The NAS is ping-able from the Linux machine I updated fstab by simply changing the IP address from 192.168.1.150 to 192.168.18.150 and saved it and checked and it is reporting correctly. Both NAS and Laptop have been rebooted. If I try to mount the NAS from CLI I get the following mit@NX1:~$ mount /media/nas mount.nfs: access denied by server while mounting 192.168.18.150:/volume1/Data I have a shortcut on my Desktop (XFCE) which when I click on it to Mount, it gives the same error My line is the fstab file looks like this 192.168.18.150:/volume1/Data /media/nas nfs users,rw,_netdev 0 0 All I done to edit was to add a "8" to the "1" to make "18" and then travelled to the end of the line and saved the file (using Nano) Any suggestions? Tim H -- Next meeting: Online, Jitsi, Tuesday, 2024-02-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
