From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Cc: Eric Leblond <eric@inl.fr>
Subject: Re: [RFC] XML output for libnetfilter_conntrack
Date: Tue, 21 Nov 2006 16:46:22 +0000 [thread overview]
Message-ID: <45632D5E.2020102@ufomechanic.net> (raw)
In-Reply-To: <456322E6.4070901@ufomechanic.net>
* Amin Azez wrote, On 21/11/06 16:01:
> I suggest an alternative compact version from which greater verboseness
> might be justified.
>
> <conntrack status="ASSURED" timeout="100">
> <flow direction="original" | <original
> packets="1" bytes="10">
> <layer2 number="0" name="eth" vlan="2"
> src="00:00:00:00:00:00" dst="00:00:00:00:00:00"/>
> <layer3 number="2" name="ipv4" src="192.168.0.1" dst="92.1.0.253"/>
> <layer4 number="16" name="udp" src="53" dst="53"/>
> </flow> | </original>
> <flow direction="reply" | <reply
> ... etc
> </flow> | </reply>
> </conntrack>
>
> I realise that layer2 isn't part of the main conntrack but it is part of
> my conntrack, so I put it in there. I guess at name and number for layer2.
>
> Maybe sport and dport should be used for L4 and not src and dst again...??
We should include a timestamp and (short-term-unique) conntrack-id in
that, and maybe even a created time if we keep it (I can't remember now):
<conntrack ctid="1378654" created="102837453" time="102837459"
timeout="100" status="ASSUERED">
Sam
prev parent reply other threads:[~2006-11-21 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 13:58 [RFC] XML output for libnetfilter_conntrack Pablo Neira Ayuso
2006-11-21 16:01 ` Amin Azez
2006-11-21 16:46 ` Amin Azez [this message]
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=45632D5E.2020102@ufomechanic.net \
--to=azez@ufomechanic.net \
--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.