From: Changli Gao <xiaosuo@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables] libxt_length: update to revision 1
Date: Mon, 26 Jul 2010 08:07:33 +0800 [thread overview]
Message-ID: <AANLkTimH8Cd7NooRxNMLSH5aGWVMsCD6MdSrd4mB5A6d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1007251827200.14790@obet.zrqbmnf.qr>
On Mon, Jul 26, 2010 at 12:28 AM, Jan Engelhardt <jengelh@medozas.de> wrote:
> On Saturday 2010-07-24 13:47, Changli Gao wrote:
>
>>On Sat, Jul 24, 2010 at 4:55 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
>>> On Saturday 2010-07-24 06:29, Changli Gao wrote:
>>>
>>>>update libxt_length to revision 1 to support ipv6 jumbo frames.
>>>
>>> You can't just go and change these things, would break xt_length v0.
>>>
>>
>>Hmm. I have updated the patch(attached), but the v0 handlers are not
>>called. Is there anything I missed? Or Is there a bug in iptables?
>
> Probably because you are still breaking the compatibility by editing
> struct xt_length_info.
I am sure it isn't the problem. The kernel module can work with the
old iptables binary. However after I committed the rules with the
revision 1, I can't get the correct output with the command
'iptables-save' or 'iptables -nvL'. I checked the code of iptables,
and found it doesn't check the revision when founding matches and
targets, and even the kernel seems doesn't transfer the revision info
to user space.
> I'd say let's concentrate on rev 2 that I
> submitted.
>
I have seen it. Thanks.
--
Regards,
Changli Gao(xiaosuo@gmail.com)
next prev parent reply other threads:[~2010-07-26 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 4:29 [PATCH iptables] libxt_length: update to revision 1 Changli Gao
2010-07-24 5:28 ` Eric Dumazet
2010-07-24 5:43 ` Changli Gao
2010-07-24 8:55 ` Jan Engelhardt
2010-07-24 11:47 ` Changli Gao
2010-07-25 16:28 ` Jan Engelhardt
2010-07-26 0:07 ` Changli Gao [this message]
2010-07-26 0:21 ` Changli Gao
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=AANLkTimH8Cd7NooRxNMLSH5aGWVMsCD6MdSrd4mB5A6d@mail.gmail.com \
--to=xiaosuo@gmail.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).