DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C65F820854
Date:   Sun, 11 Nov 2018 11:08:22 +0100
From:   Niels de Vos <ndevos@redhat.com>
To:     Naruto Nguyen <narutonguyen2018@gmail.com>
Cc:     Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: mount client port allocated in privilege port range
Message-ID: <20181111100822.GB4421@ndevos-x270>
References: <CANpxKHEmtZkfcFVhxyrF0PZ2TwTNHCGgYN4qNZu2dn=GasbOVg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANpxKHEmtZkfcFVhxyrF0PZ2TwTNHCGgYN4qNZu2dn=GasbOVg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Sat, Nov 10, 2018 at 10:48:41AM +0700, Naruto Nguyen wrote:
> Hi everyone,
> 
> When running mount command with tcp under root account, I see that the
> tcp client port is allocated in privilege range like 830... I do not
> think it's a good behavior as port in privilege range is limited and a
> lot of well known service is using it. Could you please let me know
> any reason for that? It's better for mount nfs client port to be
> allocated in dynamic port range instead even the system is running
> under root permission? and any other way to make it happens besides
> running under a normal user?

Have a look at 'man 5 nfs' and search for the "noresvport" option. You
will also want to read the "Using non-privileged source ports"
paragraph.

HTH,
Niels