#Hamachi

After getting the Hamachi 2 update (without a prior notice, nicely done… No more auto update if they continue to break stuff) I started to notice a bunch of XPs receiving this error after a reboot: Failed to connect to the engine.

Hamachi is auto started, at boot, because we have a shortcut in the startup folder. No other way to auto start the free version (as far as I know).

I wrote before, that the console version of Hamachi didn’t seem to generate tun/tap driver errors. But after rebooting my Mac I was no longer able to start Hamachi.

Nazgul:hamachi-0.9.9.9-20-osx yeri$ ./hamachi start
25 19:08:15.659 [   0] [14306] tap: connect() failed 2 (No such file or directory)

So I guess I’ll have to wait for a fix after all. :(

When playing with KisMAC, I noticed something weird in my /var/log/system.log;

$date com.apple.launchd[1] (tuncfgd$pid) posix_spawnp("/usr/sbin/tuncfg", ...):
No such file or directory
$date com.apple.launchd[1] (tuncfgd$pid) Exited with exit code: 1
$date com.apple.launchd[1] (tuncfgd) Throttling respawn: Will start in 10 seconds

tun is (trying) to restart every 10 (!) seconds. I tried updating Hamachi’s tun/tap drivers, without any success. It kept restarting the process every 10 seconds.

After a bit of Googling, it seemed to be a known problem. So I decided to uninstall Hamachi & the tun/tap drivers.