Hamachi-gui

I have OpenSuSE 11.2
I installed tuncfg (from opensuse build service) and compat-openssl097g and I got hamachi (hamachi-gui-0.9.6-3.3.i586.rpm) from the OpenSuSE build service (software.opensuse.org: Search Results)

I started tuncfg the first thing and then I started Hamachi. It starts up but it will not do anything. It just says, “Starting Hamachi” and that’s all it does.
For the fun of it, I even tried joining a network to see if that would make it connect but it just crashes.

The gui looks great but I wish it would work. Why is it not connecting?

I do not know what any of the software you speak about is supposed to do, but wile you talk about “connecting”, what about your firewall?

As far as I know, it is not in use. I never activated it on the computer and the router does not seem to have one in use either.

“As far as I know” should not be enough for me. The fact that you did not switch it on does not say much as it is switched on when you did not switched it off either at install or later.
Better check in YaST > Security and uers > Firewall to be sure.

Thanks! I had no idea how to check that.
ok, it does say that the firewall is running.
So, how do I set it to allow Hamachi to start?

For that you must know which ports it uses, which I can not tell you, but it should be in the documentation.

In any case, you could do a test by simply switching off the firewall for a short time and see if your app functions now. That will tell you you are searching in the correct direction for a solution.

And when you have some time left, walk through the different parts of YaST to give you an idea in which areas it can be of any help to you may need arise.

It didn’t work. I even tried filling out the allow list based on this info: Hamachi:Ports and Protocols - LogMeInWiki.com but that did not work either. Samba does not even seem to work.

I even tried starting it from the terminal and this is what I got:


hamachi-gui
Error loading file: /home/<username>/.hamachi-gui.conf
Failed to open hamachi config file at /home/<usernam>/.hamachi/config
fopen(): No such file or directory
connect(): No such file or directory
sh: hamachi: command not found
sh: hamachi: command not found
fopen(): No such file or directory
connect(): No such file or directory
fopen(): No such file or directory
connect(): No such file or directory

I’ve also tried creating the directory(ies) manually and starting it up but that did not work.

As said earlier, I do not know anything about Hamachi, but it seems that it can not function without a proper file* .hamachi-gui.conf *in your home directory.

I do not understand what directories you created. It only asks for that file in your home directory (which I can assume savely that it exists).

I had tried creating the .hamachi-gui.conf and .hamachi directories with a /config subfolder within the .hamachi folder but that did not help.
I’ve also copied over my old .hamachi files from my old SuSE 10.0 but that did not help either.

I still get this:
Error loading file: /home/<username>/.hamachi-gui.conf
connect(): No such file or directory
sh: hamachi: command not found
sh: hamachi: command not found
connect(): No such file or directory
connect(): No such file or directory

Please prove that /home/<username>/.hamachi-gui.conf exists by posting

ls -l .hamachi-gui.conf

from your home directory.
And please put computer output (like the output you posted earlier) between CODE tags (use Go Advanced below right to get a tool bar with the # button in it, select tthe computer text and click the # button). And show it complete including command and prompts. Like mine:

henk@boven:~> ls -l .hamachi-gui.conf
ls: kan geen toegang krijgen tot .hamachi-gui.conf: Bestand of map bestaat niet
henk@boven:~>

ok, here it is:


ls -l .hamachi-gui.conf
total 0

  1. You did somehow succeed in removing the prompt which I asked you NOT to omit and which my example shows.
  2. This proves that your .hamachi-gui.conf is not a file but directory where the error is:
Error loading file: /home/<username>/.hamachi-gui.conf

Mark the word file.

Now I do not know anything about this aplication, I am only trying to interprete what it says and to check if that is correct. When you think that you know better what should be directories, what should be files, what should go where and what should be in there, that can perfectly be true because you have experience with the program and you have the documentation (I hope).

When your problem persists nevertheless, you then better wait (and hope) for another Hamachi user to show up here.

Thanks anyway.
Yes, I hope the hamachi experts might see this.

“sh: hamachi: command not found” - You don’t have the hamachi binary. Hamachi-gui is only a graphical front-end to text-mode-only hamachi.

You can install it by installing http://download.opensuse.org/repositories/home:/etamPL/openSUSE_11.3/noarch/hamachi-0.9.9.9-20.62.1.noarch.rpm (which will automatically download it and install), or download it directly from http://files.hamachi.cc/linux/hamachi-0.9.9.9-20-lnx.tar.gz and install it manually (if you do you just need to untar it and run “sudo install -m 755 hamachi /usr/bin”, because as you said, tuncfg you have already installed from build service).

For the dudes helping on this thread that might not know —

Hamachi is a pretty cool little program. I remember watching about it on techTV 10 years ago.

It allows secure virtual vpn connections to the hamachi clients that are joined up into a group. So i.e. old school
games with lan only multiplayer can be played by people in a hamachi vpn group.

I connects right through hardware firewalls without opening ports. This is what makes it effective for remote access with rdc or
whatever terminal client you need.

The program started out so small and now its the engine that runs “LogMeIn Inc.” which is now a massive corporation around this product.

Funny how these things are. Remembering when it was such a small program back in the 90’s. Now its the leader in this area.

I tried ‘sudo install -m 755 hamachi /usr/bin’ but nothing happens.
So, should I run make install like the README says, or would that mess things up since I have tuncfg installed already?

What do you mean by “nothing happens”? If there’s no output, it’s ok. Try “which hamachi” to check if it’s installed.

Running “make install” will break tuncfg, because the build service version has some patches.

so, ‘which hamachi’ returns /usr/bin/hamachi so it’s there.

But when try ./hamachi-init, I get:
bash: ./hamachi-init: No such file or directory

I’ve even tried it as root too with the same results. I’ve also ran cnf hamachi-init and it can’t find it.

When I try ./hamachi, I get:
“Cannot find configuration directory /root/.hamachi. Have you run ‘hamachi-init’ ?”

This is driving me nuts. I was able to get it to work fine on SuSE 10.0 but it just won’t run for some reason on OpenSuSE 11.2. >:(

Sorry. I forgot about hamachi-init. Run “sudo ln -sf hamachi /usr/bin/hamachi-init”.

And don’t run hamachi as root.

So, I started (as root) tuncfg, then exited so that I wouldn’t be root anymore, then I was able to start hamachi (cd /usr/bin then ./hamachi-init) and then I tried starting Hamachi gui but now, it seems to crash after signing me in.

When I checked the status of hamachi I got:


hamachi
Hamachi, a zero-config virtual private networking utility, ver 0.9.9.9-20

  version  : hamachi-lnx-0.9.9.9-20
  pid      : ****  <-- I took these numbers out
  status   : logged in
  nickname : anonymous

Now, hamachi gui crashes and when I do: hamachi start
it says, Hamachi is already started.

After shutting everything down, I tried it again but this time, I didn’t need to run hamachi-init again (right?)
my steps:

  1. su (give root password) then tuncfg and then exit
  2. cd /usr/bin ./hamachi start
  3. start hamachi-gui (from the kicker menu, then it crashes)

So, when I try the steps again (but this time, I tried starting hamachi-gui from the commandline) I got:


/usr/bin> ./hamachi-gui
Error loading file: /home/<username>/.hamachi-gui.conf
Failed to open hamachi config file at /home/<username>/.hamachi/config
Segmentation fault

Now what do I do? :question: