What happens when you remove the IPv6 adresses from the NFS config? As you are using IPv4, those should not be needed.
I haven't had time to enable IPv6 yet, so can't check locally what works and what doesn't. On 23 December 2019 17:50:58 CET, Peter Humphrey <pe...@prh.myzen.co.uk> wrote: >Hello list, > >Since I set up IPv6 on my LAN, I've been unable to NFS-export a >directory on >machine A (an Atom serving portage via git, among other things) and >mount it >on machine B (this workstation). It was working fine until then, but >now mount >commands fail. In both kernels I have NFSv4 selected, but not 4.x; no >fancy >extras like ACLs. > >I went back to the Gentoo nfs-utils wiki page and made sure I had >everything >right, then searched for other people's problems. Nothing has helped so >far. > >On the server: >$ cat /etc/conf.d/nfs >NFS_NEEDED_SERVICES="rpc.idmapd" >OPTS_RPC_NFSD="1 -N 2 -N 3 -V 4 -N 4.1" >OPTS_RPC_MOUNTD="-p 32767" >OPTS_RPC_STATD="-p 32765 -o 32766" >OPTS_RPC_IDMAPD="" >OPTS_RPC_GSSD="" >OPTS_RPC_SVCGSSD="" >OPTS_RPC_RQUOTAD="" >EXPORTFS_TIMEOUT=30 >$ cat /etc/exports >mnt/nfs 192.168.1.5/24(rw,no_subtree_check,crossmnt,fsid=0) \ > fe80::5/64(rw,sync,no_subtree_check,crossmnt,fsid=0) >/mnt/nfs/portage >192.168.1.5/24(rw,no_subtree_check,anonuid=250,anongid=250,fsid=1) \ > fe80::5/64(rw,no_subtree_check,anonuid=250,anongid=250,fsid=1) >/mnt/nfs/port.resc >192.168.1.5/24(rw,no_subtree_check,anonuid=250,anongid=250,fsid=2) \ > fe80::5/64(rw,no_subtree_check,anonuid=250,anongid=250,fsid=2) >$ grep nfs /etc/fstab >/usr/portage /mnt/nfs/portage none bind > 0 0 > >On the client: >$ grep nfs /etc/fstab >192.168.1.2:/mnt/nfs/portage /mnt/atom/usr/portage nfs4 >noauto,rw,_netdev 0 0 > >Now I try to mount /usr/portage from the host on /mnt/atom/usr/portage >(which >does exist) and get this: ># mount /mnt/atom/usr/portage >mount.nfs4: mounting 192.168.1.2:/mnt/nfs/portage failed, reason given >by server: No such file or directory ># mount 192.168.1.2:/mnt/nfs/portage /mnt/atom/usr/portage >mount.nfs: mounting 192.168.1.2:/mnt/nfs/portage failed, reason given >by server: No such file or directory ># mount [fe80::2]:/mnt/nfs/portage /mnt/atom/usr/portage >mount.nfs: mount system call failed > >It doesn't seem to be a firewall problem, because I get the same result >if I >start both machines without their firewalls - I don't do that very >often! Ping >works fine in both directions, whether IPv4 or v6. Do I have to tweak >mapd >somehow? > >I'm feeling a bit clueless... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
