Ok so I'm stuck on login failed.

I already did the /sbin fix on tuncfg.c for ifconfig

Do I need to put the path somewhere else in tuncfg.c?

I know this thread is very old, but I'll still post a solution because it's still a problem in Fedora. There's actually a very easy fix:

1. Stop the tuncfg process: su -c 'killall tuncfg' OR sudo killall tuncfg

2. Log on to the root terminal: su -

3. Start tuncfg: tuncfg

4. Create the Hamachi config for the ROOT user: hamachi-init

5. Exit out of the root terminal: exit

6. Create the Hamachi config for the CURRENT user if you haven't already: hamachi-init

7. Use Hamachi!!

If you want to make tuncfg run automatically as root on boot up, then add it to /etc/rc.local: echo "tuncfg" | su -c 'tee -a /etc/rc.local' OR echo "tuncfg" | sudo tee -a /etc/rc.local.

I also had the same problem so thanks for the great post that has allowed me to use hamachi

chris

You're welcome

Still nothing

Everything was going fine with the install until I got to the part where I run hamachi-init. It is nowhere to be find on my computer after running the installation process.

Any ideas what to try next???

try to re-install hamachi, but copy or save the tuncfg.c file which you edited. (or just remember to make the changes again)

just to be clear: it's a very old thread...

Got it!
This is indeed a very old thread but it's still the first hit when you try to google hamachi login failed (i.e. the terminal output)

So, I was trying all I could think of, tap/tun was enabled, tuncfg was running, and Hamachi worked perfectly until last reboot, yet login kept failing

Had a look into /home/<user>/.hamachi and found a .lock file
renamed to .lock.back, tried again, and guess what?
login succeeded.

This may or may not be the problem that the first poster had, but as the thread is still 'alive' and never solved, I thoughht it was a good idea to add what fixed it for me:

if Hamachi suddenly starts failing to login for no apparent reason even tho it did work before, remove or rename the file /home/<user>/.hamachi/.lock

well...
Turns out that simply removing the .lock file doesnt really do the trick. To make it work I have to use hamachi-init -f (force using the directory ~/.hamachi even tho it already exists).
Doing that and then removing the lock usually gets me back on line, but with 2 small problems:

- a new Hamachi IP every time. Kind of a PITA (I have to change a number of scripts)
- all this dang thing has to be done every time I reboot my Linux server. It doesnt happen all that often but still...

Im trying to find out why this happens so I can try to really fix it. None of the hints in this thread helped so far, except from my dirty workaround (with new IP at every use )