I ran into a problem with shorewall save/restore in version 3.4.7. I
have SAVE_IPSETS=Yes and had just defined an ipset with a default
binding to another ipset. The problem was the
/var/lib/shorewall/restore-ipsets script that was generated did not
delete the default binding, so it was unable to destroy the ipset.
The attached patch to 3.4.7 solved the problem for me. Hope it helps
someone else.
--
David Rothenberger ---- daveroth@acm.org
"Be *excellent* to each other."
-- Bill, or Ted, in Bill and Ted''s Excellent Adventure
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
David Rothenberger wrote:> I ran into a problem with shorewall save/restore in version 3.4.7. I > have SAVE_IPSETS=Yes and had just defined an ipset with a default > binding to another ipset. The problem was the > /var/lib/shorewall/restore-ipsets script that was generated did not > delete the default binding, so it was unable to destroy the ipset. > > The attached patch to 3.4.7 solved the problem for me. Hope it helps > someone else.Thanks, David. Roberto: I think that a similar change is also needed in the compiler in the define_firewall() function. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/