Received-SPF: pass (google.com: domain of linux-nfs+bounces-969-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Precedence: bulk
MIME-Version: 1.0
References: <CALXu0UdFR7Xn51eKFUUi6a68wvDKc-RXz7F4LKyQgDptqfYbgw@mail.gmail.com>
In-Reply-To: <CALXu0UdFR7Xn51eKFUUi6a68wvDKc-RXz7F4LKyQgDptqfYbgw@mail.gmail.com>
From: Cedric Blancher <cedric.blancher@gmail.com>
Date: Sun, 7 Jan 2024 23:33:31 +0100
Message-ID: <CALXu0UfSJ0Qc3HOecf4pQ=VnEVqxRw6OGzNwhh9BUVYaHV7_oQ@mail.gmail.com>
Subject: nfs-utils&nfsd&autofs not supporting non-2049 TCP port numbers - Fwd:
 showmount -e with custom port number?
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"

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
showmount -e does not support a port number
autofs does not support non-2049 port numbers
nfsd referrals do not support setting non-2049 port numbers
...

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


-- 
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur