On Jul 11, 2010, at 12:19 PM, Michael wrote: > Lonnie Abelbeck wrote: > >> I tested this, and it works for me. Remember that 'Log Local Out' only >> applies to packets outbound directly from the local AstLinux box (OUTPUT >> Chain), *not* forwarded packets, (FORWARD Chain). For example packets >> from a web browser on a LAN NAT'ed subnet will not show with "Log Local >> Out". On the other hand, if you ssh into the AstLinux box (or use serial >> console) and enter... > > That explains it. Thanks a lot. Of course, I thought I would log ALL > outgoing traffic and I thus used a local browser on the LAN to generate > traffic. > > So, how would I go and monitor the FORWARD chain? Because, if the astlinux > box is used as a router, then this is the interesting information.
AstLinux uses Arno's IPtables Firewall script for the firewall. If I remember correctly, there is no direct support for logging all FORWARD Chain traffic. I don't know how useful that would be anyway, a lot of chaff to sort through. Logging blocked traffic is usually more useful. The firewall Tab options: __ Log Denied TCP attempts to privileged and unprivileged ports __ Log Denied UDP attempts to privileged and unprivileged ports __ Log Denied non-TCP/UDP/ICMP attempts (restart firewall after an change) can be quite useful to track down firewall configuration issues. Lonnie ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
