netdev - Re: : getsockopt(fd, SOL_IP, SO_ORIGINAL_DST, sa, &salen) is in fact sometimes returning the source IP instead the destination IP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 23 Jan 2019 09:54:21 +0100
From:   Willy Tarreau <w@....eu>
To:     "Mohandass, Roobesh" <Roobesh_Mohandass@...fee.com>
Cc:     Lukas Tribus <lists@...i.eu>, Florian Westphal <fw@...len.de>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: : getsockopt(fd, SOL_IP, SO_ORIGINAL_DST, sa, &salen) is
 in fact sometimes returning the source IP instead the destination IP

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