From: Kristian Evensen <kristian.evensen@gmail.com>
To: Cong Wang <cwang@twopensource.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] tcp: Add TCP_FREEZE socket option
Date: Wed, 22 Oct 2014 19:11:30 +0200 [thread overview]
Message-ID: <CAKfDRXiOQK2Mc=OS26Pox-bpsca74uStm4RB5o5jKkhkD6d_5A@mail.gmail.com> (raw)
In-Reply-To: <CAHA+R7OTmmeUf=_LaN1_isL1ZKiqcS0pYE0eKpRbPhaPeX-2jQ@mail.gmail.com>
Hi,
On Wed, Oct 22, 2014 at 6:56 PM, Cong Wang <cwang@twopensource.com> wrote:
> At least split TCP is transparent to applications, while your approach is not.
> I don't understand why you said it typically operates on some ports, since
> TCP is stateful.
I see that I might have used the wrong word here. I am use to calling
them TCP splitters, but I see that the devices are also referred to as
transparent TCP proxies. Anyhow, they are still transparent, but they
violate end-to-end (even though I guess that is pretty common
now-a-days).
What I mean by the port-comment is that only connections to some ports
are proxied/split. For example, one of the operators in Norway only
proxy port 80, so any HTTPS transfer risk getting stuck after a
temporary disconnect.
-Kristian
prev parent reply other threads:[~2014-10-22 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 15:36 [PATCH net-next] tcp: Add TCP_FREEZE socket option Kristian Evensen
2014-10-22 15:54 ` Eric Dumazet
2014-10-22 16:10 ` Kristian Evensen
2014-10-22 16:14 ` David Miller
2014-10-22 17:08 ` Kristian Evensen
2014-10-22 19:50 ` Hagen Paul Pfeifer
2014-10-22 20:33 ` Kristian Evensen
2014-10-24 14:58 ` Yuchung Cheng
2014-10-24 16:26 ` Hagen Paul Pfeifer
2014-10-25 21:29 ` Kristian Evensen
2014-10-25 21:21 ` Kristian Evensen
2014-10-22 16:56 ` Cong Wang
2014-10-22 17:11 ` Kristian Evensen [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='CAKfDRXiOQK2Mc=OS26Pox-bpsca74uStm4RB5o5jKkhkD6d_5A@mail.gmail.com' \
--to=kristian.evensen@gmail.com \
--cc=cwang@twopensource.com \
--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).