From: Tom Talpey <tom@talpey.com>
To: Chuck Lever <chuck.lever@oracle.com>, Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/1] Remote calls don't need to use privilege ports
Date: Tue, 6 Feb 2018 13:22:12 -0500 [thread overview]
Message-ID: <02863316-1c99-182c-b19e-cc1aff46c382@talpey.com> (raw)
In-Reply-To: <6EF07D03-7F1C-43D1-963B-ED28AD614BF4@oracle.com>
On 2/6/2018 12:34 PM, Chuck Lever wrote:
> mountd can and should use a dynamic port assignment, IMO.
> It doesn't have to use 20048.
Speaking of 20048, does anyone know why Nico made this assignment?
Apart from making it well-known for firewalls, what system(s)
actually required it? I don't recall it ever being discussed.
Using it is certainly not required, since portmap resolves it.
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
++ mountd 20048 tcp NFS mount protocol
[Nicolas_Williams] [Nicolas_Williams]
2010-08-09
++ mountd 20048 udp NFS mount protocol
[Nicolas_Williams] [Nicolas_Williams]
2010-08-09
Tom.
next prev parent reply other threads:[~2018-02-06 18:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 16:36 [PATCH 0/1] Remote calls don't need to use privilege ports Steve Dickson
2018-02-05 16:36 ` [PATCH 1/1] rmtcalls: Don't use privileged ports for remote calls Steve Dickson
2018-02-05 17:02 ` [PATCH 0/1] Remote calls don't need to use privilege ports Chuck Lever
2018-02-05 17:09 ` Tom Talpey
2018-02-05 17:11 ` Chuck Lever
2018-02-05 19:46 ` Steve Dickson
2018-02-07 4:35 ` NeilBrown
2018-02-07 16:09 ` Chuck Lever
2018-02-07 21:16 ` NeilBrown
2018-02-07 21:23 ` Chuck Lever
2018-02-07 23:16 ` NeilBrown
2018-02-08 0:13 ` Chuck Lever
2018-02-08 0:45 ` NeilBrown
2018-02-08 0:46 ` Chuck Lever
2018-02-05 19:21 ` Steve Dickson
2018-02-05 19:47 ` Chuck Lever
2018-02-06 16:37 ` Steve Dickson
2018-02-06 17:34 ` Chuck Lever
2018-02-06 18:22 ` Tom Talpey [this message]
2018-02-06 18:36 ` Chuck Lever
2018-02-07 0:15 ` Tom Talpey
2018-02-06 19:00 ` Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02863316-1c99-182c-b19e-cc1aff46c382@talpey.com \
--to=tom@talpey.com \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).