From 4c1fbb67e4388448bd453b284c45a410a12de755 Mon Sep 17 00:00:00 2001 From: Tom Eastep Date: Thu, 14 Apr 2011 15:20:15 -0700 Subject: [PATCH] Update release documents --- Shorewall/changelog.txt | 2 ++ Shorewall/releasenotes.txt | 22 ++++++++++++++++------ 2 files changed, 18 insertions(+), 6 deletions(-) diff --git a/Shorewall/changelog.txt b/Shorewall/changelog.txt index 4daa24ebf..1a8fe3ea6 100644 --- a/Shorewall/changelog.txt +++ b/Shorewall/changelog.txt @@ -6,6 +6,8 @@ Changes in Shorewall 4.4.19.1 3) Restore :- in masq file. +4) Correct default route safe/restore. + Changes in Shorewall 4.4.19 Final 1) Update release documents. diff --git a/Shorewall/releasenotes.txt b/Shorewall/releasenotes.txt index 0088b18ef..a54de0738 100644 --- a/Shorewall/releasenotes.txt +++ b/Shorewall/releasenotes.txt @@ -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 ':-' 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