Summary: | unbound - TCP Fast Open | ||
---|---|---|---|
Product: | IPFire | Reporter: | Erik Kapfer <ummeegge> |
Component: | --- | Assignee: | Erik Kapfer <ummeegge> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Balancing | ||
Priority: | - Unknown - | CC: | michael.tremer |
Version: | 2 | ||
Hardware: | unspecified | ||
OS: | Unspecified |
Description
Erik Kapfer
2018-12-07 15:09:50 UTC
Yes, our kernel should support that. Are there any known downsides? By setting only the configure options TFO is not activated or can be used. There is also the need for a net.ipv4.tcp_fastopen = 3 entry in sysctl.conf but if TFO should be permanent active something like this echo 3 > /proc/sys/net/ipv4/tcp_fastopen in e.g. rc.local --> https://blog.wasin.io/blog/2016/12/26/how-to-enable-fast-tcp-open-on-ubuntu.html is needed too. Some possible problems with an active one can be found in here --> https://tools.ietf.org/html/rfc7413#section-4.2.2 Some improvement tests --> https://reproducingnetworkresearch.wordpress.com/2014/06/03/cs244-14-tcp-fast-open-2/ are also pretty interesting. nginx and haproxy (may more) can also benefit from TFO . Am currently building it and will also go for some testings but wanted to ask if in there is in general interest in it. Best, Erik There is probably more to thinking about --> https://blog.donatas.net/blog/2017/03/09/tfo/ ... I think we should go ahead with this. We can definitely compile in support for TFO into unbound. We can still disable this using the sysctl option. Would you please prepare two patches for this? Yes i can do this am currently building it and will go then for a fast test and if positive i deliver it then to the mailinglist. Best, Erik As far as I am aware this is all built and shipped. If not, please re-open. |