Overview
Request 90213 accepted
- Update to 4.4.25.2 For more details see changelog.txt and
releasenotes.txt
* Previously, if all the following were true:
- AUTOMAKE=Yes
- Current compiled script (/var/lib/shorewall/firewall or
/var/lib/shorewall6/firewall) up to date
- LEGACY_FASTSTART=No
- There was a saved configuration
then rather than start the current configuration, 'shorewall
start -f' or 'shorewall6 start -f' would incorrectly restore
the saved configuration.
* The DropSmurfs and TCPFlags actions are now available in
Shorewall6. They were previously omitted from the IPv6
actions.std file.
* The 'rawpost' table was previously omitted from the output of
the 'dump' command. It is now displayed.
* Previously, if a configuration contained more than one wildcard
interface (physical name ending in '+'), then the generated script
might not work properly with Shorewall-init. This defect dates back
to the introduction of Shorewall-init.
- Created by toganm
- In state accepted
- Package maintainers: bruno_friedmann and polslinux
Request History
toganm created request
- Update to 4.4.25.2 For more details see changelog.txt and
releasenotes.txt
* Previously, if all the following were true:
- AUTOMAKE=Yes
- Current compiled script (/var/lib/shorewall/firewall or
/var/lib/shorewall6/firewall) up to date
- LEGACY_FASTSTART=No
- There was a saved configuration
then rather than start the current configuration, 'shorewall
start -f' or 'shorewall6 start -f' would incorrectly restore
the saved configuration.
* The DropSmurfs and TCPFlags actions are now available in
Shorewall6. They were previously omitted from the IPv6
actions.std file.
* The 'rawpost' table was previously omitted from the output of
the 'dump' command. It is now displayed.
* Previously, if a configuration contained more than one wildcard
interface (physical name ending in '+'), then the generated script
might not work properly with Shorewall-init. This defect dates back
to the introduction of Shorewall-init.
toganm accepted request
reviewed ok.