From: Willy Tarreau <w@1wt.eu>
To: "Mohandass, Roobesh" <Roobesh_Mohandass@McAfee.com>
Cc: Lukas Tribus <lists@ltri.eu>, Florian Westphal <fw@strlen.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [NETDEV]: getsockopt(fd, SOL_IP, SO_ORIGINAL_DST, sa, &salen) is in fact sometimes returning the source IP instead the destination IP
Date: Wed, 23 Jan 2019 09:54:21 +0100 [thread overview]
Message-ID: <20190123085421.GE19955@1wt.eu> (raw)
In-Reply-To: <MWHPR16MB150280EC34A9D4A8ECF809D4ED990@MWHPR16MB1502.namprd16.prod.outlook.com>
Hi Roobesh,
On Wed, Jan 23, 2019 at 08:07:48AM +0000, Mohandass, Roobesh wrote:
> Hi Willy/Florian/Lukas,
>
> disabling nf_conntrack_tcp_loose (solved the problem) and for last 24 hours,
> we are not evening seeing a single wrong connection data by send-proxy.
>
> Worth a note in your documentation related to this, as users might be aware
> off.
>
> Thanks very much for your help and support, I will report back if I see
> anything again related to this.
Thank you for your feedback on this issue, and kudos to Florian
for spotting the root cause!
Willy
next prev parent reply other threads:[~2019-01-23 8:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MWHPR16MB1502549F7BAAE102EF1D5DF4EDB50@MWHPR16MB1502.namprd16.prod.outlook.com>
[not found] ` <MWHPR16MB150233EF69CFD4562BFA65ABEDB60@MWHPR16MB1502.namprd16.prod.outlook.com>
[not found] ` <MWHPR16MB1502DC55542EBA8121631B16EDB20@MWHPR16MB1502.namprd16.prod.outlook.com>
2018-12-31 6:20 ` : getsockopt(fd, SOL_IP, SO_ORIGINAL_DST, sa, &salen) is in fact sometimes returning the source IP instead the destination IP Mohandass, Roobesh
2019-01-07 11:17 ` Florian Westphal
2019-01-07 14:57 ` Mohandass, Roobesh
2019-01-12 14:37 ` Lukas Tribus
2019-01-12 14:37 ` [NETDEV]: " Lukas Tribus
2019-01-12 16:04 ` : " Florian Westphal
2019-01-12 16:04 ` [NETDEV]: " Florian Westphal
2019-01-12 17:26 ` : " Willy Tarreau
2019-01-12 17:26 ` [NETDEV]: " Willy Tarreau
2019-01-12 18:01 ` : " Lukas Tribus
2019-01-12 18:01 ` [NETDEV]: " Lukas Tribus
2019-01-12 18:33 ` : " Willy Tarreau
2019-01-12 18:33 ` [NETDEV]: " Willy Tarreau
2019-01-17 5:23 ` Mohandass, Roobesh
2019-01-23 8:07 ` Mohandass, Roobesh
2019-01-23 8:54 ` Willy Tarreau [this message]
[not found] ` <MWHPR16MB1502A336CCB4EF3F0FCB69ECEDB20@MWHPR16MB1502.namprd16.prod.outlook.com>
2019-01-07 7:58 ` : " Mohandass, Roobesh
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=20190123085421.GE19955@1wt.eu \
--to=w@1wt.eu \
--cc=Roobesh_Mohandass@McAfee.com \
--cc=fw@strlen.de \
--cc=lists@ltri.eu \
--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).