From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
netdev@vger.kernel.org,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: sunrpc port allocation and IANA reserved list
Date: Wed, 11 Nov 2009 06:58:10 +0900 [thread overview]
Message-ID: <1257890290.3044.39.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1257887844.3044.24.camel@heimdal.trondhjem.org>
On Wed, 2009-11-11 at 06:17 +0900, Trond Myklebust wrote:
> The people who are trying to run absolutely all IANA registered services
> on a single Linux machine that is also trying to run as an NFS client
> may have a problem, but then again, how many setups do you know who are
> trying to do that?
BTW: Even these setups can be fixed. One way to extend the available
port ranges is to allocate more than one IP address; either through the
use of multiple NICs, or through address aliasing. You can set up the
services to listen on one interface, while setting up your routing
tables to ensure that any outgoing connections to your NFS servers go
through through a different interface.
You could also use virtualised machines to host the services, etc...
Trond
next prev parent reply other threads:[~2009-11-10 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 17:43 Chris Friesen
2009-11-10 17:53 ` Ben Hutchings
2009-11-10 18:37 ` Chris Friesen
2009-11-10 18:48 ` Chris Friesen
2009-11-10 20:26 ` Trond Myklebust
2009-11-10 21:06 ` Chris Friesen
2009-11-10 21:17 ` Trond Myklebust
2009-11-10 21:58 ` Trond Myklebust [this message]
2009-11-10 21:32 ` Ben Hutchings
2009-11-10 21:34 ` Chuck Lever
2009-11-10 21:42 ` Ben Hutchings
2009-11-10 21:54 ` Chris Friesen
2009-11-10 22:14 ` Trond Myklebust
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=1257890290.3044.39.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=bhutchings@solarflare.com \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®