Can't log in with hamachi.
 

hi. Im trying to get a program named hamachi working. I got it installed but whenever i try to login the login fails. I've started it with the debug flag and this is what i get when trying to login.

i've searched on google, on the hamachi support forum, etc, but still not sure what the problem is. I hope someone here is familar with it to help. Thanks for any help in advance. I appreciate it.

login with hamachi
 

I'm far from being an expert, but what strikes me right off is the line that says 'tap configuration failed'. In my experience, you have to log into the console as root and run 'tuncfg', then logout of the root console and start hamachi.
My biggest problem was with the Linux GUI, it won't repaint and it freezes and won't work for me. Maybe we'll get to the bottom of these problems soon.:twocents:

thanks for your response. i can't login even with tunecfg running. i've tried running tuncfg -d to get debug info but it just hangs. The weird thing is when i first installed it on my laptop i was able to start it up and login right off the bat. But now i can't login on the laptop either. I noticed that when i was logged in on the laptop i had ham0 in the output of ifconfig. I've never had it on the desktop (haven't successfully logged in once) So my guess is the problem is when i tries to setup ham0.

can't log in with hamachi
 

I think your problem is probably spelled out right here. It seems to be pointing to tun/tap. If you could post this snippet on the hamachi forum, you'll probably get a response pretty soon.:study:

29 11:28:18.691 [ 4784] tap: bad response 00007f00
29 11:28:18.691 [ 4784] ses: state 5.1 -> 7.0
29 11:28:18.691 [ 4784] ses: udp sock -- 192.168.0.2:32777
29 11:28:18.691 [ 4784] ses: sending discovery
29 11:28:24.794 [ 4784] ses: state 7.0 -> 7.1
29 11:28:24.794 [ 4784] ses: received disc.ok
29 11:28:24.794 [ 4784] ses: state 7.1 -> 8.0
29 11:28:24.794 [ 4784] ses: tap configuration failed
29 11:28:24.794 [ 4784] ses: error 8 0 1

i've posted the whole thing at the hamachi forum. so far i have got one response there from what i believe is a developer to post the output of tuncfg -d but that command just hangs on both my desktop and laptop. thanks for your response.

It appears the network is down
http://forums.hamachi.cc/viewtopic.php?t=5052

FWIW I can not log in to the network either and I have it failing at sending helo...

thanks. So that explains why i could log in on my laptop that one time, the server must have been up. And explains how it could suddenly stop working.

hmmm. I checked the annoucements to see if the server is down again and it isn't but i still can't log in. I think im going to give up on hamachi and try ssh tunneling. Hamachi sounds like it would be a nice program if i could get it to work. oh well.

I had this same problem.
 

I had the exact same problem, and it turned out the when I ran tuncfg it wasn't completing
correctly. Run 'tuncfg -d' to see what is happening. In my case, it couldn't find ifconfig
and adding /sbin to my path fixed the problem. Hope this helps.

Lehonti

You must have /sbin to your path when running tuncfg.

Tuncfg is looking for "ifconfig" and if it don't find it you will have tap problem.

hi! my tuncfg -d does not return any information...

i've added /sbin to my path and if i run as user ifconfig i receive this...

i'm still trying to figure out what is not working...

hamachi start returns...

any help is very much appreciated!!!

I had the same problem. Took me a while to figure it all out with the help of the previous posts. I assume that all was installed properly and you already run hamachi-init as the current user. I use Fedora Core 6 which doesn't allow running programs in the /sbin folder without specifying the folder.

You should be in the folder where you unpacked hamachi and into the tuncfg folder, which in my case was:

/tmp/hamachi-0.9.9.9-20-lnx/tuncfg/

Next, rename the original tuncfg file in that folder (only if you need to)

mv tuncfg tuncfg.backup

Next, use your choice of text editor to edit the tuncfg.c file. Search for the piece of code that has ifconfig. There is only one instance of that.

Change:
"ifconfig %s %u.%u.%u.%u ", ctx[i].dev,

To:
"/sbin/ifconfig %s %u.%u.%u.%u ", ctx[i].dev,

Then:
"gcc tuncfg.c -o tuncfg"

That recompiles tuncfg to incorporate the changes you made.

Next, if you had already started tuncfg, kill all instances of tuncfg with

"killall tuncfg"

Next, run "make install" as root to install the new tuncfg

Next, Run "tuncfg" as root

Next, run "hamachi start" as a regular user and you may proceed as indicated in the README file.

feistyfeline, thank you.
This redhat 'particularity' just keeps getting on the way...
I didn't spend much time on it but, if someone has an easy way to include the damned /sbin/ dir into the root's path automatically, that would really be a feature to put as default...
Thanks a lot for that great single post :)

I'd also like to add my thanks for a great solution to an irritating problem. thank you very much for your help
netsurf

fedora core 8 still has the same problem
 

I think this is something that happens with every version of fedora.

I was using fedora core 6 and got the error

I'm upgrading now to fedora core 8 and I still have to go through updating tuncfg.c with gcc.

I tried an rpm that was on pbone and the rest of the web and those rpms don't work.

The only way to get past this Logging in...failed error is to be able to update the /sbin path for tuncfg

I hope someone could just create an rpm for fedora with hamachi that would just work and resolve all these issues

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.

nice
 

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

Can't find hamachi-init
 

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 :( )