Wouldn't it be better using wireguard at this point. I thought hamachi was long past it's prime.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
After having that same issue with haguichi, I switched to using hamachi in the terminal only and haven't had it happen since.
As for alternatives, I've heard lots of good things about Tailscale (or headscale if you want to self host).
If them connecting to you is an option, WireGuard is also stupidly easy to set up and very reliable. If you need to also forward layer 2 traffic (old LAN games and weird local protocols), you can use OpenVPN for that. A bit hard to set up but also quite capable.
I haven't tried to use hamachi in years so I'm not sure about a solution to your problem. However, I can strongly recommend Zerotier as a potential alternative
+1 Zerotier works awesome
Unfortunately that trace isn't very useful due to the lack of debug symbols. One would have to decompile and analyze the binary to really gather some information as to how that happened, and it's probably against their TOS.
hamachi will occasionally disconnect *and then ask for my password to restart the service. *
The GUI is probably trying to restart the daemon for you which causes this, because that's not standard behaviour. You can probably fix that but just allowing your user to do that passwordless, although it's dumb:
# /etc/polkit-1/rules.d/50-hamachi.rules
polkit.addRule(function (action, subject) {
if (
subject.user === "YOURUSERNAMEHERE"
&& action.id === "org.freedesktop.systemd1.manage-units"
&& action.lookup("unit") === "logmein-hamachi.service"
) {
return polkit.Result.YES;
}
})
You'll want to change your username in there and also adjust the service name if it's different.