Bug 2830 - Add option to set TCP_USER_TIMEOUT on linux
Summary: Add option to set TCP_USER_TIMEOUT on linux
Status: NEW
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: 7.6p1
Hardware: Other Linux
: P5 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-01 10:08 AEDT by Julien Wallior
Modified: 2018-02-02 01:15 AEDT (History)
1 user (show)

See Also:

Attachments
Adds support for TCP_USER_TIMEOUT. (11.35 KB, patch)
2018-02-01 10:08 AEDT, Julien Wallior 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Wallior 2018-02-01 10:08:04 AEDT 
Created attachment 3118 [details]
Adds support for TCP_USER_TIMEOUT.

Since 2010, Linux has had a socket option to be able to set a custom timeout of how long a TCP session can stay up if the link drops (default is ~15 set by tcp_retries1/2). https://patchwork.ozlabs.org/patch/62889/

The attached patch lets the user set the TCP_USER_TIMEOUT on both sshd and ssh.
Comment 1 Darren Tucker 2018-02-01 11:57:38 AEDT 
I don't think we want to add support for a platform-specific socket option like this.

On the client side you can implement it as an external ProxyCommand dialer that sets the option and passes the connected socket back via ProxyUseFdpass.
Comment 2 Julien Wallior 2018-02-02 01:15:42 AEDT 
> On the client side you can implement it as an external ProxyCommand
> dialer that sets the option and passes the connected socket back via
> ProxyUseFdpass.
I see how this will work on the client side. This socket option needs to be set on the server side too. Any suggestion how to do that?