wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Reuben Lifshay <rlifshay@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard Android app stops working on Chrome OS after suspend
Date: Wed, 3 Nov 2021 11:07:47 -0700	[thread overview]
Message-ID: <CABip9K7zAJKQR__Hj-X9-NxrgG-fw4mxW2dPn1K-MMeAMnSHXA@mail.gmail.com> (raw)
In-Reply-To: <CABip9K7f3AKBG9WuJ5_u0n7ExCXKjvdGiy-6YEe8TLzTu0Ezqg@mail.gmail.com>

I've had the Wireguard Android app on my chromebook for awhile and
it's seemed to work just fine. Recently I've started using it more
though, and I discovered that if I closed the lid of my chromebook for
a few minutes or if I let it go to sleep that I can no longer get any
of my tunnels to work. Toggling the tunnels and/or wifi does not fix
it, nor does force stopping the wireguard app. I have to do a full
reboot to get things working correctly again.

I did some debugging and discovered that the wireguard packets were
still being sent to and received by the remote server, but there was
something incorrect about them because they never appeared on the
corresponding wireguard interface on the server. I didn't see anything
that stood out in the app debug log either. After some searching I
found a reddit post where someone discovered that if they downgraded
to version 1.0.20210506 that the issue went away. I didn't try that
myself yet because I don't really want to enable dev mode to allow
sideloading apps right now.

I can enable debug mode for wireguard on one of my servers to get more
info if it would be helpful, but have yet to do so.

Here's a link to the reddit post:
https://www.reddit.com/r/chromeos/comments/q0lbnl/network_troubles_after_version_93_update/

Reuben

           reply	other threads:[~2021-11-03 18:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CABip9K7f3AKBG9WuJ5_u0n7ExCXKjvdGiy-6YEe8TLzTu0Ezqg@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABip9K7zAJKQR__Hj-X9-NxrgG-fw4mxW2dPn1K-MMeAMnSHXA@mail.gmail.com \
    --to=rlifshay@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).