>> after the upgrade, the firewall performs correctly but the >> shorewall.log is now broken. >What does that mean exactly?
Shorewall functions as it did before the upgrade... allows traffic that is allowed by the rulesets to get through and denies those that should be denied.
shorewall status shorewall hits shorewall stop shorewall start shorewall try ______
all function as expected.
However, when I go to access bering's weblet at 192.168.1.254 the shorewall.log does not show any detail. As if it has been broken and no longer sees the file.
The file itself located at /var/log/shorewall.log is 0 bytes.
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
