From: Lane Russell <lanerussell@protonmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Connection issues with Google Fi
Date: Fri, 28 Sep 2018 04:38:57 +0000 [thread overview]
Message-ID: <qKu5swioFkO6-GRUyzeclQ3H7fOed-Uf0Xd4QZRw0pwywVTaZZop9zTIGQ8EBAGGXhSJeTgu3_XSLYgFNaokCvVDSNdkvMr6Y6QiDHme-io=@protonmail.com> (raw)
In-Reply-To: <EHYEPfkFpkfKvezFkP0dpmtlpyl6SuHLqMvOWl8PMZhUJZxGjQTmfbL8YqhxxC4NsvFm7p4N6OFTmfURdPerP5quN0wgmhTSDSBgac-GvS0=@protonmail.com>
Interesting, now that I have a better chance to look at this, I see that the logs show:
Failed to send data packet write udp6 [::]:49896->[2607:7700:0:8::48ca:860f]:51820
This is interesting because the DNS name my client interface is pointed at does not have a AAAA record.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, September 27, 2018 12:23 PM, Lane Russell <lanerussell@protonmail.com> wrote:
> I believe I'm using the userspace implementation. I have stock Android on my Nexus 6P and installed the WireGuard app from Google Play.
>
> I am able to consistently replicate the issue by bringing the WireGuard tunnel up while connected to cellular only, then connecting to WiFi.
>
> Log 1: After bringing up tunnel on cellular, then roaming to Wifi
> https://s3.amazonaws.com/pyrahex-misc/logs/wireguard-log_1_cellular2wifi.txt
>
> Log 2: After connecting to WiFi, I restarted the WireGuard tunnel
> https://s3.amazonaws.com/pyrahex-misc/logs/wireguard-log_2_restart_tunnel.txt
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, September 27, 2018 10:48 AM, Jason A. Donenfeld Jason@zx2c4.com wrote:
>
> > Hi Lane,
> > Are you using the kernel module or the userspace implementation? Can
> > you send a debug log?
> > Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-09-28 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 14:58 Connection issues with Google Fi Lane Russell
2018-09-27 15:48 ` Jason A. Donenfeld
2018-09-27 17:23 ` Lane Russell
2018-09-28 4:38 ` Lane Russell [this message]
2018-09-28 4:43 ` Jason A. Donenfeld
2018-09-28 13:54 ` Lane Russell
2018-10-02 3:07 ` Jason A. Donenfeld
2018-10-02 12:44 ` Lane Russell
[not found] <mailman.1.1538128801.16643.wireguard@lists.zx2c4.com>
2018-09-28 10:09 ` Brian Candler
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='qKu5swioFkO6-GRUyzeclQ3H7fOed-Uf0Xd4QZRw0pwywVTaZZop9zTIGQ8EBAGGXhSJeTgu3_XSLYgFNaokCvVDSNdkvMr6Y6QiDHme-io=@protonmail.com' \
--to=lanerussell@protonmail.com \
--cc=Jason@zx2c4.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).