From: Jesse Peng <jesse@deansoft.com.tw>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Emmanuel Guiton <emmanuel@netlab.hut.fi>,
netfilter-devel@lists.netfilter.org,
KOVACS Krisztian <hidden@balabit.hu>
Subject: Re: Counter problem in a new nat target.
Date: Thu, 11 Dec 2003 11:20:15 +0800 [thread overview]
Message-ID: <3FD7E26F.2020209@deansoft.com.tw> (raw)
In-Reply-To: Pine.LNX.4.44.0312101514250.10808-100000@filer.marasystems.com
Henrik Nordstrom wrote:
>Making other designs relating conntrack entries with custom data either
>requires abusing one of the existing fields and risk catastrophic results
>if there ever is a conflict with the originally intended use of these
>fields or by building an index outside of the conntrack table which is
>both complex and error prone.
>
>
>
The conntrack->help.Private_connection_helper_info and
conntrack->nat.help.Private_nat_helper supposed not that much accused
been abused.They exist only if you need a helper put his private data,
so once not overlapsed with other helpers(You know the traffic your
helper wants is not what any other helper wants) is for sure, than You
of cource can put your helper data there. I think a helper exist not
stonely if a registered helper exist or even a conntrack->helper exist,
that depends on how you judge the "existence", by soul or by body ;)!
next prev parent reply other threads:[~2003-12-11 3:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 11:53 Counter problem in a new nat target Emmanuel Guiton
2003-12-08 12:28 ` Henrik Nordstrom
2003-12-09 10:01 ` Emmanuel Guiton
2003-12-09 10:15 ` Henrik Nordstrom
2003-12-09 13:48 ` Emmanuel Guiton
2003-12-09 16:16 ` Henrik Nordstrom
2003-12-10 8:35 ` Jesse Peng
2003-12-10 11:00 ` Emmanuel Guiton
2003-12-10 11:15 ` Henrik Nordstrom
2003-12-10 12:52 ` Emmanuel Guiton
2003-12-10 14:19 ` Henrik Nordstrom
2003-12-11 3:20 ` Jesse Peng [this message]
2003-12-11 8:20 ` Henrik Nordstrom
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=3FD7E26F.2020209@deansoft.com.tw \
--to=jesse@deansoft.com.tw \
--cc=emmanuel@netlab.hut.fi \
--cc=hidden@balabit.hu \
--cc=hno@marasystems.com \
--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.