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

From: Thomas Gelf (vserver_at_gelf.net)
Date: Fri 27 Feb 2004 - 08:34:26 GMT


Am Fre, den 27.02.2004 schrieb Alex Lyashkov um 09:11:
> ÷ ðÔÎ, 27.02.2004, × 10:03, Thomas Gelf ÐÉÛÅÔ:
> > is it possible to realize this?
> > how much work would it be?
> >
> > the first part (tun/tap interface == virtual eth0 inside the vserver,
> > bridge them to real eth0, allow CAP_NET_ADMIN for the visible interfaces
> > only) should be no problem, what about per-context routing/firewalling?
> >
> VServer not have it.

that's the reason why I posted this - something like that should be
developed. my questions are:

- is it realizable?
- if not: why not?
- how much work would it be?

probably stable vs shouldn't be modified that way, but what about kernel
2.6? a usable networking support is in my opinion an essential
requirement for a vserver project - and at the moment the network
inside a vserver "works", but there is still no real networking support.

-- 
Thomas Gelf <vserver_at_gelf.net>

_______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver


About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Fri 27 Feb 2004 - 08:34:03 GMT by hypermail 2.1.3