forked from extern/shorewall_code
Document fix for find_first_interface_address()
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
parent
cc561c0b61
commit
f424b4325f
@ -2,6 +2,8 @@ Changes in Shorewall 4.4.8.4
|
|||||||
|
|
||||||
1) Restore lone ACCEPT rule to the OUTPUT chain under OPTIMIZE 2.
|
1) Restore lone ACCEPT rule to the OUTPUT chain under OPTIMIZE 2.
|
||||||
|
|
||||||
|
2) Set IP before sourcing the params file.
|
||||||
|
|
||||||
Changes in Shorewall 4.4.8.3
|
Changes in Shorewall 4.4.8.3
|
||||||
|
|
||||||
1) Make wildcard interfaces play well with optimize 4.
|
1) Make wildcard interfaces play well with optimize 4.
|
||||||
|
@ -223,6 +223,9 @@ I I I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
|
|||||||
output policy was $FW->all ACCEPT, then the OUTPUT chain was empty
|
output policy was $FW->all ACCEPT, then the OUTPUT chain was empty
|
||||||
and no packets could be sent.
|
and no packets could be sent.
|
||||||
|
|
||||||
|
2) If find_first_interface_address() was called in the params file, a
|
||||||
|
fatal error occured on start/restart.
|
||||||
|
|
||||||
4.4.8.3
|
4.4.8.3
|
||||||
|
|
||||||
1) A problem with optimize 4 and wildcard interface names (those
|
1) A problem with optimize 4 and wildcard interface names (those
|
||||||
|
Loading…
Reference in New Issue
Block a user