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
2009/5/8 Steve gentoo_...@shic.co.uk:
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
Anthony Metcalf wrote:
*That* depends on the exact specifics of what he is/isn't allowed to
be showing.They may not even want the service to show as
existing at that address for whatever reason.
Thanks for all your discussion... I'll try to clarify - the PPP over
SSH approach does seem
On Thursday 07 May 2009, Steve wrote:
Anthony Metcalf wrote:
*That* depends on the exact specifics of what he is/isn't allowed to
be showing.They may not even want the service to show as
existing at that address for whatever reason.
Thanks for all your discussion... I'll try to
On Wed, 6 May 2009 06:24:08 +0600, Mike Kazantsev wrote:
But you don't have to!
Just setup first apache to forward requests to the second one in any
way you like using mod_rewrite:
If the second server is only serving HTTPS, you don't even need that.
Just have the router forward port 80 to
Neil Bothwick wrote:
If the second server is only serving HTTPS, you don't even need that.
Just have the router forward port 80 to the first server and port 443 to
the second.
That leaves the HTTPS server open to the public though, which is
specifically not allowed to the OP.
I would say
On Wed, 06 May 2009 11:09:50 +0100, Anthony Metcalf wrote:
If the second server is only serving HTTPS, you don't even need that.
Just have the router forward port 80 to the first server and port 443
to the second.
That leaves the HTTPS server open to the public though, which is
Neil Bothwick wrote:
On Wed, 06 May 2009 11:09:50 +0100, Anthony Metcalf wrote:
If the second server is only serving HTTPS, you don't even need that.
Just have the router forward port 80 to the first server and port 443
to the second.
That leaves the HTTPS server open to
I've a gentoo box sat behind a firewall - it runs a apache and sshd with
holes punched through NAT to allow remote access. It runs DHCP and DNS
services for my LAN.
I would like to run a second instance of apache on a fresh IP address -
to simulate a hosted environment supporting https. I
Am Dienstag 05 Mai 2009 22:32:38 schrieb Steve:
I've a gentoo box sat behind a firewall - it runs a apache and sshd with
holes punched through NAT to allow remote access. It runs DHCP and DNS
services for my LAN.
I would like to run a second instance of apache on a fresh IP address -
to
Sascha Hlusiak wrote:
The easiest thing would probably be to just use ssh port forwarding because
you already have all the pieces running anyway. Wouldn't a simple
ssh -L 12345:secondapache:https u...@remotessh
and the browsing to https://localhost:12345 do the trick? Or you could use a
Am Dienstag 05 Mai 2009 23:28:22 schrieb Steve:
Sascha Hlusiak wrote:
The easiest thing would probably be to just use ssh port forwarding
because you already have all the pieces running anyway. Wouldn't a simple
ssh -L 12345:secondapache:https u...@remotessh
and the browsing to
On Tuesday 05 May 2009, Sascha Hlusiak wrote:
Am Dienstag 05 Mai 2009 23:28:22 schrieb Steve:
Sascha Hlusiak wrote:
The easiest thing would probably be to just use ssh port forwarding
because you already have all the pieces running anyway. Wouldn't a
simple
ssh -L
On Tue, 05 May 2009 22:28:22 +0100
Steve gentoo_...@shic.co.uk wrote:
Sascha Hlusiak wrote:
The easiest thing would probably be to just use ssh port forwarding because
you already have all the pieces running anyway. Wouldn't a simple
ssh -L 12345:secondapache:https u...@remotessh
...
14 matches
Mail list logo
