2004-07-07 16:16:55 +02:00
|
|
|
Shorewall 2.0.5
|
2004-03-15 19:47:21 +01:00
|
|
|
|
|
|
|
|
----------------------------------------------------------------------
|
2004-07-07 16:16:55 +02:00
|
|
|
Problems Corrected in version 2.0.4
|
2004-05-14 00:07:06 +02:00
|
|
|
|
2004-07-06 16:13:52 +02:00
|
|
|
1) A DNAT rule with 'fw' as the source that specified logging caused
|
|
|
|
|
"shorewall start" to fail.
|
2004-05-14 00:07:06 +02:00
|
|
|
|
2004-07-07 16:16:55 +02:00
|
|
|
----------------------------------------------------------------------
|
|
|
|
|
Problems Corrected in version 2.0.5
|
|
|
|
|
|
|
|
|
|
1) Eliminated "$RESTOREBASE: ambiguous redirect" messages during
|
|
|
|
|
"shorewll stop" in the case where DISABLE_IPV6=Yes in
|
|
|
|
|
shorewall.conf.
|
|
|
|
|
|
2004-07-10 04:08:03 +02:00
|
|
|
2) An anachronistic reference to the mangle option was removed from
|
|
|
|
|
shorewall.conf.
|
2004-07-11 18:17:29 +02:00
|
|
|
|
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
|
Problems Corrected in version 2.0.6
|
|
|
|
|
|
|
|
|
|
1) Some users have reported with the pkttype match option in iptables/
|
|
|
|
|
Netfilter failing to match certain broadcast packets. The result
|
|
|
|
|
is that the firewall log shows a lot of broadcast packets being
|
|
|
|
|
logged.
|
|
|
|
|
|
|
|
|
|
Users experiencing this problem can use PKTTYPE=No in
|
|
|
|
|
shorewall.conf to cause Shorewall to use IP address filtering of
|
|
|
|
|
broadcasts rather than packet type.
|
