From: Cathy Sarisky (cathy_at_acornhosting.net)
Date: Thu 17 Oct 2002 - 20:46:26 BST
You most likely need to make sure that SSH isn't binding all IPs in the main server. If the main server already has bound the vserver's IP, the vserver's instance of SSH won't be able to use it. Edit sshd_config to change the ListenAddress parameter, and you should be all set.
(Caveat: carefully! There's nothing worse than locking yourself out of the box!)
---------- Original Message ----------------------------------
From: "Michael Stowe" <stowem_at_ravenous.net>
Reply-to: vserver_at_solucorp.qc.ca
Date: Thu, 17 Oct 2002 12:01:44 -0700
>Georges:
>
>Thanks for the resonse. If that's not correct, then I must have missed
>something in the network configuration.
>
>When I start the vserver, I have the eth interface disabled in the vserver.
>On the host server, it creates an alias of eth0:<server name>..when I ssh
>into the IP I give it, I get the host server and not the vserver (
>Undertandably because it's an alias on the host's ethernet controller. ). Is
>there some sort of redirection I need to do?
>
>Thanks.
>
>
>--
>Michael Stowe
>Systems Administrator
>Alcatraz Media, LLC
>http://www.alcatrazmedia.com
>
>
>----- Original Message -----
>From: "Georges Toth" <georges_at_norm.lu>
>To: <vserver_at_solucorp.qc.ca>
>Sent: Thursday, October 17, 2002 11:45 AM
>Subject: Re: [vserver] FAQ location and question
>
>
>> hi,
>>
>> > 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. )?
>>
>> nope, that's not correct
>>
>> --
>> regards,
>> Georges Toth
>>
>>
>
>
>
________________________________________________________________
Sent via the WebMail system at webmail.pioneernet.net