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

Update release documents

Browse Source
This commit is contained in:
Tom Eastep 2011-04-14 15:20:15 -07:00
parent 8fa41771bd
commit 4c1fbb67e4
2 changed files with 18 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -6,6 +6,8 @@ Changes in Shorewall 4.4.19.1
3) Restore :<low port>-<high port> in masq file.
4) Correct default route safe/restore.
Changes in Shorewall 4.4.19 Final
1) Update release documents.

22
Shorewall/releasenotes.txt
View File

@ -18,15 +18,25 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
1) A duplicate ACCEPT rule in the INPUT chain has been eliminated when
the firewall is stopped.
2) Shorewall previously interpreted all 'nexthop' routes as default
routes when analyzing the pre-start routing configuration. This
could lead to unwanted default routes when the firewall was started
or stopped.
3) A defect introduced in Shorewall 4.4.17 broke the ability to
2) A defect introduced in Shorewall 4.4.17 broke the ability to
specify ':<low port>-<high port>' in the ADDRESS column of
/etc/shorewall/masq.
3) Several long-standing defects having to do with default route
save/restore have been corrected in the Multi-ISP implementation.
a) Shorewall previously interpreted all 'nexthop' routes as
default routes when analyzing the pre-start routing
configuration. This could lead to unwanted default routes when
the firewall was started or stopped.
b) The default route with metric 0 was usually not restored
during 'stop' processing.
c) If there were multiple default routes in the main table prior
to 'shorewall start' and USE_DEFAULT_RT was set, only the
first one with metric 0 was deleted.
4.4.19
1) Corrected a problem in optimize level 4 that resulted in the