forked from extern/shorewall_code
Document 4.4.19.3 fixes
This commit is contained in:
parent
631a2a7092
commit
a7edb358ed
@ -2,6 +2,10 @@ Changes in Shorewall 4.4.19.3
|
||||
|
||||
1) Eliminate issue with 'gawk'.
|
||||
|
||||
2) Ensure that a host route to the gateway exists in the main table.
|
||||
|
||||
3) Only allow USER/GROUP in the OUTPUT chain.
|
||||
|
||||
Changes in Shorewall 4.4.19.2
|
||||
|
||||
1) Restore the ability to have IPSET names in the ORIGINAL DEST column
|
||||
|
@ -22,6 +22,16 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
|
||||
|
||||
This incompatibility has been corrected.
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
failures in the rare event that such a route does not exist.
|
||||
|
||||
4.4.19.2
|
||||
|
||||
1) In Shorewall-shell, there was the ability to specify IPSET names in
|
||||
|
Loading…
Reference in New Issue
Block a user