Overview

Request 331029 accepted

- Update to version 4.6.13 For more details see changelog.txt and
realeasenotes.txt
* The 'rules' file manpages have been corrected regarding the
packets that are processed by rules in the NEW section.
* Parsing of IPv6 address ranges has been corrected. Previously,
use of ranges resulted in 'Invalid IPv6 Address' errors.
* The shorewall6-hosts man page has been corrected to show the
proper contents of the HOST(S) column.
* Previously, INLINE statements in the mangle file were not
recognized if a chain designator (:F, :P, etc.) followingowed
INLINE(...). As a consequence, additional matches following
a semicolon were interpreted as column/value pairs unless
INLINE_MATCHES=Yes, resulting in compilation failure.
* Inline matches on IP[6]TABLE rules could be ignored if
INLINE_MATCHES=No. They are now recognized.
* Specifying an action with a logging level in one of the
_DEFAULT options in shorewall[6].conf
(e.g., REJECT_DEFAULT=Reject:info) produced a compilation error:
ERROR: Invalid value (:info) for first Reject parameter
/usr/share/shorewall/action.Rejectect (line 52)
That has been corrected. Note, however, that specifying logging
with a default action tends to defeat one of the main purposes
of default actions which is to suppress logging.
* Previously, it was necessary to set TC_EXPERT=Yes to have full
access to the user mark in fw marks. That has been corrected so
that any place that a mark or mask can be specified, both the
TC mark and the User mark are accessible.

Loading...
Request History
Togan Muftuoglu's avatar

toganm created request

- Update to version 4.6.13 For more details see changelog.txt and
realeasenotes.txt
* The 'rules' file manpages have been corrected regarding the
packets that are processed by rules in the NEW section.
* Parsing of IPv6 address ranges has been corrected. Previously,
use of ranges resulted in 'Invalid IPv6 Address' errors.
* The shorewall6-hosts man page has been corrected to show the
proper contents of the HOST(S) column.
* Previously, INLINE statements in the mangle file were not
recognized if a chain designator (:F, :P, etc.) followingowed
INLINE(...). As a consequence, additional matches following
a semicolon were interpreted as column/value pairs unless
INLINE_MATCHES=Yes, resulting in compilation failure.
* Inline matches on IP[6]TABLE rules could be ignored if
INLINE_MATCHES=No. They are now recognized.
* Specifying an action with a logging level in one of the
_DEFAULT options in shorewall[6].conf
(e.g., REJECT_DEFAULT=Reject:info) produced a compilation error:
ERROR: Invalid value (:info) for first Reject parameter
/usr/share/shorewall/action.Rejectect (line 52)
That has been corrected. Note, however, that specifying logging
with a default action tends to defeat one of the main purposes
of default actions which is to suppress logging.
* Previously, it was necessary to set TC_EXPERT=Yes to have full
access to the user mark in fw marks. That has been corrected so
that any place that a mark or mask can be specified, both the
TC mark and the User mark are accessible.


Togan Muftuoglu's avatar

toganm accepted request

reviewed OK

openSUSE Build Service is sponsored by