From: Torsten Luettgert <ml-netfilter@enda.eu>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: TEE broken in 3.6
Date: Wed, 17 Oct 2012 09:45:43 +0200 [thread overview]
Message-ID: <20121017094543.2ddb0397@goldlack.enda.eu> (raw)
In-Reply-To: <1350417618.3954.1494.camel@edumazet-glaptop>
On Tue, 16 Oct 2012 22:00:18 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Could you try latest tree, with the following patch ?
Yeah, that works.
I'm still a bit sad, though, since I'll have to wait for 3.7 now (no
FLOWI_FLAG_KNOWN_NH in 3.6.*), or is there any solution for those "old"
kernels, too?
Regards,
Torsten
next prev parent reply other threads:[~2012-10-17 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 19:13 TEE broken in 3.6 Torsten Luettgert
2012-10-16 20:00 ` Eric Dumazet
2012-10-17 7:45 ` Torsten Luettgert [this message]
2012-10-17 7:48 ` Eric Dumazet
2012-10-17 8:15 ` Pablo Neira Ayuso
2012-10-17 8:33 ` [PATCH] netfilter: xt_TEE: dont use destination address found in header Eric Dumazet
2012-10-17 8:23 ` TEE broken in 3.6 Pablo Neira Ayuso
2012-10-17 8:34 ` Eric Dumazet
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=20121017094543.2ddb0397@goldlack.enda.eu \
--to=ml-netfilter@enda.eu \
--cc=eric.dumazet@gmail.com \
--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).