extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-20 17:58:07 +02:00
Code Issues Packages Projects Releases Wiki Activity

Document accounting fixes

Browse Source
This commit is contained in:
Tom Eastep 2011-02-03 09:57:59 -08:00
parent 23eef3b215
commit 475b811171
2 changed files with 24 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -10,6 +10,8 @@ Changes in Shorewall 4.4.17 RC 1
5) Several fixes to IPv6 tcfilters. 5) Several fixes to IPv6 tcfilters.
6) Correct three issues in per-IP accounting.
Changes in Shorewall 4.4.17 Beta 3 Changes in Shorewall 4.4.17 Beta 3
1) Allow run-time address variables in the masq file. 1) Allow run-time address variables in the masq file.

21
Shorewall/releasenotes.txt
View File

@ -41,6 +41,27 @@ RC 1
c) There is now an ipv6 tcfilters skeleton included with c) There is now an ipv6 tcfilters skeleton included with
Shorewall6. Shorewall6.
3) Several issues with accounting are corrected.
a) If an accounting rule of the form:
chain1 chain2
was configured and neither chain was referenced again in the
configuration, then an internal error was generated when
optimize level 4 was selected and OPTIMIZE_ACCOUNTING=Yes.
b) If there was only a single accounting rule and that rule
specified an interface in the SOURCE or DEST columns, then the
generated ruleset would fail to load when
OPTIMIZE_ACCOUNTING=Yes.
c) If a per-IP accounting table name appeared in more than one
rule and the specified network was not the same in all
occurrences, then the generated ruleset would fail to load.
This is now flagged as an error at compile time.
Beta 3 Beta 3
1) If the SOURCE column in /etc/shorewall6/rules contained an IPv6 1) If the SOURCE column in /etc/shorewall6/rules contained an IPv6