Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1448777

Re: strange Mac OSX RST behavior

Path csiph.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod
From Jason Baron <jbaron@akamai.com>
Newsgroups linux.kernel
Subject Re: strange Mac OSX RST behavior
Date Fri, 22 Jul 2016 23:10:01 +0200
Message-ID <rXPRL-2CP-9@gated-at.bofh.it> (permalink)
References <rQ8yd-8iZ-3@gated-at.bofh.it> <rQagG-WO-43@gated-at.bofh.it> <rQagG-WO-41@gated-at.bofh.it> <rQbcK-1vP-5@gated-at.bofh.it>
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1469221708; bh=NEz3Wqzp2wjr38hnrIb96GybuGDQTCz/ARnFmSz8meg=; l=728; h=To:References:CC:From:Date:In-Reply-To:From; b=nlhr0fJ+g7pu81iQtlJ1FVSiNvesp/9/xvZig5LVPie9FpLCpTrCDuOMqQ+QrbtxS OYRd5ryYSE2GHuohIG2JXUM7yp6vfO2f6nbc3O6g4EEtU9qDKWeRHaLzXmrVWDfQ9s +nuF+jzQwQTzoTA8vYW+VDaIFBnkzkilOT8nokMI=
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version 1.0
Content-Type text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding 7bit
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 21
Organization linux.* mail to news gateway
X-Original-Cc Rick Jones <rick.jones2@hpe.com>, <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>, <davem@davemloft.net>, <eric.dumazet@gmail.com>
X-Original-Date Fri, 22 Jul 2016 17:08:27 -0400
X-Original-Message-ID <d2aefee2-b11d-b93e-d3ad-6b4202bc7852@akamai.com>
X-Original-References <1467385815-6357-1-git-send-email-jbaron@akamai.com> <5776A3A4.8000503@hpe.com> <5776A607.70800@akamai.com> <20160701191609.1fc1c045@lxorguk.ukuu.org.uk>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1448777

Show key headers only | View raw


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 linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

Re: strange Mac OSX RST behavior Jason Baron <jbaron@akamai.com> - 2016-07-22 23:10 +0200

csiph-web