From: "Maciej Żenczykowski" <zenczykowski@gmail.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
Linux NetDev <netdev@vger.kernel.org>,
Netfilter Development Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] doc: document danger of applying REJECT to INVALID CTs
Date: Sat, 9 May 2020 14:28:55 -0700 [thread overview]
Message-ID: <CANP3RGe3fnCwj5NUxKu4VDcw=_95yNkCiC2Y4L9otJS1Hnyd-g@mail.gmail.com> (raw)
In-Reply-To: <20200509211744.8363-1-jengelh@inai.de>
I *think* that your talk of 3 packets is not needed, ie. the initial
delayed packet doesn't have to be a retransmission.
It can be the first copy of that segment that gets massively delayed
and arrives late and causes problems,
by virtue of arriving after the retransmission already caused the
connection to move on.
Other than that this does seem perhaps a bit cleared than what I wrote.
next prev parent reply other threads:[~2020-05-09 21:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 5:22 [PATCH] document danger of '-j REJECT'ing of '-m state INVALID' packets Maciej Żenczykowski
2020-05-09 10:52 ` Jan Engelhardt
2020-05-09 17:45 ` Maciej Żenczykowski
2020-05-09 18:02 ` Maciej Żenczykowski
2020-05-09 21:17 ` [PATCH] doc: document danger of applying REJECT to INVALID CTs Jan Engelhardt
2020-05-09 21:28 ` Maciej Żenczykowski [this message]
2020-05-09 21:31 ` Maciej Żenczykowski
2020-05-12 21:00 ` [PATCH v2] " Jan Engelhardt
2020-05-12 21:25 ` Maciej Żenczykowski
2020-05-13 4:39 ` Benjamin Poirier
2020-05-13 9:17 ` [PATCH v3] " Jan Engelhardt
2020-05-13 9:28 ` Maciej Żenczykowski
2020-05-13 9:39 ` [PATCH v4] " Jan Engelhardt
2020-05-13 16:29 ` Maciej Żenczykowski
2020-06-03 13:36 [PATCH] " Jan Engelhardt
2020-06-07 22:30 ` Pablo Neira Ayuso
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='CANP3RGe3fnCwj5NUxKu4VDcw=_95yNkCiC2Y4L9otJS1Hnyd-g@mail.gmail.com' \
--to=zenczykowski@gmail.com \
--cc=fw@strlen.de \
--cc=jengelh@inai.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).