Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1448777 > unrolled thread
| Started by | Jason Baron <jbaron@akamai.com> |
|---|---|
| First post | 2016-07-22 23:10 +0200 |
| Last post | 2016-07-22 23:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: strange Mac OSX RST behavior Jason Baron <jbaron@akamai.com> - 2016-07-22 23:10 +0200
| From | Jason Baron <jbaron@akamai.com> |
|---|---|
| Date | 2016-07-22 23:10 +0200 |
| Subject | Re: strange Mac OSX RST behavior |
| Message-ID | <rXPRL-2CP-9@gated-at.bofh.it> |
Hi, After looking at this further we found that there is actually a rate limit on 'rst' packets sent by OSX on a closed socket. Its set to 250 per second and controlled via: net.inet.icmp.icmplim. Increasing that limit resolves the issue, but the default is apparently 250. Thanks, -Jason On 07/01/2016 02:16 PM, One Thousand Gnomes wrote: >> yes, we do in fact see a POLLRDHUP from the FIN in this case and >> read of zero, but we still have more data to write to the socket, and >> b/c the RST is dropped here, the socket stays in TIME_WAIT until >> things eventually time out... > After the FIN when you send/retransmit your next segment do you then get > a valid RST back from the Mac end? > > Alan
Back to top | Article view | linux.kernel
csiph-web