Re: routing table doesn't report wireguard routes

Turns out, I didn't understand quite how the routing table works in Linux. Here is a good high-level description of how this works: (thanks to wurtel over at stackexhange: https://unix.stackexchange.com/questions/188584/which-order-is-the-route-table-analyzed-in )

routing table doesn't report wireguard routes

Ubuntu 16.04.4 LTS Currently, WireGuard's routes don't seem to show up in the routing table, at least as viewed via "route -n" and "netstat -rn". Is this an issue, or am I misunderstanding the mechanism WireGuard uses to route traffic? In my case, the client config has "AllowedIPs = 0.0.0.0/0",

Connection issues with Google Fi

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

Re: Connection issues with Google Fi

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

Re: Connection issues with Google Fi

Installed the new release and tried roaming from Fi service to WiFi, all appears to be working as expected. Thanks for following up! ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: Connection issues with Google Fi

ent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, September 27, 2018 12:23 PM, Lane Russell 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 consist

Re: Connection issues with Google Fi

Ah, thanks for your help! I'll be off to learn about XLAT/CLAT. ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard

Configure WireGuard for Roaming Between IPv4, IPv6

What is the best practice for configuring Wireguard to work over diverse networks, including IPv4-only, IPv6-only, and dual-stack? For example, my current configuration only deals with IPv4. When I roam from an IPv4-only network to a dual-stack, my device routes IPv4 traffic over the WireGuard

WireGuard behaviour with systemd-resolved

I've noticed some concerning behaviour using WireGuard on Manjaro GNOME. When the WireGuard interface is brought up, the system starts using the DNS servers provided in the wg-client.conf file. Intermittently however, internal DNS records will resolve using their public IP addresses. Using

Re: WireGuard behaviour with systemd-resolved

I'm not sure of the proper way to resolve this issue with systemd-resolved, but I was able to get to a more comfortable position in my case by disabling systemd-resolved and manually configuring my DNS servers in /etc/resolv.conf. Since the machine in question always sends all traffic over the

Re: Configure WireGuard for Roaming Between IPv4, IPv6

Høiland-Jørgensen wrote: > Lane Russell writes: > >> Thanks so much for setting me straight. I've gotten IPv6 working over >> my IPv4 tunnels to ensure that IPv6 traffic can't leak out while I'm >> using Wireguard. Since my ISP uses SLAAC to hand out /56s, I have a >> /