Tom Eastep wrote: > Tom Eastep wrote: >> Tom Eastep wrote: >> >>> The bug has nothing to do with Shorewall-lite but rather is a result >>> of the change that I made in 4.0.11 to defer setting up ip forwarding >>> until after the rules are in place. I missed the case where the >>> command is 'restore' (which is what occurs when -f is specified to >>> 'start' and there is a saved config). >>> >>> Patch attached. >> >> I've also uploaded Shorewall-perl 4.0.11.2 which corrects the problem. > > And Shorewall-perl-4.0.12.1.
why not you release 4.0.13? versions are cheap. anyway even it's a small bug and the fix is very little imho it's a serious bug. since anyone who update to 4.0.11 and later sometime reboot his firewall (what's more do it remotely) cause that it's stop working. and it's hard to find the reason (i learn it in the hard way). and currently the latest version in fedora, redhat and centos (epel) is 4.0.11 which makes thing worst. -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
