From: Robert Rati <Robert.Rati@motorola.com>
To: nfs@lists.sourceforge.net
Subject: NFS through firewall
Date: Mon, 03 Mar 2003 18:10:51 -0600 [thread overview]
Message-ID: <3E63EF0B.2070903@motorola.com> (raw)
I am trying to provide a directory to the outside world through a
firewall via NFS. I can mount the directory from another system, but
when I try to list the contents of the directory the firewall blocks the
communication. I see that the host system is attempting to send data on
port 65535 using the UDP protocol. I have the following firewall rule
that SHOULD match it, but isn't:
/sbin/ipchains -A output -j ACCEPT -i eth0 -p udp --source-port 61000:65535
I have set the local port range to be 61000-65535. My question is, why
is NFS choosing port 65535 to transfer data? Is it using the local port
range? I tried changing the port range and restarting the NFS daemons,
but it still tried to use port 65535.
I know this isn't necessarily a firewall expert group, but have there
been any issues with ipchains/2.2 kernels blocking NFS traffic on port
65535?
Rob
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-03-04 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 0:10 Robert Rati [this message]
2003-03-04 0:33 ` NFS through firewall Philippe Troin
2003-03-04 2:40 ` Robert Myers
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=3E63EF0B.2070903@motorola.com \
--to=robert.rati@motorola.com \
--cc=nfs@lists.sourceforge.net \
/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