services in the host to ONLY bind the host's IP address, instead of all
Not true.
The whole point of vservers networking is that you can give some ip to thw
whole server, and then when services inside bind to '0.0.0.0' they get anlo
what was allocated for given vserver.
If what you say was
Dariush Pietrzak wrote:
services in the host to ONLY bind the host's IP address, instead of all
Not true.
The whole point of vservers networking is that you can give some ip to thw
whole server, and then when services inside bind to '0.0.0.0' they get anlo
what was allocated for given vserver.
I need to run a few different websites on my box using vservers. What
method does everyone use to route the traffic from eth1 (externel
interface, real ip) to the vservers bound to eth0 (internal ip,
192.168.x.x network)?
Darryl Ross wrote:
Dariush Pietrzak wrote:
services in the host to
Each of my vservers will be running apache2, mysql, exim, pop3d, sshd,
and proftpd. I will need to redirect requests to these services from
external (internat) clients to each vserver. Has anyone written a howto
explaining this type of setup, or, can someone explain to me how they
have their
If they're running on standard ports, I don't see a way to do it for most
of these services, but perhaps someone knows something about NAT that I
don't. (If so, please share - I know of no way to do name-based NAT,
which is what you're asking for.)
You could certainly get it working with Apache
I have just started using the vserver package. My question is how do I
run multiple vservers on a single host, with each vserver running it's
own ssh and apache2 servers. Also, how will the host know to connect
incoming http requests to the appropriate vserver? Is there a detailed
guide I
On Wed, 10 Mar 2004, Chris Besignano wrote:
I have just started using the vserver package. My question is how do I
run multiple vservers on a single host, with each vserver running it's
own ssh and apache2 servers.
Each vserver needs its own IP address. And you'll need to reconfigure
