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 tr
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 this crash is the resu
e a lot 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:
Date: Sun, Nov 6, 2016 at 9:07 AM
To: WireGuard mailing list
Hi !
I&#x
> 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 happen
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
c
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
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. In hex, the bottom p
> 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
http://lists.zx2c4.com/mailman
> <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 interva
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
http://lists.zx2c4.com/mailman/list
Wait I noticed this message was a reply to another. I haven't received
the first...
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
http://lists.zx2c4.com/mailman/listinfo/wireguard
Hi k,
Yowza! Any thing else useful in dmesg?
Using that same 20161103 snapshot?
Was it easy to come by or did it occur a bit sporadically? If you can
reliably reproduce, that'd be helpful.
Thanks,
Jason
On Sun, Nov 6, 2016 at 9:07 AM, wrote:
>> <4>[13905.634933] Process (pid: 41189632, thre
> <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.
___
WireGuard mailing list
WireGua
13 matches
Mail list logo
