28 ms·
https://www.reddit.com/r/mullvadvpn/comments/15v1cz5/err_network_changed_as_well_as_dns_probe_on/ https://www.reddit.com/r/mullvadvpn/comments/15v1cz5/err_net..
by harshreality 3y ago
https://www.reddit.com/r/mullvadvpn/comments/15v1cz5/err_network_changed_as_well_as_dns_probe_on/ https://www.reddit.com/r/mullvadvpn/comments/15v1cz5/err_net...
Using the official wireguard client allegedly works, but I don't know how they handle ip assignment, which is the complicated part for commercial VPNs like that.
Changing locations sometimes helps.
- lucasyvas 3y agoThis is a great tip, although I don't think that explains why OpenVPN has the same issue on this laptop I'm typing from right now.
- harshreality 3y agoI'd speculate that the problem isn't related to the VPN connection, but to how the Mullvad client app handles the interface (especially if keepalives frequently fail and the interface keeps getting downed). Even the official clean OpenVPN app has its own sense of up and down tunnels, which could cause similar problems. Wireguard, at least in its official linux implementation, is much lighter weight and if necessary reestablishes an active session on demand (whenever there's traffic) without any interface-level tweaks. That's probably invisible to applications, or at least much less visible even if there are low-level syscalls that can inspect the state of a wg tunnel interface.