From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 41D80158042 for ; Thu, 31 Oct 2024 11:07:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9F55AE0856; Thu, 31 Oct 2024 11:07:15 +0000 (UTC) Received: from smarthost01c.ixn.mail.zen.net.uk (smarthost01c.ixn.mail.zen.net.uk [212.23.1.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2DB45E07F0 for ; Thu, 31 Oct 2024 11:07:14 +0000 (UTC) Received: from [82.69.80.10] (helo=cube.localnet) by smarthost01c.ixn.mail.zen.net.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1t6T1E-007no1-Su for gentoo-user@lists.gentoo.org; Thu, 31 Oct 2024 11:07:13 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] nfs mounting Date: Thu, 31 Oct 2024 11:07:13 +0000 Message-ID: <2202241.irdbgypaU6@cube> In-Reply-To: <1952017.taCxCBeP46@rogueboard> References: <10555432.nUPlyArG6x@cube> <4943483.GXAFRqVoOG@cube> <1952017.taCxCBeP46@rogueboard> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-Originating-smarthost01c-IP: [82.69.80.10] Feedback-ID: 82.69.80.10 X-Archives-Salt: a49707f5-7356-4006-9d45-23ce4cac4ed1 X-Archives-Hash: 115ed17e40a3861db7bc87e4419b82a7 On Thursday 31 October 2024 09:52:23 GMT Michael wrote: > 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=25 > > 0 ,anongid=250) > > /var/cache/packages > > wstn.prhnet(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=25 > > 0 ,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. I can only say that a backslash used to work, but now it doesn't. > > 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 remember you said something about problems with some DSL routers. Let's wait and see though. I won't be ready to try it today. > 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. I've always used static addresses. The exception is the wireless network, on which things come and go. I'm confident in dnsmasq on the wired LAN - it's been running for years. > Temporarily disable firewalls on both ends and check connectivity and access > to NFS ports 111,2049 on the server. The firewalls are fine. They're the first thing I check in a case like this. > Check firewall logs/rules on the wireless router and configure accordingly > if they are blocking. The shorewall NFS macro allows TCP ports 111, 2049 and 20048; that last one is for mountd. The router is a Fritz!Box, and it's a bit of a beast to understand. (Is there a characteristic German approach to user interface design? I begin to wonder, what with this and my boiler...) > Finally, make sure hostnames/IP addresses are correctly reflected on NFS > configuration at both ends. Of course. -- Regards, Peter.