From: Andreas Messer <andi@bastelmap.de>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Unexpected tcpv6 connection resets since linux 4.4
Date: Wed, 09 Mar 2016 20:12:34 +0100 [thread overview]
Message-ID: <2277643.Q5Ry2PpJQt@proton> (raw)
In-Reply-To: <CAM_iQpXSu_uXCOCtw02EAaOVP_54a1G8pgZrDMTWFEGnSeycJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Mon, Mar 7, 2016 at 15:58, Cong Wang <xiyou.wangcong@gmail.com>wrote:
> On Sun, Mar 6, 2016 at 7:10 AM, Andreas Messer <andi@bastelmap.de> wrote:
> > i have updated two of my machines in the last weeks to linux 4.4.1 and
> > linux 4.4.3. It seems that since then i get unexpected TCPv6 connection
> > resets when connecting to these machines remotely. The issue occurs with
> > sshd and with a http service. /etc/hosts.deny and /etc/hosts.allow are
> > empty on both server machines. I'm not so in IPv6 and have no idea whats
> > going on. Please find attached a network trace from one of the machines
> > when connecting with ssh (on port 23 for debugging).
>
> Sounds like the problem fixed by the following commit:
>
> commit 9cf7490360bf2c46a16b7525f899e4970c5fc144
> Author: Eric Dumazet <edumazet@google.com>
> Date: Tue Feb 2 19:31:12 2016 -0800
>
> tcp: do not drop syn_recv on all icmp reports
Thanks for the tip. I applied the patch to V4,4,1 and it solved the problem.
Cheers,
Andreas
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-03-09 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4875526.tAzumr2zO3@proton>
2016-03-07 23:58 ` Unexpected tcpv6 connection resets since linux 4.4 Cong Wang
2016-03-09 19:12 ` Andreas Messer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2277643.Q5Ry2PpJQt@proton \
--to=andi@bastelmap.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).