netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tihomir Katic <tihomir.katic@gmail.com>
To: Pierre Chifflier <chifflier@wzdftpd.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [NEW SOFTWARE] FIRO - Iptables optimization
Date: Thu, 9 Jun 2011 15:39:55 +0200	[thread overview]
Message-ID: <BANLkTim994oFbnN-ef06kUdooaiU9tOJJA@mail.gmail.com> (raw)
In-Reply-To: <20110609133323.GG8745@mail.wzdftpd.net>

Hi Pierre

Thank you

You are right, my mistake with .rar (please use unrar until I change
it on web server)

Makefile should have only
# g++ -o FIRO FIRO.cpp
g++ (GCC) 3.4.6
Copyright (C) 2006

which is pretty old version, I didn't try it with newer...

Br
Tihomir



2011/6/9 Pierre Chifflier <chifflier@wzdftpd.net>:
> On Thu, Jun 09, 2011 at 03:18:38PM +0200, Tihomir Katic wrote:
>> Hi
>>
>> I developed some firewall optimizer for iptables optimization.
>>
>> FIRO is parsing output of iptables-save command and removes redundant
>> rules from it. Rules in each chain and table are optimized separately.
>> Optimization procedure continues until there are no more rules to
>> remove or to modify. As a result, FIRO generates new file with new set
>> of rules for every successful optimization procedure. Also, it logs
>> all actions and changes in separated files.
>>
>> List of optimization procedures:
>>  -  Remove irrelevant rules
>>  -  Remove redundant "shadowed after" rules
>>  -  Remove redundant "shadowed before" rules
>>  -  Remove last rules with same action as chain
>>  -  Merge rules
>>  -  Remove redundant parameters from rules
>>  -  Remove redundant elements from parameters
>>  -  Reposition of "logging" rules in chain
>>
>> This is free software, 1st published version, and I would appreciate
>> every download, every test, every reported bug, suggestion, etc.
>>
>> Link to FIRO:
>> http://valeria.zesoi.fer.hr/~tkatic
>
> Hi,
>
> There are some problems with the download link:
> - as Patrick said, please do not use a rar file, tar.gz is better
> - please package it as a directory (and not unpack all files in current
>  directory)
> - please provide a build system (a Makefile)
>
> There are many build errors:
> CharField.cpp: In destructor ‘cCharField::~cCharField()’:
> CharField.cpp:37:12: error: ‘free’ was not declared in this scope
> ..
> Configuration.cpp: In member function ‘void cConfiguration::LogDebugData(int, std::string)’:
> Configuration.cpp:160:38: error: ‘fopen’ was not declared in this scope.
>
> Pierre
>
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-06-09 13:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 13:18 [NEW SOFTWARE] FIRO - Iptables optimization Tihomir Katic
2011-06-09 13:23 ` Patrick McHardy
2011-06-09 13:33 ` Pierre Chifflier
2011-06-09 13:39   ` Tihomir Katic [this message]
2011-06-09 13:44 ` Jan Engelhardt
2011-06-09 14:07   ` Tihomir Katic
2011-06-09 14:16     ` Jan Engelhardt
2011-06-09 14:23       ` Tihomir Katic
2011-06-09 14:25         ` Tihomir Katic
2011-06-09 14:34         ` Jan Engelhardt
2011-06-09 15:55           ` Tihomir Katic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BANLkTim994oFbnN-ef06kUdooaiU9tOJJA@mail.gmail.com \
    --to=tihomir.katic@gmail.com \
    --cc=chifflier@wzdftpd.net \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).