From: Paul Sladen (vserver_at_paul.sladen.org)
Date: Thu 17 Oct 2002 - 20:50:45 BST
On Thu, 17 Oct 2002, Michael Stowe wrote:
> I've tried to locate the mailing list archives
The person who used to host the list archives has had to stop; we're in the
process of getting another archive setup with all the old messages in it.
> My question is: Am I correct in assuming that a vserver can only
> esablish outgoing network connections and not have any incoming
> connections ( Like SSH. )?
No. (The vservers wouldn't much use if that was the case! :-).
By default programs (daemons/servers) normally bind to the IP ``0.0.0.0''
which means "all IP addresses" (including those IP addresses of vserver,
even if they haven't been started yet). Because the host server has access
to all the IP addresses in the system it will steal them before the vservers
have a chance to use them.
So your copy of SSH in the host-server has started up and grabbed Port 22
(the SSH port) on all the addresses in the system, meaning that when you
startup the vserver, the port is already taken on their IP address.
You should edit `/etc/ssh/sshd_config' on the host server and add:
Now when you restart SSH and then restart the vservers; the Port/IP will no
long be being stolen by the SSH daemon running in the host server.
You will need to do this for all your services (Apache, Sendmail, etc)
running in the host server. (The easist is just to /not/ running anything
in the host-server except SSH; and then configure that as above).
If you really want to run more services in the host-server, you should
investigate the `/etc/init.d/v_ssh' style scripts, which enable you run
services in the host server, but force them to only listen on the IP address
of the host server. If one doesn't exist your service, copy-and-paste one
of the existing examples.
-- Nottingham, GB