Received-SPF: pass (google.com: domain of linux-nfs+bounces-970-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Feedback-ID: i31e841b0:Fastmail
Message-ID: <68a64e1a-6f39-2b9e-b41c-ae2200e054c0@themaw.net>
Date: Mon, 8 Jan 2024 10:01:43 +0800
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.15.1
To: Cedric Blancher <cedric.blancher@gmail.com>,
 Linux NFS Mailing List <linux-nfs@vger.kernel.org>
References: <CALXu0UdFR7Xn51eKFUUi6a68wvDKc-RXz7F4LKyQgDptqfYbgw@mail.gmail.com>
 <CALXu0UfSJ0Qc3HOecf4pQ=VnEVqxRw6OGzNwhh9BUVYaHV7_oQ@mail.gmail.com>
Content-Language: en-US
From: Ian Kent <raven@themaw.net>
Subject: Re: nfs-utils&nfsd&autofs not supporting non-2049 TCP port numbers -
 Fwd: showmount -e with custom port number?
In-Reply-To: <CALXu0UfSJ0Qc3HOecf4pQ=VnEVqxRw6OGzNwhh9BUVYaHV7_oQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 8/1/24 06:33, Cedric Blancher wrote:
> Good evening!
>
> Generic issue in all of nfs-utils: None of the utils properly support
> NFSv4 with non.standard (TCP/2049) port numbers.
>
> mount supports it for mounting, but does not show it for listing mounts
> /proc/mounts does not show the port number either

I'll leave this to the nfs folks but, looking at the nfs kernel code,

neither of the above appear to be accurate. But then you haven't provided

information about what kernel and utility versions your report is based on

so I can't check.


> showmount -e does not support a port number

Now this does look to be a problem, even with the current code, and the

mountd port can't be specified at all.


> autofs does not support non-2049 port numbers

What is it you expect to be able to do with autofs that you can't do?


It's interesting that you sound like you assume mountd "must" not be

used for NFSv4 and it's not the first time I've heard that.


I thought NFSv4 "must" be able to be used without mountd but there was

nothing that says mountd "must" not be used to provide port information

to clients if they ask, such as on a local (probably isolated) network.


So, based on that assumption, the fact that it (the kernel => mount(8),

proc mount listings) doesn't print the value of the port option if the

default NFS server port is being used seems sensible enough.


I'm not aware of any protocol in NFS itself for communicating the list

of exports. And if your not on an isolated network would being able to

list the exports be a wise idea?


So I'm not sure what your expecting to be done ... other than some

improvements to showmount(8).


> nfsd referrals do not support setting non-2049 port numbers
> ...

Another interesting comment, I don't actually know about NFS referrals

these days. I'd be interested in hearing about them.


Ian

>
> Could you please make a concentrated effort and allow non-2049 port
> numbers for NFSv4 mounts, in all of the lifecycle of a NFSv4 mount?
>  From nfsd, nfsd referrals, client mount/umount, autofs
> mount/umount+LDAP spec
>
> Ced
>
> ---------- Forwarded message ---------
> From: Cedric Blancher <cedric.blancher@gmail.com>
> Date: Sun, 7 Jan 2024 at 22:32
> Subject: showmount -e with custom port number?
> To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
>
>
> Good evening!
>
> How can I get showmount -e to use a non-2049 TCP port number to show
> mounts on a NFSv4 server?
>
> /sbin/showmount -e localhost@30000
> clnt_create: RPC: Unknown host
>
> Ced
> --
> Cedric Blancher <cedric.blancher@gmail.com>
> [https://plus.google.com/u/0/+CedricBlancher/]
> Institute Pasteur
>
>