I am working on a hamachi arm port for my NAS. It is done, but when I try to login, it says just Logging in .. for a long time... My RPi with the same binary Can connect to the server withoutany issues.

At the debugger log of the hamachid, I Can only see the following lines:

------------------
Mod: compare this output with the RPi's output, I think the problem is related with the first line, with the resolving... But why the hamachi daemon wants to resolve a simple IP address?
------------------

I have already done something similar, except the last line, which does the forwarding. I tried it, but unfortunately not helped. I think, there is another error. Otherwise (if the issue is module related) the interface ham0 Cannot be created. So there is another error I think...

Interesting! I decided to start the process from the scratch and secondly start the hamachid by hands.

So, firstly, I rebooted the box. After it, I loaded the /ffp/lib/modules/2.6.31.8/kernel/drivers/net/tun.ko module with the insmod command and created the device node with the correct permissions. And finally, tried to start the daemon with debugger console. When I executed it at the first time, it returned blank and exited. No idea, why... But secondly, it started, with a successful handshake with the server. So looked like perfect, but while, I tried to intercept the debugged daemon, and start the normal one, every time, when I pressed Ctrl+C, the console only gave me a ^C.... And I Can't kill it of course. Like in case of the new openvpn... Barmalej, Do You remember, what was Your solution at the past? If I clearly remember, it caused, because the NSA320S kernel has auto module loading function...

Firstly, I simply created the device node, fixed the permissions, etc. After that, I tried to start the hamachid. As expected, it gives exactly the same output, than at my past tries. But after the devnode creation, I Could't see the tun module at the lsmod output. So, I tried to load the fw tun.ko with insmod. Now, I saw the tun module at the lsmod. So test round two! But unfortunately it gives me exactly the same output as the first try did...

However if I load the 'with FFp comes' tun.ko, I Can see the daemon Can start up correctly, the only one problem is, it always freezes at this statement. So I Can't use it.

Barmalej, if I send You a testing hamachi package, would You mind testing it on Your NSA310?

PS: I tried to execute the openvpn start script first with debug suffix and intercept that (So the script loads the module, but the oVPN kills) and after that run hamachid, but stuck on logging in....

Sorry I forgot to write that. So, there is an included profile.d script, who executes some aliases for the daemon to make it FFp friendly. But the profile.d scripts only have been executed, if You give it execute permission, and at the first time You have to relog, or use the source command to run the script.

. It will tell the daemon to connect to the hamachi server. Well, the login calling is wrong, I think... Because it realy does a hamachi server and NAS opposite handshake and a connection.

And when it successfully established the connection, You will see an online state, but You haven't got a client id and a Username, because You have to create a new network at the hamachi's website (https://vpn.net), or there is another option to join to an exist network. See the help (hamachi -h).

PS: I already know, You are a magician, but I didn't thought, You are a time traveller too. Or it is just the hamachid daemons output?

Bypass obvious things MrDini. Actually I am using original source, because you didn't included dns setup scripts in your package and intentionally not changing paths. This is not ffp native binary, so they might be hardcoded. What I need to know is how and what I have to configure.
Btw. You can see that server is already logging:

Finally create a new network at the Logmein page, that I linked (after a login certainly). Make sure, You didn't set a password for the joining! If I set a password, I Cannot connect to it with the Pi. And after that, replace your network ID at this command: