Hello Chris, Chris, I suggest you review your design - to do what you want to do, people invented shared hosting quite a long time ago. 1 apache/mysql/popd is capable of serving multiple virtualhosts on the same IP w/o overhead of running multiple servers/vservers.
The sole purpose of the vserver project is to provide close emulation of SEPARATE hardware boxes. Thursday, March 11, 2004, 8:41:09 AM, you wrote: CB> I need to run a few different websites on my box using vservers. What CB> method does everyone use to route the traffic from eth1 (externel CB> interface, real ip) to the vservers bound to eth0 (internal ip, CB> 192.168.x.x network)? CB> Darryl Ross wrote: >> 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. >>> If what you say was true, there wouldn't be much difference between >>> vserver setup and chrooted services. >> >> >> Did you read what he said?? >> >> As per your quote above, emphasis is mine: >> >> > services in the __host__ to ONLY bind the __host's__ IP address >> >> which is exactly what you want to do. If you need to run a service in >> the host, as well as inside the vservers (eg, ssh), you need to tell >> the host sshd to only bind to the main IP, not the IP addresses of all >> the vservers. >> >> Cheers >> Darryl >> _______________________________________________ -- Alex mailto:[EMAIL PROTECTED] 8:38:57 AM Thursday, March 11, 2004 EDT _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
