LOGALLNEW=[log-level]
When set to a log level, this option causes Shorewall to
generate a logging rule as the first rule in each builtin chain.
o The table name is used as the chain name in the log prefix.
o The chain name is used as the target in the log prefix.
I'd like to make sure i'm understanding the functionality of the
LOGALLNEW option.
I changed it to "info" and it's definitely logging much more data.
But, is it logging every packet?
Is there a way that I can log an initial handshake until a session is
established?
Ultimately, what I'm trying to do is make sure I have data to review
in my logs for any packets that come IN or OUT of our network. The man
page says that there is no rate limiting when enabling LOGALLNEW, so
is it true that LOGRATE and LOGBURST won't help me with limiting when
enabling LOGALLNEW?
I don't need every single packet IN/OUT, if I have to, then that will
be fine, but I just thought i'd ask.
Thanks
Brad B.
--
Have Mercy & Say Yeah
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
