linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Malahal Naineni <malahal@us.ibm.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Soumya Koduri <skoduri@redhat.com>,
	linux-nfs@vger.kernel.org,
	"nfs-ganesha-devel@lists.sourceforge.net"
	<nfs-ganesha-devel@lists.sourceforge.net>,
	Bruce Fields <bfields@redhat.com>,
	Niels de Vos <ndevos@redhat.com>
Subject: Re: Default ports to be used by NFS side-band protocol services (lockd, statd, rquotad)
Date: Mon, 14 Sep 2015 13:30:24 -0500	[thread overview]
Message-ID: <20150914183024.GA1277@us.ibm.com> (raw)
In-Reply-To: <55F71073.6090102@RedHat.com>

Steve Dickson [SteveD@redhat.com] wrote:
> Hello,
> 
> On 09/14/2015 09:11 AM, Soumya Koduri wrote:
> > Hi,
> > 
> > In the latest Linux distributions (Fedora), ports 2049 (nfs) and 20048 (mountd) are configured to be opened by default by firewalld service.
> > 
> > Files: '/usr/lib/firewalld/services/nfs.xml' & '/usr/lib/firewalld/services/mountd.xml'.
> Hmm... I didn't know about this... We should probably 
> set the -p 20048 by default via /etc/sysconfig/nfs file or maybe the systemd script?

I believe, mountd already uses /etc/services file by default. So
specifying it in /etc/services would be good. I think RHEL7 has one for
mountd. This is specific to NFSv3 anyway...


Regards, Malahal.


  reply	other threads:[~2015-09-14 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 13:11 Default ports to be used by NFS side-band protocol services (lockd, statd, rquotad) Soumya Koduri
2015-09-14 18:22 ` Steve Dickson
2015-09-14 18:30   ` Malahal Naineni [this message]
2015-09-15 19:15     ` Soumya Koduri
2015-09-16 13:25       ` [Nfs-ganesha-devel] " Steve Dickson
2015-09-16 13:42         ` Trond Myklebust

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=20150914183024.GA1277@us.ibm.com \
    --to=malahal@us.ibm.com \
    --cc=SteveD@redhat.com \
    --cc=bfields@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=ndevos@redhat.com \
    --cc=nfs-ganesha-devel@lists.sourceforge.net \
    --cc=skoduri@redhat.com \
    /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).