wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Lane Russell <lanerussell@protonmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Connection issues with Google Fi
Date: Thu, 27 Sep 2018 14:58:03 +0000	[thread overview]
Message-ID: <D6gJBvvJiEjhD6sGH1nVqTjK0phGs51GwYC8Fv6emeVhbYQzru65w-G3uCH7osm1EK1I2t_rsYDfaKJ4EO_8Tm9c6_T8ujEp0bWdVk8Jv2I=@protonmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 641 bytes --]

Using a Nexus 6P on Google Fi, I'm noticing that when roaming between cellular and WiFi, I occasionally lose the ability to use WireGuard. Coming from Verizon, I didn't previously have this issue.

I can only assume this has something to do with Fi manipulating the routing table in such a way that breaks WireGuard connectivity. I verified that WiFi Assitant is disabled. A simple tunnel-up, tunnel-down doesn't seem to fix the issue. Rebooting fixes the issue.

Next time the issue occurs, I can dump the ip rule list, but may need some assistance figuring out which ip tables to pull. Is this the info that will be needed to troubleshoot?

[-- Attachment #1.2: Type: text/html, Size: 712 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2018-09-27 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 14:58 Lane Russell [this message]
2018-09-27 15:48 ` Connection issues with Google Fi Jason A. Donenfeld
2018-09-27 17:23   ` Lane Russell
2018-09-28  4:38     ` Lane Russell
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='D6gJBvvJiEjhD6sGH1nVqTjK0phGs51GwYC8Fv6emeVhbYQzru65w-G3uCH7osm1EK1I2t_rsYDfaKJ4EO_8Tm9c6_T8ujEp0bWdVk8Jv2I=@protonmail.com' \
    --to=lanerussell@protonmail.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).