From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Ingo Lantschner <ingo.lists@vum.at>, nfs@lists.sourceforge.net
Subject: Re: udp port sunrpc unreachable
Date: Thu, 2 Feb 2006 10:29:09 -0500 [thread overview]
Message-ID: <20060202152909.GC12118@fieldses.org> (raw)
In-Reply-To: <1138893904.8894.11.camel@lade.trondhjem.org>
On Thu, Feb 02, 2006 at 10:25:04AM -0500, Trond Myklebust wrote:
> On Thu, 2006-02-02 at 10:19 -0500, J. Bruce Fields wrote:
> > On Thu, Feb 02, 2006 at 09:31:37AM -0500, Trond Myklebust wrote:
> > > Portmap appears only to be listening on the loopback adddress. Are you
> > > perhaps starting it before the external network comes up?
> >
> > I think that's actually the debian default setting these days; with the
> > debconf verbosity at the default, it should have asked you about this
> > when portmap was installed. Just edit /etc/default/portmap to comment
> > out the obvious line.
>
> If true, then that would appear to be a rather ridiculous default. Have
> they put out a rationale for this?
Nope, I'm wrong, the default is the opposite. So probably someone chose the
more secure-sounding option at install time and then forgot about it....
--b.
Template: portmap/loopback
Type: boolean
Default: false
_Description: Should portmap be bound to the loopback address?
Portmap by default listens to all IP addresses. However, if you are
not using RPC services that connect to remote servers (like NFS or NIS)
you can safely bind it to the loopback IP address 127.0.0.1.
.
This will allow RPC local services (like FAM) to work properly while
preventing remote systems from accessing your RPC services.
.
You can change this configuration also by editing the OPTIONS
line in the /etc/default/portmap file. If you just don't specify
the -i option it will bind to all interfaces.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-02-02 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 9:21 udp port sunrpc unreachable Ingo Lantschner
2006-02-02 14:31 ` Trond Myklebust
2006-02-02 15:19 ` J. Bruce Fields
2006-02-02 15:25 ` Trond Myklebust
2006-02-02 15:29 ` J. Bruce Fields [this message]
2006-02-02 15:36 ` Trond Myklebust
2006-02-02 18:25 ` SOLVED: " Ingo Lantschner
2006-02-03 15:53 ` Ingo Lantschner
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=20060202152909.GC12118@fieldses.org \
--to=bfields@fieldses.org \
--cc=ingo.lists@vum.at \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.