Re: [WireGuard] mips32 crash

Hey k, > So , guys, I found where shit lies ! > Crash happens only when l2tp is involved. > I reproduced crash in the following scenario : > > Windows ETH -> ETH Dlink ETH L2TP WG -> WG L2TP ETH Ubuntu Brilliant! Are you able to trigger this with ordinary iperf? Or just CIFS? Are you able to

Re: [WireGuard] mips32 crash

Hey k, Excellent work! My MIPS VM is still alive. :) On Mon, Nov 7, 2016 at 7:54 AM, wrote: > After 10 hours of testing it crashed but another way. > I did mistake. It did not shutdown arm<>mips connection. It was almost > idle but still on. Do you mean to indicate that

Re: [WireGuard] mips32 crash

of k's messages were flagged by spam filters. I'll repost the conversation below in this message. Jason ~=~=~=~= Forwarded conversation Subject: [WireGuard] mips32 crash From: <k...@vodka.home.kg> Date: Sun, Nov 6, 2016 at 9:07 AM To: WireGuard mailing list <

Re: [WireGuard] mips32 crash

> Not a lot of participation from the LEDE package maintainer, so I just > ordered a TL-WR841N for €10, which should arrive on Tuesday, and then > I'll try to reproduce on actual hardware, and in general keep things > rolling well on this platform. So , guys, I found where shit lies ! Crash

Re: [WireGuard] mips32 crash

On Mon, Nov 07, 2016 at 03:06:02AM +0100, Jason A. Donenfeld wrote: > Not a lot of participation from the LEDE package maintainer Well, I only saw one mail from the reporter, so it's difficult to understand your discussion. I haven't run-tested wireguard on an actual router in a while, so there

Re: [WireGuard] mips32 crash

Not a lot of participation from the LEDE package maintainer, so I just ordered a TL-WR841N for €10, which should arrive on Tuesday, and then I'll try to reproduce on actual hardware, and in general keep things rolling well on this platform. ___ WireGuard

Re: [WireGuard] mips32 crash

On Sun, Nov 6, 2016 at 9:07 AM, wrote: >> <4>[13905.634933] Process (pid: 41189632, threadinfo=82bca000, >> task=81ce, tls=8100cea5) > >> Likely caused by memory corruption. > > Look at pid value. Its defenitly not valid pid. Task structure was > corrupted. Indeed.

Re: [WireGuard] mips32 crash

> Wireguard ver 20161103, 20161105 If I understand this right, the one that's crashing is on 1105? In which case, could you tell me if 1103 crashes, or if it's only 1105? ___ WireGuard mailing list WireGuard@lists.zx2c4.com

Re: [WireGuard] mips32 crash

> <7>[13905.531148] wireguard: Sending handshake initiation to peer 1 > (x.x.x.x:16) > <4>[13905.629622] [ cut here ] So you said the crash 100% occurs 100ms after sending handshake initiation. If related this could be because: a) The scheduler ticks come in 100ms

Re: [WireGuard] mips32 crash

Strange, spam filters don't like your domain. Got the message. Analyzing now. Think you could "instrument" where you think the crash happens with a bunch of printks? ___ WireGuard mailing list WireGuard@lists.zx2c4.com