From: "İbrahim Ercan" <ibrahim.metu@gmail.com>
To: Andre Paulsberg-Csibi <Andre.Paulsberg-Csibi@no.ibm.com>
Cc: Florian Westphal <fw@strlen.de>,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org,
netfilter-owner@vger.kernel.org
Subject: Re: Is this possible SYN Proxy bug?
Date: Tue, 18 Jun 2019 14:50:49 +0300 [thread overview]
Message-ID: <CAK6Qs9nUPeGqVG=2vZ-8r9mqUVmCSs3c6wpmTrEfvvX0CGj5Ww@mail.gmail.com> (raw)
In-Reply-To: <OFD1A8080A.6956CA33-ON0025841D.003AFD98-C125841D.003BC900@notes.na.collabserv.com>
On Tue, Jun 18, 2019 at 1:53 PM Andre Paulsberg-Csibi
<Andre.Paulsberg-Csibi@no.ibm.com> wrote:
>
> Maybe a suggestion would be to also have a setting/option where SYNPROXY uses the same MSS as the original packet ?
>
>
As I know, Syn proxy should imitates client and server. To do that, It
should send mss value to client that we set in iptables rule. Same way
it should send mss value to server that what client send already .
These should be default behavior, not an option.
prev parent reply other threads:[~2019-06-18 11:51 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
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 [this message]
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='CAK6Qs9nUPeGqVG=2vZ-8r9mqUVmCSs3c6wpmTrEfvvX0CGj5Ww@mail.gmail.com' \
--to=ibrahim.metu@gmail.com \
--cc=Andre.Paulsberg-Csibi@no.ibm.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter-owner@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).