DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=OK3w59yE6wUZJspZueNqxLNeyYzbdKiTLv6YxvYqu20vdVkrhtY5IltW7pFJFYEdhP
         4wi0INRa109kjvtD2rpP/yyEg4G2Uq//Xu0dcPq92IfY7IXVn3/r1j1xA4ZAKdZHXSMX
         8KAlt8tZma8EO/lN/eQtF0n1qSHVwzhbqrL60=
Precedence: list
MIME-Version: 1.0
In-Reply-To: <4AD88C6B.1000201@freemail.gr>
References: <4AD88C6B.1000201@freemail.gr>
Date: Fri, 16 Oct 2009 18:07:57 +0000
Message-ID: <95408c820910161107l84597c9y364ec2cdabb2de68@mail.gmail.com>
Subject: Re: [alpine-devel] vserver
From: Natanael Copa <natanael.copa@gmail.com>
To: Harry Lachanas <grharry@freemail.gr>
Cc: Alpine Developers <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1

On 10/16/09, Harry Lachanas <grharry@freemail.gr> wrote:
> I wonder
> a) if possible to achive networking  ( any kernel issues here  ??) on
> vserver  and vhosts using bridges ( like  xen,  openvz  )

no becuase xen an openvz provides a virtual network stack for the
guests (with xen the guest needs another kernel with network stack).
The network interface in guest is the same network interface on host.

well... that means that you can create a bridge on the host and assign
it to the guest, but the problem here is that the guest and host share
the network interface.

> b) If anybody succeded doing it ?
>
> Vserver networking IMHO is not the best you can get ...

depends on how you define "best". if you mean flexible (as in each
guest can run its own firewall) then you are right. If you mean use
less resources (speedier and less memory) then vserver is the best. :)

>
> Immediately after I installed vs and vhost and ssh on both .. I crashed
> into this
>
> http://linux-vserver.org/Frequently_Asked_Questions#When_I_try_to_ssh_to_the_guest.2C_I_log_into_the_host.2C_even_if_I_installed_sshd_on_the_guest._What.27s_wrong_here.3F
>
>
> ( my luck I guess ;-) )

yeah... you are right. networking might be slightly tricky since the
guests shares the network with host. Think chroot. If you have got the
guest running and you run "ip addr" on host you will see that the
guests ip addesses is assigned to the hosts network interface. Again.
think the guest as a chroot more than a virtual machine.

That said, the newer kernels does have some nice tricks to hide the
problem with 0.0.0.0 address binding and loopback.

I even think they have done some attempt to create virtual network
stacks for the guests in recent kernels. I havent tested those though.

What do you run on your vserver host? kernel version?

I'm working on setting up a compile server for alpine and I need to
have vserver with recent kernel on that one. (actually working on it
as we speak)

-- 
Natanael Copa


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---