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 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
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 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 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,
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,
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
> >>
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
On 04/27/2017 06:29 PM, Don Bowman wrote:
> On 26 April 2017 at 15:06, Joseph Salisbury
> wrote:
>> Hi Don,
>>
>> Can you see if this bug started happening in v4.11-rc3? Since your
>> running Ubuntu, a kernel is already available here:
>>
On 04/27/2017 06:29 PM, Don Bowman wrote:
> On 26 April 2017 at 15:06, Joseph Salisbury
> wrote:
>> Hi Don,
>>
>> Can you see if this bug started happening in v4.11-rc3? Since your
>> running Ubuntu, a kernel is already available here:
>> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/
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:
>>
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
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?
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?
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
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'
On 26 April 2017 at 15:06, Joseph Salisbury
wrote:
> Hi Don,
>
> Can you see if this bug started happening in v4.11-rc3? Since your
> running Ubuntu, a kernel is already available here:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/
It appears I was
On 26 April 2017 at 15:06, Joseph Salisbury
wrote:
> Hi Don,
>
> Can you see if this bug started happening in v4.11-rc3? Since your
> running Ubuntu, a kernel is already available here:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/
It appears I was incorrect about where this was
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 =
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?
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
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
(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
(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
Hi Don,
Can you see if this bug started happening in v4.11-rc3? Since your
running Ubuntu, a kernel is already available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/
If v4.11-rc2 is good and -rc3 is bad, I can help you bisect between the two.
Thanks,
Joe
On 04/25/2017
Hi Don,
Can you see if this bug started happening in v4.11-rc3? Since your
running Ubuntu, a kernel is already available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/
If v4.11-rc2 is good and -rc3 is bad, I can help you bisect between the two.
Thanks,
Joe
On 04/25/2017
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 destination.
Its not a routing rule issue (since ICMP/UDP work).
Its not a traffic selector just selecting
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 destination.
Its not a routing rule issue (since ICMP/UDP work).
Its not a traffic selector just selecting
28 matches
Mail list logo