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 ---- [EMAIL PROTECTED]
"Be *excellent* to each other."
-- Bill, or Ted, in Bill and Ted's Excellent Adventure
#! /bin/sh /usr/share/dpatch/dpatch-run
## 98.ipset_unbind.dpatch by <David Rothenberger <[EMAIL PROTECTED]>>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: No description.
@DPATCH@
diff -urNad shorewall-3.4.7~/lib.cli shorewall-3.4.7/lib.cli
--- shorewall-3.4.7~/lib.cli 2007-09-08 09:04:21.000000000 -0700
+++ shorewall-3.4.7/lib.cli 2007-10-17 10:28:59.000000000 -0700
@@ -306,6 +306,7 @@
echo "__EOF__" >> $f
echo >> $f
echo "ipset -U :all: :all:" >> $f
+ echo "ipset -U :all: :default:" >> $f
echo "ipset -F" >> $f
echo "ipset -X" >> $f
echo "ipset -R << __EOF__" >> $f
-------------------------------------------------------------------------
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/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
