This repository has been archived by the owner on May 26, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 28
set linger to 0 for both inbound and outbound connections #36
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned Stebalien
Apr 4, 2019
Stebalien
added a commit
to libp2p/go-reuseport-transport
that referenced
this pull request
Apr 4, 2019
We should do this from go-tcp-transport (libp2p/go-tcp-transport#36), not here, as setting linger to 0 will cause us to send RST packets instead of nicely closing connections. Also, document why we need the fallback dialer.
vyzo
reviewed
Apr 4, 2019
func tryLinger(conn net.Conn, sec int) { | ||
if lingerConn, ok := conn.(interface { | ||
SetLinger(int) error | ||
}); ok { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a handful, maybe worth naming the linger interface.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bah!
This causes us to send RST packets instead of FIN packets when closing connections and means connections immediately enter the "reset" state instead of entering the TIME-WAIT state. Importantly, this means we can immediately reuse the 5-tuple and reconnect.
vyzo
approved these changes
Apr 4, 2019
anacrolix
approved these changes
Apr 4, 2019
marten-seemann
pushed a commit
to libp2p/go-libp2p
that referenced
this pull request
Apr 26, 2022
We should do this from go-tcp-transport (libp2p/go-tcp-transport#36), not here, as setting linger to 0 will cause us to send RST packets instead of nicely closing connections. Also, document why we need the fallback dialer.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This causes us to send RST packets instead of FIN packets when closing connections and means connections immediately enter the "reset" state instead of entering the TIME-WAIT state.
Importantly, this means we can immediately reuse the 5-tuple and reconnect.
(blocked on a go-reuseport-transport release: libp2p/go-reuseport-transport#14)