From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 127 - system TFO setting is missing in sysctl.conf
Date: Tue, 29 Jan 2019 12:23:07 +0000 [thread overview]
Message-ID: <3B9320D8-DFFE-4A7E-9089-37FA690CD37F@ipfire.org> (raw)
In-Reply-To: <26592848a7f5da6d867975be4f44699e7f6e902e.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
Hello,
Oh, I have no idea why I missed that patch.
The changes for unbound have been integrated though which is why this is in the change log.
In current next, net.ipv4.tcp_fastopen is already set, so this patch can be marked as merged.
Best,
-Michael
> On 29 Jan 2019, at 09:08, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> Regarding to the Core 127 announcement where it has been outlined that
> the "system is now using TCP fast-open where possible" i wanted to
> report that the regarding patch -->
> https://patchwork.ipfire.org/patch/2001/
> is possibly missing cause the responsible line in sysctl.conf
> net.ipv4.tcp_fastopen = 3
> is after an update to Core 127 not presant.
>
> Best,
>
> Erik
>
prev parent reply other threads:[~2019-01-29 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 9:08 ummeegge
2019-01-29 12:23 ` Michael Tremer [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=3B9320D8-DFFE-4A7E-9089-37FA690CD37F@ipfire.org \
--to=michael.tremer@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