On Wednesday 30 October 2024 23:24:19 GMT Peter Humphrey wrote: > On Thursday 17 October 2024 16:00:36 GMT I wrote: > > --->8 > > Well, it looks as though I have it working, over an Ethernet link anyway. > There's now no /mnt/nfs with fsid=0, with the portage tree and the packages > directory mounted below it. This is /etc/exports on the i5: > > /var/db/repos/gentoo > wstn.prhnet(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250 > ,anongid=250) > /var/cache/packages > wstn.prhnet(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250 > ,anongid=250) > > Those are just two long lines. Breaking them seemed to cause problems. You > see that there's no intermediate mount point.
Yes, the /etc/exports syntax is sensitive to breaks or spaces. There should be a single space between the exported directory and the client's hostname or IP address and no more. > The last two weeks' work has left me unsure of the integrity of the i5, so > I'm going to install a fresh new system and save it before tackling the > wireless link. Then I may be able to coil up that great long Ethernet cable > and stow it. Hmm ... if your NFS configuration works over wired ethernet, but not over wireless, this could point to a lower network level problem. I tend to use static IP addresses on both endpoints to simplify checks and configuration, but if you use hostnames check reverse name resolution is correct and adjust your /etc/hosts on both ends, check the DNS configuration on your LAN and check the client/server IP allocations are as they should be. Temporarily disable firewalls on both ends and check connectivity and access to NFS ports 111,2049 on the server. Check firewall logs/rules on the wireless router and configure accordingly if they are blocking. Finally, make sure hostnames/IP addresses are correctly reflected on NFS configuration at both ends.
signature.asc
Description: This is a digitally signed message part.
