Summary

Since installing 21.0-20241023-nightly, apps on my tablet can no longer access Internet when Wireguard is connected. This worked just fine right up until 20241023-nightly, and Wireguard’s app hasn’t been updated in over a year, so I’m pretty sure it’s the new build.

Looks like it’s DNS. (It’s always DNS.) There are a couple of conspicuously related-looking commits in this build: 406071 (VPN-covered DNS traffic may not fall through) and 406070 (Revert ”Prevent DNS traffic from bypassing lockdown VPNs”).

Expected Behavior

Apps should be able to connect to the Internet even when Wireguard is connected.

Current Behavior

Apps lose access to Internet immediately when Wireguard is connected. Curiously, Chrome is unaffected; all other apps that I’ve tested are affected, including Firefox, which says ”Address not found”, hinting at DNS.

Steps to Reproduce

1. Install Wireguard
2. Set up a connection that doesn’t route all traffic but just that interface’s address space. I’m including a screenshot of my Wireguard configuration below.
3. Toggle the Wireguard interface on.
4. Open Firefox and try to browse the web.

Device information

/codename gts4lvwifi /version 21 /date 2024-10-23 /kernel 4.9.337-g16026dfb9b4c #1 Wed Oct 23 13:53:22 UTC 2024 /baseband none /mods Google Apps

I have read the directions