From: Florian Westphal <fw@strlen.de>
To: Brandon Cazander <brandon.cazander@multapplied.net>
Cc: Florian Westphal <fw@strlen.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: PROBLEM: TPROXY and DNAT broken (bisected to 079096f103fa)
Date: Fri, 12 Aug 2016 21:03:19 +0200 [thread overview]
Message-ID: <20160812190319.GB25519@breakpoint.cc> (raw)
In-Reply-To: <BL2PR07MB2306C9A7EB393F441D56E7D69E1E0@BL2PR07MB2306.namprd07.prod.outlook.com>
Brandon Cazander <brandon.cazander@multapplied.net> wrote:
> Is there anything I can provide or do to help get this issue fixed? Even with the patch provided, our application is still broken.
[..]
> I think that it is worth doing, as the original kernel change broke my user space program and could do the same to others as well.
>
> On another setup, even with the DIVERT rule in place, I'm still seeing the RST after the ACK. I'm not sure how it is behaving differently than the other setup so I need to look into that. But it definitely worked before the changes to the kernel.
Well, what is different in that setup?
(e.g. rules, application binding different ip address, etc)
Once I can re-create the problem chances for a fix will be a bit
higher...
next prev parent reply other threads:[~2016-08-12 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 18:19 PROBLEM: TPROXY and DNAT broken (bisected to 079096f103fa) Brandon Cazander
2016-07-27 19:01 ` Eric Dumazet
2016-07-28 14:48 ` Florian Westphal
2016-07-29 13:21 ` Florian Westphal
2016-08-02 21:58 ` Brandon Cazander
[not found] ` <BL2PR07MB2306B2B920C441DF5406B1439E050@BL2PR07MB2306.namprd07.prod.outlook.com>
[not found] ` <20160802221121.GB31209@breakpoint.cc>
2016-08-03 15:47 ` Brandon Cazander
2016-08-12 15:35 ` Brandon Cazander
2016-08-12 19:03 ` Florian Westphal [this message]
2016-08-15 16:28 ` Brandon Cazander
2016-09-06 16:41 ` Brandon Cazander
2016-09-06 22:57 ` Florian Westphal
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=20160812190319.GB25519@breakpoint.cc \
--to=fw@strlen.de \
--cc=brandon.cazander@multapplied.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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).