On May 22, 2011, at 9:23 AM, Mr Dash Four wrote: > >> Summary of Beta 3: >> >> [...] >> >> g) The builtin actions (dropBroadcast, rejNonSyn, etc.) now support >> an 'audit' parameter which causes all ACCEPT, DROP and REJECTs >> performed by the action to be audited. This allows creation of >> audited versions of the Shorewall-provided default actions >> (action.Drop and action.Reject). >> >> Note: The builtin actions are those actions listed in the >> output of 'shorewall show actions' whose names begin with a >> lower-case letter. >> > How do I utilise this (I don't have/use any of these actions as far as I > know, but they are still included in my chains)?
Read:
http://www.shorewall.net/Actions.html#Default
http://www.shorewall.net/Audit.html
> Otherwise, pretty
> extensive changes which I would be able to test through as soon as I get
> out of the rut I am in at present. You were also planning to introduce
> "random-generated-and-unused" number allocated to devices - for use in
> tcdevices, do you remember?
I remember you complaining about the current algorithm.
> I'll do some testing tomorrow, hopefully!
Thanks
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
PGP.sig
Description: This is a digitally signed message part
------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
