From: Patrick McHardy <kaber@trash.net>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: aggg Re: libnfnetlink_conntrack encapsulation issues
Date: Thu, 27 Jul 2006 16:32:22 +0200 [thread overview]
Message-ID: <44C8CE76.2090500@trash.net> (raw)
In-Reply-To: <44C8CC58.1080909@ufomechanic.net>
Amin Azez wrote:
> * Patrick McHardy wrote, On 27/07/06 15:00:
>
>>it appears the layer7 match does some
>>bad hacks here.
>
> Thats my layer7 stuff.
> I recognize that ifdef's here are no good because the file is used for
> userspace, which doesn't solve the general problem of adding conntrack
> attributes generally (which I've been doing for the last 15 months). The
> current mechanism effectively ensures that this cannot happen (sadly)
One way to add new stuff is to get your patch into the kernel. Other
than that its hard, I agree. ifdefs are not a good idea because
following members don't have a constant value anymore.
>>It looks like a really dumb idea, this will break
>>once we add new attributes. Not sure why a match would need ctnetlink
>>attributes.
>>
>
> Some matches (like layer7) store state which is output via
> /proc/net/ip_conntrack, I also need it as part of conntrack updates.
> I like receiving a conntrack update when the layer7 is detected, for
> instance.
A match shouldn't do that - what kind of state does it store? Can't
you just use your match and combine it with CONNMARK?
> I also output the link layer mac addresses as part of conntrack dumps/
The LL address is not part of the conntrack entry and can change at any
time, so it doesn't belong in ctnetlink.
next prev parent reply other threads:[~2006-07-27 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 10:53 libnfnetlink_conntrack encapsulation issues Amin Azez
2006-07-27 11:04 ` aggg " Amin Azez
2006-07-27 14:00 ` Patrick McHardy
[not found] ` <44C8CC58.1080909@ufomechanic.net>
2006-07-27 14:32 ` Patrick McHardy [this message]
2006-07-27 14:43 ` Amin Azez
2006-07-27 14:59 ` Patrick McHardy
2006-07-27 15:16 ` Amin Azez
2006-07-29 2:11 ` Patrick McHardy
2006-07-28 15:38 ` Pablo Neira Ayuso
2006-07-28 21:13 ` Amin Azez
2006-07-29 10:51 ` Pablo Neira Ayuso
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=44C8CE76.2090500@trash.net \
--to=kaber@trash.net \
--cc=azez@ufomechanic.net \
--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.