From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: nf_inet_address
Date: Thu, 06 Dec 2007 10:54:17 +0100 [thread overview]
Message-ID: <4757C6C9.20002@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0712051828450.10753@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Dec 5 2007 18:24, Jan Engelhardt wrote:
>>> And the name doesn't really match. I'd prefer to type for all of
>>> netfilter and then have conntrack use that one.
>>>
>> About nf_inet_addr; does any userspace program depend on
>> nf_conntrack_address? If so, I would have to add some #defines to remain
>> compat.
>
> Oh and also, if we can actually do that. Because if xt_FOOBAR
> starts using
>
> struct xt_foobar_target_info {
> union nf_inet_addr blubb;
> };
>
> we may not change nf_inet_addr beyond its current size...
> I hope that is ok for this century, given it is already 128 bits.
Thats seems OK.
next prev parent reply other threads:[~2007-12-06 9:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 19:05 NF [PATCH 1/4] xt_owner Jan Engelhardt
2007-11-25 19:06 ` NF [PATCH 2/4] xt_TEE Jan Engelhardt
2007-11-25 19:39 ` Krzysztof Oledzki
2007-11-25 19:55 ` Jan Engelhardt
2007-11-25 20:22 ` Krzysztof Oledzki
2007-11-26 7:24 ` Patrick McHardy
2007-11-26 20:14 ` Jan Engelhardt
2007-11-27 0:12 ` Patrick McHardy
2007-12-05 17:24 ` nf_inet_address (was: NF [PATCH 2/4] xt_TEE) Jan Engelhardt
2007-12-05 17:35 ` Jan Engelhardt
2007-12-06 9:54 ` Patrick McHardy [this message]
2007-11-25 19:06 ` NF [PATCH 3/4] xt_TCPOPTSTRIP Jan Engelhardt
2007-11-26 7:24 ` Patrick McHardy
2007-11-26 16:19 ` Jan Engelhardt
2007-11-26 16:19 ` Patrick McHardy
2007-11-26 16:25 ` Jan Engelhardt
2007-11-27 12:37 ` Patrick McHardy
2007-11-27 14:50 ` Jan Engelhardt
2007-11-27 15:25 ` Patrick McHardy
2007-11-25 19:07 ` NF [PATCH 4/4] xt_gateway Jan Engelhardt
2007-11-26 7:30 ` Patrick McHardy
2007-11-26 9:17 ` Amin Azez
2007-11-26 15:35 ` Patrick McHardy
2007-11-26 16:34 ` Amin Azez
2007-11-27 0:19 ` Patrick McHardy
2007-11-27 9:33 ` Amin Azez
2007-11-27 13:03 ` Patrick McHardy
2007-11-27 13:33 ` Amin Azez
2007-12-03 14:19 ` Jan Engelhardt
2007-12-03 14:23 ` Amin Azez
2007-11-25 19:07 ` IPT [PATCH 1/4] libxt_owner Jan Engelhardt
2007-11-25 19:08 ` IPT [PATCH 2/4] libxt_TEE Jan Engelhardt
2007-11-25 19:08 ` IPT [PATCH 3/4] libxt_TCPOPTSTRIP Jan Engelhardt
2007-11-25 19:08 ` IPT [PATCH 4/4] libxt_gateway Jan Engelhardt
2007-11-26 7:12 ` NF [PATCH 1/4] xt_owner Patrick McHardy
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=4757C6C9.20002@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@vger.kernel.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.