Subject: Re: [vserver] Avoiding kernel internal routing among vserver clients
From: Thomas Weber <l_vserver@mail2news.4t2.com>
Date: Tue, 07 Aug 2007 23:04:28 +0200

Am Dienstag, den 07.08.2007, 12:05 +0200 schrieb Rik Bobbaers:
> i don't know if this will work but...
> 
> if you make a routing table for each ip of a virtual server, with routes 
> to your gateway, wouldn't that work?
> in /etc/rt_tables:
> 100 vs1
> 101 vs2
> etc...
> 
> and then for each table, a different/same route:
> ip route add <hostip>/32 dev $IF table vs1
> ip route add default via $GW dev $IF table vs1
> ip rule add from $IP/32 table vs1 pref 1000
> 
> something like that? (i made sort of the same routing stuff, but i want 
> only 1 route for each subnet ;))

That was like the first thing i've tried. Routing to anything thats not
locally hosted works just fine. But once you try to reach another
vserver on another subnet that happens to be hosted on the same host it
will route internally and not hit the wire at all - which is bad and
actually makes vservers unusable if you want to move vservers among
different hosts. 
Firewalling between the vserver clients for example is not manageable.
IDS would be another issue.

  Tom