forked from extern/shorewall_code
Update release docs for NULL_ROUTE_RFC1918 fix
This commit is contained in:
parent
e32a7167ff
commit
5bd5a16e5c
@ -1,8 +1,8 @@
|
|||||||
Changes in Shorewall 4.4.14.1
|
Changes in Shorewall 4.4.14.1
|
||||||
|
|
||||||
None.
|
1) Clear VERBOSE and VERBOSITY at CLI startup
|
||||||
|
|
||||||
3) Fix NULL_ROUTE_RFC1918
|
2) Fix NULL_ROUTE_RFC1918
|
||||||
|
|
||||||
Changes in Shorewall 4.4.14
|
Changes in Shorewall 4.4.14
|
||||||
|
|
||||||
|
@ -14,7 +14,13 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
|
|||||||
----------------------------------------------------------------------------
|
----------------------------------------------------------------------------
|
||||||
4.4.14.1
|
4.4.14.1
|
||||||
|
|
||||||
None.
|
1) If the current environment exported the VERBOSE variable with a
|
||||||
|
non-zero value, then startup would fail.
|
||||||
|
|
||||||
|
2) If a route existed for an entire RFC1918 subnet (10.0.0.0/8,
|
||||||
|
172.20.0.0/12 or 192.168.0.0/16), then setting
|
||||||
|
NULL_ROUTE_RFC1918=Yes would cause the route to be replaced with an
|
||||||
|
'unreachable' one.
|
||||||
|
|
||||||
4.4.14
|
4.4.14
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user