holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Update release documents for 4.4.21.1

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2011-07-19 07:01:02 -07:00
parent ef2f19ce35
commit 778302daba
3 changed files with 31 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -8,6 +8,8 @@ Changes in Shorewall 4.4.21.1
4) Fix -j SNAT --to-address ... --persistent 4) Fix -j SNAT --to-address ... --persistent
5) Fix LOGMARK.
Changes in Shorewall 4.4.21 Final Changes in Shorewall 4.4.21 Final
1) Update release documents. 1) Update release documents.

14
Shorewall/known_problems.txt
View File

@ -4,11 +4,23 @@
2) A harmless 'unitialized variable' diagnostic is issued by the 2) A harmless 'unitialized variable' diagnostic is issued by the
compiler when it is displaying the capabilities. compiler when it is displaying the capabilities.
Corrected in Shorewall 4.4.21.
3) As the result of a typo, an orphan filter chain named FORWAR can 3) As the result of a typo, an orphan filter chain named FORWAR can
be created under rare circumstances. This chain is deleted by be created under rare circumstances. This chain is deleted by
OPTIMIZE level 4. OPTIMIZE level 4.
3) The SNAT options --persistent and --randomize (/etc/shorewall/masq) Corrected in Shorewall 4.4.21.
4) The SNAT options --persistent and --randomize (/etc/shorewall/masq)
generate invalid iptables input. generate invalid iptables input.
Corrected in Shorewall 4.4.21.
5) The LOGMARK log level was generated invalid iptables input making
it unusable.
Corrected in Shorewall 4.4.21.

16
Shorewall/releasenotes.txt
View File

@ -26,6 +26,22 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
3) The SNAT options --persistent and --randomize now work properly 3) The SNAT options --persistent and --randomize now work properly
(/etc/shorewall/masq). (/etc/shorewall/masq).
4) The LOGMARK log level was previously generated invalid iptables
input making it unusable. That has been corrected.
The syntax for LOGMARK is now:
LOGMARK(<priority>)
where <priority> is a syslog priority (1-7 or debug, info, notice,
etc.).
Example rule:
#ACTION SOURCE DEST PROTO DEST
# PORT(S)
LOG:LOGMARK(info) lan dmz udp 1234
4.4.21 Final 4.4.21 Final
1) All problems corrections included in Shorewall 4.4.20.1 - 4.4.20.3 1) All problems corrections included in Shorewall 4.4.20.1 - 4.4.20.3