cancel
Showing results for 
Search instead for 
Did you mean: 
Active Contributor

Re: Ubuntu 17.10 hamachid crashes on login (glibc 2.26)

I cannot post the solution for unknown reason. If you need docker files send me a private message.
LogMeIn Contributor

Re: Ubuntu 17.10 hamachid crashes on login (glibc 2.26)

Martin,

I can follow up to see why, Can you DM me with any screenshots. Steps you took while posting and a copy of your post?

Best,

Vitor
Vitor is a member of the LogMeIn Community Care Team.

Was your question answered? Please mark it as an Accepted Solution.
Was a post helpful or informative? Give it a Kudo!
Active Contributor

Re: Ubuntu 17.10 hamachid crashes on login (glibc 2.26)

Hamachi in docker solution:

 

download and unpack:

https://www.dropbox.com/s/6cq55ari82sqtzl/docker-hamachi.zip

 

copy /var/lib/logmein-hamaci/* to docker-hamachi/tmp/logmein-hamachi folder:

run:

./build.sh

./connect.sh

 

copy docker-hamachi.desktop to ~/.local/share/applications (change exec and icon path in file), if you want docker to bi in application launcher in Gnome shell.

 

It work if you want connect to client (ssh, mount), but on client side could be problem because you will end inside docker... In my case, after start docker I can connect to client even from host os (fedora 27), but hamachi list works only inside docker... It is temporarly solution if you need to connect to your clients until logmein do not fix hamchi to works with glibc 2.26...  

 

New Contributor

Re: Ubuntu 17.10 hamachid crashes on login (glibc 2.26)

Running Hamachi inside Docker is not a solution. It's practically the same as running it in a VM, which is useless because it defeats the whole purpose of Hamachi.

New Contributor

Re: Ubuntu 17.10 hamachid crashes on login (glibc 2.26)


vexati0n wrote:

Running Hamachi inside Docker is not a solution. It's practically the same as running it in a VM, which is useless because it defeats the whole purpose of Hamachi.


You can forward all traffic from docker to host machine with iptables. 

 

So You will get a connection to all your clients from a host machine via docker instance and all your clients will reach your host machine by port forwarding.