Date: Sat, 23 Aug 2025 08:01:18 -0700 From: Rick Macklem <rick.macklem@gmail.com> To: Lionel Cons <lionelcons1972@gmail.com> Cc: Freebsd hackers list <freebsd-hackers@freebsd.org> Subject: Re: FreeBSD NFS4 on custom TCP port (not 2049)? Message-ID: <CAM5tNy6_SoXdrK_0BrhJJ72TZ56rhDyWq2%2BG_5gGSGpQAVrgPw@mail.gmail.com> In-Reply-To: <CAM5tNy73p3tJSsV92m2xWkNfyVTRMkvTW%2BfSiK1vGqjkPK6nhQ@mail.gmail.com> References: <CAPJSo4XaQZ3bV0CRr0dXLGAVWp=NLBy9KJDtHr9bPyUAxpKOrQ@mail.gmail.com> <CAM5tNy73p3tJSsV92m2xWkNfyVTRMkvTW%2BfSiK1vGqjkPK6nhQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Sat, Aug 23, 2025 at 7:38 AM Rick Macklem <rick.macklem@gmail.com> wrote: > > On Fri, Aug 22, 2025 at 11:09 PM Lionel Cons <lionelcons1972@gmail.com> wrote: > > > > Do the FreeBSD NFS4 server and client support operating at a custom > > TCP port (not TCP 2049)? > > How can I set the TCP port number for the server, and how do I mount it? > It does not do that now. You would have to patch the sources. Actually, I was incorrect. If you change the lines that start with "nfsd" in /etc/services, it will use whatever port# you specify there. I do wonder why you would want to change it? There can only be one instance of "nfsd" in each vnet jail (which means only one running on the server if you are not using vnet jails), so why would you want it at a different port#? rick > > The RFC has always defined 2049 as the port# and FreeBSD does not > have support for RDMA, which does use a different port#. > > rick > > > > > Lionel > >help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy6_SoXdrK_0BrhJJ72TZ56rhDyWq2%2BG_5gGSGpQAVrgPw>