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

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

Hello,

 

Our development team has been made aware of this. We have changed our FAQ to reflect this. 

 

http://help.logmein.com/articles/en_US/Documentation/hamachi-c-hamachi-systemrequirements

 

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!
New Contributor

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

Are there plans to support glibc 2.26 in the near future?

New Contributor

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

I am using fedora 27, glibc 2.26-15.fc27 is the lowest  possible option for hamachi,

 

dnf downgrade glibc glibc-common glibc-devel glibc-headers

 

Package glibc of lowest version already installed, cannot downgrade it.
Package glibc-common of lowest version already installed, cannot downgrade it.
Package glibc-devel of lowest version already installed, cannot downgrade it.
Package glibc-headers of lowest version already installed, cannot downgrade it.
Error: No packages marked for downgrade.

 

 

11.15 15:29:02.976 cfg: load()
11.15 15:29:02.976 dbg: deploy_id '' parse failed
11.15 15:29:02.976 cfg: hkc set: [2048] [2048]
11.15 15:29:02.976 cfg: save()
11.15 15:29:02.983 cfg: hks: [0] [2048]
11.15 15:29:02.983 cfg: hkc: [0] [2048] [2048]
11.15 15:29:02.983 starting up ..
11.15 15:29:02.983 sys: version linux-2.1.0.165
11.15 15:29:02.983 sys: os Linux 4.13.12-300.fc27.x86_64 #1 SMP Wed Nov 8 16:38:01 UTC 2017 x86_64
11.15 15:29:02.983 vpn: IPv6 support is: 3
11.15 15:29:02.984 ipc: 5 listening at /var/run/logmein-hamachi/ipc.sock
11.15 15:29:02.984 avc: start
11.15 15:29:02.984 avc: retry [1]
11.15 15:29:03.034 avc: retry [2]
11.15 15:29:03.084 avc: retry [3]
11.15 15:29:03.135 avc: retry [4]
11.15 15:29:03.185 avc: retry [5]
11.15 15:29:03.235 avc: warning, avc not ready, fallback 1
11.15 15:29:03.235 resolv: url has ip on it
11.15 15:29:03.235 sys: initializing vpn domains, vpn-reinstall = 0 ..
11.15 15:29:03.235 vpn: added [Hamachi] domain (not roaming)
11.15 15:29:03.235 dbg: setup_vpn_domain [Hamachi]
11.15 15:29:03.236 dbg: vpn_domain::config - [Hamachi]
11.15 15:29:03.236 vpn: switched [Hamachi] domain into L3 mode, 25.23.19.146/255.0.0.0
11.15 15:29:03.236 dbg: enable(Hamachi), locked: 0
11.15 15:29:03.236 vpn: domain [Hamachi] -> 'VPN_opening'
11.15 15:29:03.236 vpn: enabling [Hamachi] domain ..
11.15 15:29:03.236 vpn: on_set_tapdev(, 1) -> ok
11.15 15:29:03.237 tap: device ham0 opened
11.15 15:29:03.237 vpn: domain [Hamachi] -> 'VPN_up'
11.15 15:29:03.237 dbg: setup_vpn_domain [Hamachi]
11.15 15:29:03.237 dbg: vpn_domain::config - [Hamachi]
11.15 15:29:03.237 vpn: domain [Hamachi] -> 'VPN_setting_up'
11.15 15:29:03.237 tap: config(ham0, 25.23.19.146, 255.0.0.0, [/96])
11.15 15:29:03.238 tap: if_config() -> 1
11.15 15:29:03.238 vpn: tap config done, [ok]
11.15 15:29:03.238 vpn: domain [Hamachi] -> 'VPN_up'
11.15 15:29:03.238 vpn: added [Null] domain (not roaming)
11.15 15:29:03.238 dbg: setup_vpn_domain [Null]
11.15 15:29:03.238 dbg: vpn_domain::config - [Null]
11.15 15:29:03.241 sys: connmgr_go_online, reconnect 1
11.15 15:29:03.254 ses: on_conn_state(connected, 0x0)
11.15 15:29:03.254 ses: select conn mode 'dns lb'
11.15 15:29:03.254 ses: go_offline, keep_tunnels 1, login_on_relaunch 0, actual state 4 ..
11.15 15:29:03.267 sys: go_online, reconnect 1
11.15 15:29:03.273 ses: resolving hamachi-dc.logmein-gateway.com ..
11.15 15:29:03.273 vpn: arp, 25.23.19.146 is at 7a:79:19:17:13:92
11.15 15:29:03.362 ses: resolving hamachi-list.10.logmein-gateway.com ..
hamachid: relocation error: hamachid: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

 

 

We are using hamachi in our company for a long time. Ia m sorry but just stating in faq is not enough. We need a solution.

New Contributor

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

Hard to believe that Logmein views a change to the FAQ as a response/solution. I’m sure many of us existing Hamachi Linux users have machines on our networks running other flavors than the ones strictly supported. This response translates as “thanks for your patronage, now please go elsewhere.”

 

This problem seems eminently solvable with a modest code fix, with at worst branching code for backward compatibility with older versions of Glibc.

New Contributor

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

17.04 isn't an LTS release... which goes to show why you seem to think updating the documentation is an acceptable answer to this issue. As usual, Linux gets shuffled to the bottom of the priority list. I suppose you think you're doing us a favor by even acknowledging Linux's existence. Luckily for us there are other projects that do the same thing as Hamachi that don't treat Linux like a redheaded stepchild.

Highlighted
Active Contributor

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

I have found the solution. I have created docker with centos and installed logmein-hamachi inside docker and copied all logmein-hamachi files inside docker. Docker is connected with --net=host option. Wher I start docker I get connection from host linux to all my clients.  if anybody interested I can send you docker files. 

New Contributor

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

martin-b that is awesome! Please, can you share these docker files?

 

Would I be able to copy over the existing hamachi config from my host into the docker image?

New Contributor

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

+1 for me too. Very interested in the docker files.
Active Contributor

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

Hello Martin-B,

 

I would also be interested in testing it on my end if you could share it I would appreciate it.  

 

Best,

 

Vitor 

New Contributor

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

Hello.

 

Please share the fix with docket step to steps!