I made some interesting finds I'd like to share. iptables 1.4.20 introduced a new locking mechanism to avoid failures during concurrent invocations [1]; a -w option has been introduced in order to have iptables wait until lock is released, and it seems that the issue can be solved by enabling that feature.
I'd like to file a bug report, but I'm wondering whether to file it against shorewall or against iptables, since its locking/wait mechanism should probably be enabled by default in order to ensure the iptables command will really do what is expected to. Any opinions? Thanks, Maurizio [1] http://git.netfilter.org/iptables/commit/?id=93587a04d0f2511e108bbc4d87a8b9d28a5c5dd8 http://git.netfilter.org/iptables/commit/?id=d7aeda5ed45ac7ca959f12180690caa371b5b14b ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
