From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sysctl.conf: Enable TFO in sysctl
Date: Fri, 14 Dec 2018 17:41:09 +0100 [thread overview]
Message-ID: <294b888432b1f1657b4d47af48bb8dd638f54cbc.camel@ipfire.org> (raw)
In-Reply-To: <E897BFB1-E72F-4833-B252-86D37BE87F39@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
Hi Michael,
Am Freitag, den 14.12.2018, 14:59 +0000 schrieb Michael Tremer:
> Hi,
>
> > On 14 Dec 2018, at 12:03, erik.kapfer <ummeegge(a)ipfire.org> wrote:
> >
> > Fixes #11945
> >
> > This do not enables TFO support in general there is still the
> > execution of
> > echo 3 > /proc/sys/net/ipv4/tcp_fastopen
> > needed after every reboot (rc.local e.g.).
> >
>
> Why does this not enable it? Setting that value to 3 is what the
> sysctl command does.
>
> I am confused.
you are right, mixed there testings up but used also old descriptions.
There is no need to echo '3' to tcp_fastopen to survive reboots.
Should i amend the patch and correct the commit message ?
Did now some tests with OpenSSL-1.1.1a whereby unbound includes the TFO
configure options and DoT seems *really* much faster then DoT on
another system without TFO support for unbound and OpenSSL-1.1.0i but
am currently not able to find some TFO usage evidence except the TFO
key
$ cat /proc/sys/net/ipv4/tcp_fastopen_key
750532b8-36e6eb1d-800cb58e-3008f1f1
Monitoring examples like in here -->
https://blog.wasin.io/blog/2016/12/26/how-to-enable-fast-tcp-open-on-ubuntu.html
didn´t deliver any results but they are also old
(echo 3 > /proc/sys/net/ipv4/tcp_fastopen) is in this description
also included which is outdated, possibly the monitoring examples are too.
Best,
Erik
next prev parent reply other threads:[~2018-12-14 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 12:03 erik.kapfer
2018-12-14 14:59 ` Michael Tremer
2018-12-14 16:41 ` ummeegge [this message]
2018-12-14 16:54 ` [PATCH v2] " erik.kapfer
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=294b888432b1f1657b4d47af48bb8dd638f54cbc.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.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