Eduardo Ferreira wrote: > > > Tom Eastep wrote on 10/04/2007 22:29:53: >> > >> > It is definitely too early to use Shorewall-perl in production. I'm > still >> > fixing really bad bugs. >> > I guess I'll have to wait. oh, what a pity.
I would definitely wait until 3.9.1 before I tried a very complex configuration. There are lots of known problems with 3.9.0 (see http://www1.shorewall.net/pub/shorewall/development/3.9/shorewall-perl-3.9.0/known_problems.txt). > >> Although as of lunch hour yesterday, I am now running Shorewall-perl on >> my own firewall. > How could I help and test? Would a iptables-save diff between the two > versions (3.4.2? x shorewall-perl) be a valid way to compare them both? You can help by trying shorewall-perl on as many configurations as you can. If it blows up or doesn't work, I will need the configuration directory with a capabilities file. Comparing the output of iptables-save is a good way to check the configuration but you should not expect the output to be exactly the same. Shorewall-perl has a completely new way of dealing with broadcast addresses (see the release notes). But again, I would wait until 3.9.1... Thanks for volunteering to help, -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Shorewall-devel mailing list Shorewall-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-devel
