Re: [vserver] IPtables, network namespaces

From: Art -kwaak- van Breemen <>
Date: Wed 28 Mar 2012 - 14:47:48 BST
Message-ID: <>


On Wed, Mar 21, 2012 at 10:30:22PM +0900, Christian Balzer wrote:
> I believe any host based iptables (as in some client tool messaging
> something on the host to manipulate a client specific iptable) is
> cumbersome at best and prone to abuse at worst.

We have a different view on iptables :-) and customers.
We give each guest their own (multiple) DMZ's. Each DMZ has it's
own network namespace, and it's own network device (just a vlan).
Per DMZ multiple network contexts can exist.
Firewalling is done using an external firewall.
Customers are not capable of doing iptable setups, so they
request with explanation some access, and we either
honour that, come up with a better solution, or deny it with
Simple port 80 requests are all going through a transparent
outbound proxy (squid).
We try to deny ftp and honour sftp using Connect method through a
Anyway, keeping them tied in prevents a lot of abuse: any exploit
is contained within it's DMZ, so you have to be a real hacker and
not a script to get through ;-) .

Anyway: I think using vserver is worth the pain in this case.

Received on Wed Mar 28 14:48:00 2012

[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Wed 28 Mar 2012 - 14:48:00 BST by hypermail 2.1.8