From: "İbrahim Ercan" <ibrahim.metu@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Is this possible SYN Proxy bug?
Date: Mon, 24 Jun 2019 10:55:07 +0300 [thread overview]
Message-ID: <CAK6Qs9m88cgpFPaVp2qfQsepgtoa02vap1wzkdkgaSuTMm_ELw@mail.gmail.com> (raw)
In-Reply-To: <20190621111021.2nqtvdq3qq2gbfqy@breakpoint.cc>
On Fri, Jun 21, 2019 at 2:10 PM Florian Westphal <fw@strlen.de> wrote:
>
> Yes, something like this is needed, i.e. we need to pass two
> mss values -- one from info->mss ("server") that we need to
> place in the tcp options sent to client and one containing
> the clients mss that we should encode into the cookie.
>
> I think you can pass "u16 client_mssinfo" instead of u16* pointer.
Hi Florian.
We tested fixed code on real environment and we are still getting some
errors. We have a customer using syn proxy in front of a point of sale
(POS) application and they reported that about %0.4 of connections are
erroneous.
When I examine traffic from pcap file, I saw connections opens
successfully but somehow something goes wrong after then.
If we deactivates syn proxy, problem goes away. So we are sure it is
caused by syn proxy.
How can I debug syn proxy further? Do you have any suggestion?
Regards.
next prev parent reply other threads:[~2019-06-24 7:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 10:06 Is this possible SYN Proxy bug? İbrahim Ercan
2019-06-18 10:40 ` Florian Westphal
2019-06-18 11:40 ` İbrahim Ercan
2019-06-18 11:59 ` Florian Westphal
2019-06-18 12:07 ` İbrahim Ercan
2019-06-18 12:40 ` Florian Westphal
2019-06-19 9:26 ` İbrahim Ercan
2019-06-21 7:00 ` İbrahim Ercan
2019-06-21 11:10 ` Florian Westphal
2019-06-24 7:55 ` İbrahim Ercan [this message]
2019-06-24 8:09 ` Fernando Fernandez Mancera
2019-06-24 10:20 ` Florian Westphal
2019-06-24 12:35 ` İbrahim Ercan
2019-06-24 13:32 ` Florian Westphal
[not found] ` <OFD1A8080A.6956CA33-ON0025841D.003AFD98-C125841D.003BC900@notes.na.collabserv.com>
2019-06-18 11:50 ` İbrahim Ercan
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=CAK6Qs9m88cgpFPaVp2qfQsepgtoa02vap1wzkdkgaSuTMm_ELw@mail.gmail.com \
--to=ibrahim.metu@gmail.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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).