tech.lgbt is one of the many independent Mastodon servers you can use to participate in the fediverse.
We welcome all marginalized identities. This Mastodon instance is generally for folks who are LGBTQIA+ and Allies with an interest in tech work, academics, or technology in general.

Server stats:

2.9K
active users

Public

@shaknais @bagder you do want the SYN to be retried, just not when you've received an RST indicating the port is closed

Public

@mildsunrise @shaknais Ideally I would avoid the retry of the SYN, like the rest of the world does

@bagder @shaknais I'm not sure I follow... all TCP stacks retry the SYN a few times before timing out, since either the SYN or the SYN/ACK could get lost. in Linux this is controlled by the net.ipv4.tcp_syn_retries sysctl, which defaults to 6

Public

@mildsunrise @shaknais after a RST because nothing is listening?

Public

@bagder @shaknais (see next post)

Public

@bagder @shaknais the thing is that Windows does not abort the process upon receiving an RST. but you do need the retry behavior, otherwise you'd be vulnerable to loss

Public

@mildsunrise @shaknais let me phrase it like this then: I want the Linux behavior on Windows too

Public

@bagder @shaknais exactly. you want the SYN to be retried, but the process to be aborted immediately upon getting an RST. my point is that touching that tweak would alleviate one thing (the wait when the port is closed) at the expense of another (being much more vulnerable to packet loss)