From: Robert Myers <rmyers1400@attbi.com>
To: Robert Rati <Robert.Rati@motorola.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS through firewall
Date: Mon, 03 Mar 2003 21:40:14 -0500 [thread overview]
Message-ID: <3E64120E.4050403@attbi.com> (raw)
In-Reply-To: <3E63EF0B.2070903@motorola.com>
Robert Rati wrote:
> 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
Is this an output chain on the client side? Why should that cause the
client to accept a communication on 65535? Happens all the time: client
requests data on port x, declines the response on port x. Go figure.
Without seeing your entire ipchains config (and I wouldn't recommend
posting it), I can't suggest a one-line fix, but somewhere you need
/sbin/ipchains -A input -j ACCEPT -i eth0 -p udp --source-port 61000:65535,
but I wouldn't recommend it. Instead, specify that NFS use a port in
the reserved range (1-1024) and don't open a hole in your firewall where
hackers often lurk.
Check out
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/NFS-HOWTO.html
for how to specify what port NFS is using.
RM
-------------------------------------------------------
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
prev parent reply other threads:[~2003-03-04 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 0:10 NFS through firewall Robert Rati
2003-03-04 0:33 ` Philippe Troin
2003-03-04 2:40 ` Robert Myers [this message]
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=3E64120E.4050403@attbi.com \
--to=rmyers1400@attbi.com \
--cc=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