search for: logmarker

Hi everyone, Xtables-addons 1.5.4 has been released; highlights of this release are the import, cleanup/bugfixing the "condition" and "ipp2p" matches and additionally extending the "IPMARK" by IPv6. I hope people don''t mind, but I have not heard back so far, so I take it it''s ok. LOGMARK (for analyzing packet marks and connection states) now

The version of Shorewall in the \Shorewall CVS project has my next attempt at Fireparse integration. a) The LOGMARKER variable is gone and is replaced with LOGFORMAT b) LOGFORMAT contains a printf (1) formatting template that accepts three arguments: 1) The Chain Name 2) The Logging Rule Number within Chain 3) The disposition of the packet (DROP,REJECT,ACCEPT) c) To use Shorewall with Fireparse, I believe th...

...insures that all loopback traffic is allowed even if Netfilter connection tracking is confused. New Features: 1) IPV6-IPV4 (6to4) tunnels are now supported in the /etc/shorewall/tunnels file. 2) Shorewall can now be easily integrated with fireparse (http://www.fireparse.com) by setting LOGMARKER="fp=" in /etc/shorewall/shorewall.conf. Note: You may not use ULOG with fireparse unless you modify fireparse. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

...ather than 1.4.3b. Problems Corrected: None. New Features: 1) A REDIRECT-rule target has been added. This target behaves for REDIRECT in the same was as DNAT-does for DNAT in that the Netfilter nat table REDIRECT rule is added but not the companion filter table ACCEPT rule. 2) The LOGMARKER variable has been renamed LOGFORMAT and has been changed to a ''printf'' formatting template which accepts three arguments (the chain name, logging rule number and the disposition). To use LOGFORMAT with fireparse, set it as: LOGFORMAT="fp=%s:%d a=%s " CAUTION:...

http://bugzilla.netfilter.org/show_bug.cgi?id=601 Summary: log messages with flags "ACK PSH FIN" Product: netfilter/iptables Version: unspecified Platform: All OS/Version: Debian GNU/Linux Status: NEW Severity: minor Priority: P3 Component: ip_conntrack AssignedTo: laforge at

Hi, I''ve been successfully using shorewall in our K12 school since the 2.x days initially on Mandrake and now on Debian. Because of that my config has got quite complicated. The firewall has a working MultiISP setup with four interfaces (I''ve renamed them with udev to easy their identification): lan-if, dmz-if, snt-if and dnt-if (one of the providers (the one on dnt-if) is a DSL

Hi, I''m running Slackware 13.37 x86 using Shorewall 4.4.21 with OpenVPN and the VPN options I''m using in Slackware 13.37 will not work in Shorewall, but in Slackware 13.1 using the same Shorewall version and files, the ''interfaces'', ''policy'' and ''zone'', are all I have configured, it was working and this also works in Arch at

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >