All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Cc: Eric Leblond <eric@inl.fr>
Subject: [RFC] XML output for libnetfilter_conntrack
Date: Tue, 21 Nov 2006 14:58:55 +0100	[thread overview]
Message-ID: <4563061F.4080904@netfilter.org> (raw)

Hi,

I'm about to complete the new API for libnetfilter_conntrack, it
includes the possibility to dump conntrack entries in XML besides of the
classic output similar to the primitive /proc interface. An example of
the XML layout is the following:

/*
 * XML output sample:
 *
 * <conntrack>
 * 	<tuple direction="original">
 * 		<layer3 protonum="2" protoname="ipv4">
 * 			<src>192.168.0.1</src>
 * 			<dst>192.168.0.2</dst>
 * 		</layer3>
 * 		<layer4 protonum="16" protoname"udp">
 * 			<sport>80</sport>
 * 			<dport>56665</dport>
 * 		</layer4>
 * 	</tuple>
 * 	<tuple direction="reply">
 * 		<layer3 protonum="2" protoname="ipv4">
 * 			<src>192.168.0.2</src>
 * 			<dst>192.168.0.1</dst>
 * 		</layer3>
 * 		<layer4 protonum="16" protoname="udp">
 * 			<sport>80</sport>
 * 			<dport>56665</dport>
 * 		</layer4>
 * 	</tuple>
 * 	<meta>
 * 		<protocol>
 * 			<tcp>
 * 				<state>ESTABLISHED</state>
 * 			</tcp>
 * 		</protocol>
 * 		<timeout>100</timeout>
 * 		<status><assured>yes</assured></status>
 * 		<counters direction="original">
 * 			<bytes>10</bytes>
 * 			<packets>1</packets>
 * 		</counters>
 * 		<counters direction="reply">
 *			<bytes>5029</bytes>
 * 			<packets>12</packets>
 * 		</counters>
 * 	</meta>
 * </conntrack>
 */

Comments welcome,

-- 
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris

             reply	other threads:[~2006-11-21 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 13:58 Pablo Neira Ayuso [this message]
2006-11-21 16:01 ` [RFC] XML output for libnetfilter_conntrack Amin Azez
2006-11-21 16:46   ` Amin Azez

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=4563061F.4080904@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=eric@inl.fr \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.