If Wireguard loses its connection, it doesn't automatically requery the host and reconnect AFAIK. So if name resolution fails, or you're on dynamic DNS and the IP changes, it's not going to fix itself.
this post was submitted on 06 Oct 2024
28 points (91.2% liked)
Selfhosted
40219 readers
1152 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Yeah this is why OpenVPN is better for roaming clients in most cases.
Or just use tailscale/headscale/netbird and keep the underlying wireguard performance.
Tailscale in my experience does not run as kernel mode wireguard so performance is not great, but maybe that's changed.
Not sure about Netbird, but the Android app reviews are poor and it does not sound reliable.
And by default, WireGuard doesn't keep the connection alive when there's no traffic. You can tune this in settings, which I've done because I'm behind CGNAT and need a persistent connection.
@just_another_person@lemmy.world the name resolution is not the issue, the ip hasn't changed
Could it be that the domain name has both IPv4 and IPv6 and depending on the network you try to reach one or another? Wireguard can work on both protocols, but from my experience it doesn't try both to see which one works (like browsers do). So if at the first try the dns resolves the "wrong" IP version, wireguard cannot connect and doesn't fallback trying the alternative.
Then try setting PersistentKeepalive on the client
@just_another_person@lemmy.world no, the issue is not keepalive, since it cannot connect in the first place... moving to another wifi (instead of celullar) works fine, so it is not a problem with my configuration.
You might want to put these pertinent details in your post.
If you're on a cellular network that has CGNAT, Wireguard may not be able to work. Same deal if it's an IPv6 network.
@just_another_person@lemmy.world Thanks, but I did
However sometimes (not always) the connection to my home is blocked,
I guess tailscale will have to do
Tailscale is Wireguard. If it works, then something is wrong with your Wireguard configs.
@just_another_person@lemmy.world Tailscale is way more than WireGuard but ok
Friend...Tailscale uses the same Wireguard protocol as everything else. If Tailscale is working, but your solo configs aren't, it's not a Wireguard problem, it's a config problem. Guaranteed.
@just_another_person@lemmy.world
I never said my config is not working, I said sometimes (some cellular connections, but not all) it is not working, that is a huge difference.
I highly recommend you educate yourself a bit https://tailscale.com/compare/wireguard
https://tailscale.com/blog/how-tailscale-works#DERP
TLDR
Tailscale is built on TOP of Wireguard, but has a few goodies that Wireguard doesn't provide.
If you’re just looking for WireGuard with some good support for hostile networks (and easier configuration) I’d probably just recommend Tailscale.
You can run some scripts that will update DNS resolution and reconnect if the connection goes inactive, but those aren't going to be something you likely can do on your phone. (Though, IDK, you might could if we're talking rooted android, but eh, I wouldn't want to rely on it).
Do you know WHY your connection fails? Is it JUST wireguard, is it your whole connection, does the IP change, etc? You might want to setup proper monitoring to see what exactly stops working when Wireguard does to see if it's specific to the service, or if your whole link goes down, or if your router is crashing and rebooting or any number of other problems you could be having.