public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve <gentoo_sjh@shic.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A networking question...
Date: Fri, 08 May 2009 13:38:42 +0100	[thread overview]
Message-ID: <4A0427D2.2090206@shic.co.uk> (raw)
In-Reply-To: <200905072335.00108.michaelkintzios@gmail.com>

Mick wrote:
> An adaptor can have more than one public IP address (multi-homing) and you can 
> use something like: ifconfig eth0:0 192.168.0.2 netmask 255.255.255.0 up to 
> set them up (increment eth0:1, eth0:2, etc accordingly).  However, if your 
> SSL vhost is listening on a random port you don't need binding of many 
> addresses to one NIC.  You can use the same ip address.
>   
This is the essential bit I was missing, I think.  I knew it was 
possible to set up "multi-homing" (as I'd seen it on other systems) but 
I'd forgotten what it was called... and that made searching for 
documentation, erm, hard... though even knowing the term hasn't given me 
a slam-dunk search result through google.  I presume I need to fiddle 
with /etc/conf.d/net - somehow - in order to convince 
/etc/init.d/net.eth0 to do what I need.

> Other than vhost I guest you can run a second instance by reading section 5 
> here (but I'm not sure you need to do that anyway):
>
> http://www.gentoo.org/proj/en/php/php4-php5-configuration.xml
That's all helpful material - suggesting, at least, that there's no neat 
gentoo-specific one-liner to achieve the two instances I need... plus it 
highlights specific problems I might have with interactions between PHP 
in my two instances. Hmmm... I hadn't anticipated that... frustrating.

I guess the other route I could consider would be virtualisation - 
establishing a completely separate installation... at least that way I 
could be sure that no aspect of my 'alive' system could impact the 
configuation of my development system... allowing me maximum confidence 
that I know what's needed when I come to deploy.

Somewhat frustratingly, this seems to be morphing into a considerably 
more involved problem than I'd envisaged. ;)



  reply	other threads:[~2009-05-08 12:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 20:32 [gentoo-user] A networking question Steve
2009-05-05 21:23 ` Sascha Hlusiak
2009-05-05 21:28   ` Steve
2009-05-05 21:51     ` Sascha Hlusiak
2009-05-05 22:07       ` Mick
2009-05-06  0:24     ` Mike Kazantsev
2009-05-06  7:54       ` Neil Bothwick
2009-05-06 10:09         ` Anthony Metcalf
2009-05-06 10:42           ` Neil Bothwick
2009-05-06 12:08             ` Anthony Metcalf
2009-05-07 18:38               ` Steve
2009-05-07 22:34                 ` Mick
2009-05-08 12:38                   ` Steve [this message]
2009-05-08 14:43                     ` Mick

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=4A0427D2.2090206@shic.co.uk \
    --to=gentoo_sjh@shic.co.uk \
    --cc=gentoo-user@lists.gentoo.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