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

More documentation updates

Browse Source
This commit is contained in:
Tom Eastep 2011-05-10 07:42:12 -07:00
parent c630a263db
commit a16dfcbc7b
2 changed files with 20 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Shorewall/known_problems.txt
View File

@ -20,3 +20,19 @@
Corrected in Shorewall 4.4.19.1
4) The changes in 4.4.19.1 that corrected long-standing issues with
default route save/restore are incompatible with 'gawk'. When
'gawk' is installed (rather than 'mawk'), awk syntax errors having
to do with the symbol 'default' were issued.
Workaround: Install mawk
5) An entry in the USER/GROUP column in the rules and tcrules files
can cause run-time start/restart failures if the rule(s) being
added did not have the firewall as the source or and was not being
added to the POSTROUTING chain.
Workaround: Insure that all USER/GROUP matches are only specified
when the SOURCE is $FW (rules file) or is being added to the
POSTROUTING chain (:T designator in the tcrules file).

7
Shorewall/releasenotes.txt
View File

@ -24,13 +24,14 @@ 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 or was
being added to the POSTROUTING chain. This error is now caught by
rule(s) being added did not have the firewall as the source (rules
file) and were not being added to the POSTROUTING chain (:T
designator in the tcrules file). 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 to a provider table. This prevents start/restart
that gateway in 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