Document optimization bugs

This commit is contained in:
Tom Eastep 2010-08-23 15:44:04 -07:00
parent 1e6f293c3c
commit f8f4e009f4
3 changed files with 25 additions and 1 deletions

View File

@ -1,3 +1,7 @@
Changes in Shorewall 4.4.11.4
1) Fix a couple of old optimization bugs.
Changes in Shorewall 4.4.11.3
1) Fix duplicate rule generation with 'any'.

View File

@ -85,3 +85,14 @@
11) AUTOMAKE=Yes is broken -- don't use it.
Corrected in Shorewall 4.4.11.3.
12) Under rare circumstances where COMMENT is used to attach comments
to rules, OPTIMIZE 8 through 15 can result in invalid
iptables-restore (ip6tables-restore) input.
Workaround: Don't use optimizaiton levels greater than 7.
2) Under rare circumstances unvolving exclusion, OPTIMIZE 8 through 15
canresult in invalid iptables-restore (ip6tables-restore) input.
Workaround: Don't use optimizaiton levels greater than 7.

View File

@ -1,5 +1,5 @@
----------------------------------------------------------------------------
S H O R E W A L L 4 . 4 . 1 1 . 3
S H O R E W A L L 4 . 4 . 1 1 . 4
----------------------------------------------------------------------------
I. RELEASE 4.4 HIGHLIGHTS
@ -218,6 +218,15 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
I I I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
----------------------------------------------------------------------------
4.4.11.4
1) Under rare circumstances where COMMENT is used to attach comments
to rules, OPTIMIZE 8 through 15 could result in invalid
iptables-restore (ip6tables-restore) input.
2) Under rare circumstances unvolving exclusion, OPTIMIZE 8 through 15
could result in invalid iptables-restore (ip6tables-restore) input.
4.4.11.3
1) When 'any' was used in the rules SOURCE column, a duplicate rule