From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755073AbdESKDw (ORCPT ); Fri, 19 May 2017 06:03:52 -0400 Received: from a.mx.secunet.com ([62.96.220.36]:58564 "EHLO a.mx.secunet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754275AbdESKDu (ORCPT ); Fri, 19 May 2017 06:03:50 -0400 Date: Fri, 19 May 2017 12:03:42 +0200 From: Steffen Klassert To: Don Bowman CC: Cong Wang , "linux-kernel@vger.kernel.org" , Herbert Xu , Linux Kernel Network Developers Subject: Re: ipsec doesn't route TCP with 4.11 kernel Message-ID: <20170519100342.GD22049@secunet.com> References: <20170427084238.GX2649@secunet.com> <20170428071337.GG2649@secunet.com> <20170503081421.GL2649@secunet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Originating-IP: [10.182.7.193] X-G-Data-MailSecurity-for-Exchange-State: 0 X-G-Data-MailSecurity-for-Exchange-Error: 0 X-G-Data-MailSecurity-for-Exchange-Sender: 23 X-G-Data-MailSecurity-for-Exchange-Server: d65e63f7-5c15-413f-8f63-c0d707471c93 X-EXCLAIMER-MD-CONFIG: 2c86f778-e09b-4440-8b15-867914633a10 X-G-Data-MailSecurity-for-Exchange-Guid: 25932A85-C160-46EA-BE08-F0A2A82FA526 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 16, 2017 at 03:05:40PM -0400, Don Bowman wrote: > On 3 May 2017 at 04:14, Steffen Klassert wrote: > > On Sat, Apr 29, 2017 at 08:39:34PM -0400, Don Bowman wrote: > >> On 28 April 2017 at 03:13, Steffen Klassert > >> wrote: > >> > On Thu, Apr 27, 2017 at 06:13:38PM -0400, Don Bowman wrote: > >> >> On 27 April 2017 at 04:42, Steffen Klassert > >> >> wrote: > >> >> > On Wed, Apr 26, 2017 at 10:01:34PM -0700, Cong Wang wrote: > >> >> >> (Cc'ing netdev and IPSec maintainers) > >> >> >> > >> >> >> On Tue, Apr 25, 2017 at 6:08 PM, Don Bowman wrote: > >> >> > >> > >> > >> > >> confirmed, with this patch in place that the tcp functions properly. > > > > Thanks for testing! > > > > I'll make sure to get this fix into the mainline soon. > > Thanks. Let me know if there is any more assistance I can provide. > I've been running the patch for 2 weeks now on 3 machines. Thanks for testing! I plan to push it upstream at the beginning of te next week.