All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: nfs ports
Date: Fri, 28 Jan 2005 13:49:27 -0500	[thread overview]
Message-ID: <20050128184927.GA15097@bender.817west.com> (raw)
In-Reply-To: <200501281250.55466.JALaramie@Loudoun-Fairfax.com>

On Fri, Jan 28, 2005 at 12:50:55PM -0500, Jeffrey Laramie wrote:
> Hi All,
> 
> I've been fighting the good fight trying to maintain nfs connections though my 
> firewall but I'm not winning. Every time I think I have opened the ports I 
> need nfs (portmapper?) uses a different port. My questions:
> 
> 1.  Is there a netfilter patch for tracking nfs ports similar to the one for 
> ftp?
> 
> 2.  If not, can someone point me to a list of ports used by nfs so that I can 
> open up what I need once and for all?

RPC Portmapper		TCP 111
NFSD			UDP 2049

IIRC statd, mountd, lockd, and rquotad are assigned their ports by the
the portmapper when a request comes in; however, each daemon supports a
"-p" option to nail it down to a single port--see the man page of each
for specific syntax.  lockd is actually a kernel module that's loaded
on demand, and you would need to pass the static TCP/UDP port to the
modprobe command as an option (i.e. in modprobe.conf).

check out:

http://www.faqs.org/docs/Linux-HOWTO/NFS-HOWTO.html#FIREWALLS

for more specific details.

-j

--
"This anonymous clan of slack-jawed troglodytes has cost me the
 election, and yet if I were to have them killed, I would be the one
 to go to jail. That's democracy for you.
 You are noble and poetic in defeat, sir."
        --The Simpsons



  reply	other threads:[~2005-01-28 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 17:50 nfs ports Jeffrey Laramie
2005-01-28 18:49 ` Jason Opperisano [this message]
2005-01-28 19:22   ` Jeffrey Laramie
2005-01-28 18:55 ` Jose Maria Lopez
2005-01-28 19:21   ` Jeffrey Laramie

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=20050128184927.GA15097@bender.817west.com \
    --to=opie@817west.com \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.