Re: nftables: introspection capabilities?

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

 



On Tuesday 2011-05-24 10:21, gapsf@xxxxxxxxx wrote:

>Hi!
>There is a lot of frontends for iptables like shorewall, ufw, ferm and special firewall distros.
>They all are trying to formalize, simplify, integrate the
>configuration of Linux firewall and traffic control subsystems.
>They also use a certain set of metadata for their own use.
>
>One of the iptables disadvantages - the inability to effectively
>find out the internal state of the iptables.
>There is only one way - parse the "iptables -L" output, isn't it?

iptables -S, iptables-save  is preferred at all times.

>There is no doubt that for nftables frontends will be written too, so the question is:
>"Will nfatbles be able to find out various information
>about their own current state: tables, chains, rules, etc?"

You can already obtain this information by using libiptc, iterating over 
all rules and testing for a particular src/dst address (very much like 
poor man's `grep -s 1.2.3.4\b` on the text output).
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[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