From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Random UDP port assignment for rpc.statd
Date: Sun, 20 Feb 2005 15:10:37 +0100 [thread overview]
Message-ID: <20050220141037.GA7686@s> (raw)
In-Reply-To: <1108908221.27120.26.camel@lade.trondhjem.org>
[Trond Myklebust]
> su den 20.02.2005 Klokka 12:13 (+0100) skreiv Haakon Riiser:
>> Why isn't it possible to specify all of statd's listening
>> ports using the -p flag? It works for the TCP port and one
>> of the UDP ports, but there is always one more listening UDP
>> port that is randomly assigned. [...]
> rpc.statd needs some ports for communication with the portmapper
> and the lockd manager on the loopback net, and this is probably
> what you are seeing. There should be nothing that needs to be
> allowed firewall access, though.
Actually, I wanted to /block/ this port in the firewall, not open
for external access. My firewall allows everything by default, and
has rules to block ports that shouldn't be visible to the world.
Should I be concerned about this port being unblocked?
--
Haakon
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-20 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 11:13 Random UDP port assignment for rpc.statd Haakon Riiser
2005-02-20 14:03 ` Trond Myklebust
2005-02-20 14:10 ` Haakon Riiser [this message]
2005-02-20 15:30 ` Trond Myklebust
2005-02-20 16:43 ` Trond Myklebust
2005-02-20 17:04 ` Haakon Riiser
2005-02-28 3:21 ` Neil Brown
2005-02-20 17:21 ` Haakon Riiser
2005-02-20 17:38 ` Trond Myklebust
2005-02-20 18:01 ` Haakon Riiser
2005-02-28 3:32 ` Sven Köhler
2005-02-28 23:53 ` Dan Stromberg
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=20050220141037.GA7686@s \
--to=haakon.riiser@fys.uio.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox