Hmmm... Actually, echoWall and ShoreWall seem as though they would both benifit from
aspects of each other. For instance, if ShoreWall is sufficiently modular, it would
be easy for Scott to create ShoreWall modules for all of the standard applications
echoWall is set up for.
This would, to
Wyatt:
Heya. Interesting question. I think the best way to
compare and contrast the different firewall-setup packages
is to ask the authors what their intent was for providing it.
I know I built echoWall with a target user in mind, and
if you're the target user, and you're not
Heya sport fans. Sorry for the delay...took a
few days off grieving the loss of my first floppy. :)
Echowall is now rev'd to 1.40, and the old
problems with 1.33's use of cut has been fixed.
It also fixes the problem of killing off all copies
(and not just one) of ipfwd in the
Now, this is me responding without doing any sort of reading on Echowall, but here
goes anyway. I'm currently using Oxygen with Seawall, and it seems to have what I
need it to: port-forwarding to internal servers, DMZ and some sort of VPN support
(although I need to figure it out and start).
