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

Tweak 4.4.19.3 release notes

Browse Source
This commit is contained in:
Tom Eastep 2011-05-10 07:22:30 -07:00
parent 4c459bd8cb
commit c630a263db
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Shorewall/releasenotes.txt
View File

@ -24,12 +24,13 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
2) Previously, an entry in the USER/GROUP column in the rules and
tcrules files could cause run-time start/restart failures if the
rule(s) being added did not have the firewall as the source. This
error is now caught by the compiler.
rule(s) being added did not have the firewall as the source or was
being added to the POSTROUTING chain. This error is now caught by
the compiler.
3) Shorewall now insures that a route to a default gateway exists in
the main table before it attempts to add a default route through
that gateway in a provider table. This prevents start/restart
that gateway to a provider table. This prevents start/restart
failures in the rare event that such a route does not exist.
4) CLASSIFY TC rules can apply to traffic exiting only the interface
@ -39,13 +40,13 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
1:2 - 1.2.3.4
This will work fine when 1.2.3.4 can only be routed out of a single
interface, but if we assume that interface 1 is eth0, then the
above rule only works for traffic leaving through eth0.
interface. However, if we assume that eth0 is interface 1, then the
above rule only works for traffic leaving via eth0.
Beginning with this release, the Shorewall compiler will interpret
the above rule as this one:
4.2 - eth0:1.2.3.4
1.2 - eth0:1.2.3.4
4.4.19.2