Solution: Use the distribution's configuration files for interfaces, ans shorewall (www.shorewall.net) for firewall rules. It simplifies thing to great extents.


Simplifies? It may be that these guys are bad in documentation, but after a first glance on their "Setup guide", there's nothing simple about it. They have a similar way to define the zones, yes, but that's as close as they get to what I had in mind.

What I meant was being able to use almost natural language to describe the network and its rules. Something like "I have a group of hosts connected to eth0, I have another group on eth1, and I want the first group be clients on port 80 of the second group".

"Intuitive", as I define it, is when a simple example is enough to explain how to use a system, and when a newbie tries things out, they work as expected.

Eli



=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]



Reply via email to