RE: chbind problems

About this list Date view Thread view Subject view Author view Attachment view

From: John Lyons (
Date: Sun Dec 30 2001 - 08:27:56 EST

It's not exactly a problem, rather a known 'feature'

The v_sshd, v_httpd scripts in /etc/init.d are there to allow you to start
sshd on the main server and automatically restrict the IP addresses that it
listens to.

There's some documentation in the examples section on the vserver site
explaining the commands needed to start a serice and bind it to an ip
address rather than


John Lyons
ICQ 74187012

Please quote your account number in the subject line of all emails.
Failure to do so may result in your enquiries taking longer to process.

> -----Original Message-----
> From: []
> Sent: 30 December 2001 12:52
> To: Jacques Gelinas;
> Subject: chbind problems
> Hello,
> further playing with vserver showed a problem with chbind.
> My version of sshd listens on all ipadressen found on the
> network card.
> This implies, that ssh'ing to the ip of a vserver ends up in a
> connection with the main server.
> One solution could be to change the configuration file of
> sshd. here an
> excerpt of my suse /etc/ssh/sshd_config:
> Port 22
> Protocol 1,2
> #ListenAddress
> #ListenAddress ::
> changing the ListenAddress to the ip of the main server, everything
> works as desired.
> This can only be a workaround.
> A conceptual solution for this problem would be, to make visible only
> ips from the same context.
> On
you ask,

Is this really a problem ?
I think within this context it is one.

Just another question: To start services in runlevel 5 I just tried:
vserver 01 enter
init 5
but I got : init: No such process
What would be the right way to solve that problem.

Thanks for an answer

About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.4 : Mon Aug 19 2002 - 12:01:00 EDT