Re: ipsec doesn't route TCP with 4.11 kernel

2017-05-19 Thread Steffen Klassert
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 wr

Re: ipsec doesn't route TCP with 4.11 kernel

2017-05-16 Thread Don Bowman
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: >

Re: ipsec doesn't route TCP with 4.11 kernel

2017-05-03 Thread Steffen Klassert
On Fri, Apr 28, 2017 at 09:46:42AM -0700, Eric Dumazet wrote: > On Fri, 2017-04-28 at 09:13 +0200, Steffen Klassert wrote: > > encap type espinudp sport 4500 dport 4500 addr 0.0.0.0 > > > > Ok, this is espinudp. This information was important. > > > This is not a GRO issue as I thought,

Re: ipsec doesn't route TCP with 4.11 kernel

2017-05-03 Thread Steffen Klassert
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 Wan

Re: ipsec doesn't route TCP with 4.11 kernel

2017-04-29 Thread Don Bowman
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,

Re: ipsec doesn't route TCP with 4.11 kernel

2017-04-28 Thread Eric Dumazet
On Fri, 2017-04-28 at 09:13 +0200, Steffen Klassert wrote: > encap type espinudp sport 4500 dport 4500 addr 0.0.0.0 > > Ok, this is espinudp. This information was important. > This is not a GRO issue as I thought, the TX side is already broken. > > Could you please try the patch below?

Re: ipsec doesn't route TCP with 4.11 kernel

2017-04-28 Thread Steffen Klassert
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: > > for 'esp'

Re: ipsec doesn't route TCP with 4.11 kernel

2017-04-27 Thread Don Bowman
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: for 'esp' question, i have ' esp = aes256-sha256-modp1536!' is that what you mean? its

Re: ipsec doesn't route TCP with 4.11 kernel

2017-04-27 Thread Steffen Klassert
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: > > I'm not sure how to describe this. > > > > 4.11rc2 worked, after that, no. We had some recent IPsec GRO changes, this could influence TCP.

Re: ipsec doesn't route TCP with 4.11 kernel

2017-04-26 Thread Cong Wang
(Cc'ing netdev and IPSec maintainers) On Tue, Apr 25, 2017 at 6:08 PM, Don Bowman wrote: > I'm not sure how to describe this. > > 4.11rc2 worked, after that, no. > > My ipsec tunnel comes up ok. ICMP works. UDP works. But TCP, the > sender [which is the ipsec client] does not reach the destinatio