From: Athan <netfilter@miggy.org>
To: "Randall J. Parr" <RParr@TemporalArts.COM>
Cc: Guarddog-user@lists.sourceforge.net,
netfilter@lists.netfilter.org, psyche-list@redhat.com
Subject: Re: problem configuring for NFS between RH8 and RH6
Date: Wed, 8 Jan 2003 22:06:04 +0000 [thread overview]
Message-ID: <20030108220604.GE21359@miggy.org> (raw)
In-Reply-To: <3E1C808F.9030202@TemporalArts.com>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On Wed, Jan 08, 2003 at 11:48:31AM -0800, Randall J. Parr wrote:
> But then the log messages indicated RH8 -> RH6 port 887 was being
> dropped. Note that the dynamic port (in this example 887) changes every
> time I restarted RH6 NFS.
Assuming this is the user-space NFS daemon, not the in-kernel one you
should be able to make use of the following option for the mountd:
-P portnum or --port portnum
Makes mountd listen on port portnum instead of some
random port. By default, mountd will listen on the
mount/udp port specified in /etc/services, or, if
that is undefined, on some arbitrary port number
below 1024.
Reading the above, if you put a line in /etc/services like:
mount 887/udp
Then it will *ALWAYS* use that port and you can simply open that up in
your firewall settings.
HTH,
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2003-01-08 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 19:48 problem configuring for NFS between RH8 and RH6 Randall J. Parr
2003-01-08 22:06 ` Athan [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=20030108220604.GE21359@miggy.org \
--to=netfilter@miggy.org \
--cc=Guarddog-user@lists.sourceforge.net \
--cc=RParr@TemporalArts.COM \
--cc=netfilter@lists.netfilter.org \
--cc=psyche-list@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