Re: iptables analyzer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Heh what about people who run iptables from a script... like me?


--- "Earl A.Killian" <netfilter@xxxxxxxxxxxxxxxxx> wrote:
> Actually I'm planning something static, independent of the traffic
> received by the host.
> 
> Basically, it would take iptables-save output and make a list of all the
> * protocols used (the -p's)
> * the src addresses used (the -s's)
> * the dst addresses used (the -d's)
> * the src ports used (the --sport's)
> * the dst ports used (the --dport's)
> * the input interfaces used (the -i's)
> * the output interfaces used (the -o's)
> * the --icmp-types used
> then augment each of the above lists with an "other" entry, and then
> and then simulate every combination of the above and
> * the 4 conntrack states
> * the possible ip flags (-f)
> * the possible tcp flags
> against the rules, and print a table of the final target (ACCEPT or
> DROP).
> 
> The output would be big, but some intelligent pruning (use of '*' to
> merge multiple rows when possible) should make it more manageable.
> 
> One use is to simply have paranoid humans review the output.
> Another use is to run it on two different iptable rule sets and
> compare what's different (e.g. if you reorder rules for efficiency,
> this would check that you haven't inadvertently changed the firewall
> semantics).


=====
In the absence of order there will be chaos.

__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux