From: Maciej Soltysiak <maciej@soltysiak.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] TCP Fast Open in polipo
Date: Mon, 1 Jun 2015 12:10:00 +0200 [thread overview]
Message-ID: <CAMZR1YBHAeXfpo9-SnhH4EzTdnmp6Hjj83rAVXb0Xrb5vcHNAw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
Hi,
The cerowrt package for polipo has a patch to add support for TFO.
I've moved to openwrt some time ago to see how they are doing and noticed
they are not using the TFO patch.
So I went to polipo github and raised an issue [1] to apply the TFO patch.
Juliusz (the author) asked for a tcpdump to show it actually gives anything.
Before I attempt to generate a tcpdump I thought I ask here.
Does anyone have a tcpdump showing polipo benefits from TFO?
Or can do one easily to support adding this upstream?
Best regards,
Maciej Soltysiak
[1] https://github.com/jech/polipo/issues/62
[-- Attachment #2: Type: text/html, Size: 821 bytes --]
reply other threads:[~2015-06-01 10:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMZR1YBHAeXfpo9-SnhH4EzTdnmp6Hjj83rAVXb0Xrb5vcHNAw@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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