Labs & Betas

Hamachi Release Notes

LogMeIn Hamachi for Windows 2.1.0.294, Mac 2.1.0.454, and Linux 2.1.0.84

Enhancements

Hamachi log file improvement

The Hamachi crash log file now contains the version information of the Mac client.

Client improvements

On the Hamachi client, .local has been added to the ping [client ID] and copy [client ID] context menu options of Hamachi peers. For example, ping 123-456-789 has been changed to ping 123-456-789.local in the context menu. This change has no effect on functionality.

Hamachi interface on Windows

In IPv6-only mode, the Network Location Awareness service on Windows clients did not qualify the Hamachi interface as a public interface. As a result, it is now possible to set up Hamachi as a Work or Home network which is less restrictive than public networks. This, in turn, causes less issues with firewall settings.

Fixes

Command line clients trim address

The command line version of the Hamachi client trimmed the IP address of peers. This error effected Mac and Linux clients.

Notification window on Mac clients

It was not possible to click links in the notification window on Mac clients.

Notification window on Windows clients

It was not possible to move the notification window on Windows clients.

Menu bar icon missing in offline mode

The envelope icon on the menu bar was not visible on Mac clients when there was a message for the client but the client was offline.

Gateway did not check OS type on Windows

The Hamachi client did not send information about the type of operating system that the client was running. The client only communicated whether it was running a 32 or 64-bit OS. As a result, this information was not displayed on the Networks > My Networks page of the LogMeIn website.

“Cannot connect to engine” error

In some cases, due to a communication error between the Hamachi GUI and the Hamachi engine, the client failed to start and displayed a Cannot connect to engine message. This issue effected Windows and Mac clients.

Masked password field

When you create a network on the Hamachi client, it was possible to see the entered characters in the password field. As of this release, the content of the password field is masked. This issue effected Windows and Mac clients.

LogMeIn Hamachi for Windows 2.1.0.284

Fix

Default gateway of the Hamachi virtual interface

The IP address of the default gateway was not updated from 5.x.x.x to 25.x.x.x. As a result, certain firewalls prevented applications from establishing connection over Hamachi.

LogMeIn Hamachi for Windows version 2.1.0.274, Mac 2.1.0.434, and Linux 2.1.0.81

Fixes

Server relay link issue

In some cases, when the Hamachi client used direct link to connect to a peer, it dropped its via server relay link if the relay link was not in use for a longer period of time.

Custom routes in a gateway network on Windows clients

Windows clients in a gateway network did not propagate custom routes. As a result, Hamachi did not use pre-defined network subnets.

Hamachi virtual NIC failure on Windows

In some cases, configuration of the Hamachi virtual NIC failed on Windows clients.

Incorrect Linux client version information

Version information on Linux clients was incorrect.

LogMeIn Hamachi for Windows 2.1.0.262, Mac 2.1.0.426, and Linux 2.1.0.80

New Features

Online status for unattended clients

Until now the Hamachi client started automatically as a service and the client went online when you started or restarted your computer. As of this release, the Hamachi client for Free users only goes online in Hamachi networks if you log in to the computer that runs the Hamachi client. This feature only affects Windows and Mac users whose computers require them to log in with their user credentials.

System notifications

The client now displays system notifications in a popup window whenever there are important changes in Hamachi that LogMeIn wants to communicate.

Copy and ping peers by Client ID

You can now use mDNS or LLMNR to address your peers by their client ID rather than their dynamic virtual IP address. To do so, the following context menu options have been added to the Hamachi client:

Ping [ClientID]
Copy [ClientID]

[ClientID] stands for the Hamachi client ID of the peer. For example, you can ping a peer by right-clicking your peer’s name and clicking Ping 123-456-789.

Enhancements

Hamachi clients move to the 25.x.x.x IP range

As of November 19, 2012, Hamachi clients will have their virtual IP addresses changed from 5.x.x.x to 25.x.x.x. This change will have no effect on your Hamachi networks.

IPv6 address for the default gateway of the Hamachi adapter

As of this release, an IPv6 default gateway is set for the Hamachi network adapter when the IP protocol is configured to IPv6-only or Both mode. You can set the IP protocol mode in System > Preferences > Settings > Advanced Settings > Peer Connections.

Fixes

Unsuccessful client update on Fedora Linux

In some rare cases, the downloaded client update was not installed successfully and, as a result, the Hamachi client did not start on Fedora Linux computers.

Menu available in offline mode on Mac clients

When a client was installed for the first time, the System > Attach to LogMeIn account menu was available on Mac clients even if the client was offline.

Client user interface issues on Windows

In some cases, when an unexpected error occurred and the LogMeIn Hamachi service restarted the client interface, the client was resized, opened at a different location in the screen, and certain user interface configurations were not taken into account.

Hamachi Client Failing to Connect to the Hamachi Engine

In some cases, the Hamachi client was not able go online and displayed the following error:
Failed to connect to engine
By improving the client connection method it is now less likely to get this error.

Hamachi engine and client interface issues on Macs

In some cases, the Hamachi engine and the client stopped working due to an unexpected error.

LogMeIn Hamachi for Windows 2.1.0.215, Mac 2.1.0.346, and Linux 2.1.0.76

Fixes

Multicast DNS

In some cases, LogMeIn Hamachi stopped unexpectedly when multicast DNS (mDNS) packets were transferred. This issue affected Windows, Mac, and Linux clients.

VPN Alias

In some cases, peer-to-peer (P2P) connection was lost when you assigned an IPv4 address to the peers of your network. As of this release, P2P connection is reliable when using VPN alias. This fix affects Windows, Mac, and Linux clients.

Kernel extension (kext) issue

In some cases, a Hamachi client update did not refresh the necessary kernel extension. As a result, the Hamachi virtual network adapter did not work properly.

Update notification

In some rare cases, a message about not having new client updates was incorrectly displayed twice. This issue only occurred when you checked for client updates manually and then automatic updates were run that did not retrieve new client updates either. In this case, a message was displayed both after manual and after automatic checks were run.

LogMeIn Hamachi for Mac version 2.1.0.322

Fix

OSX 10.8 Mountain Lion Support Issue

When at least one of the Hamachi clients was running Mac OS X 10.8 (Mountain Lion), peer-to-peer connection was unreliable.

LogMeIn Hamachi for Mac version 2.1.0.300

New Features

Support for OSX 10.8 Mountain Lion

LogMeIn Hamachi now supports Mac OS X 10.8 (Mountain Lion).

Enhancements

Updated installer

The LogMeIn Hamachi installer has been updated to be compatible with OSX 10.8 (Mountain Lion).

Fixes

Kernel panic issue

In some rare cases, when the network configuration of a Mac was changed, the LogMeIn Hamachi network adapter caused kernel panic, which made the computer unresponsive. As a result, Hamachi users had to restart their computers. This error only occurred on Macs running OS X 10.7.

Firewall issue

In some cases, a notification about Hamachi being a threat was displayed when Hamachi was running and the firewall was turned on. This error only occurred on Macs running OS X version prior to 10.7.

LogMeIn Hamachi for Windows 2.1.0.210, Mac 2.1.0.190 and Linux 2.1.0.68

Enhancements

Support for new subscription model in Hamachi for Linux

The Linux command line version now supports the new Hamachi subscription model. For information about the new subscriptions, see the LogMeIn Hamachi User Guide or check the Knowledge Base.

Support for Linux libc pre-2.7 versions

To provide better compatibility, Hamachi now supports libc versions prior to 2.7.

Automatic reconnection

The automatic reconnection method that handles network connection errors, has been improved for Windows, Mac, and Linux clients.

Automatic updates

When automatic updates are turned on, Mac, Windows, and Linux clients now check for updates automatically after they are online for a week. To turn on automatic updates on a Mac or Windows client, go to System > Preferences >Settings > Basic settings and select Enable automatic update. By default, automatic updates are turned on.

VPN alias

You can assign an IPv4 address to the peers of your network. This is useful when the application used over Hamachi requires Class C network addresses, meaning that the network prefix (5.xxx.xxx) is the same, only the host identifier (the last part of the IP address) differs for every peer. This improvement affects Windows, Mac, and Linux clients.

Multicast DNS and LLMNR support

Hamachi now supports Multicast DNS (mDNS) and LLMNR to help name resolution. As of this release, you can use hostname.local or 123-456-789.local (client id) to address peers.
By default, mDNS is enabled on Windows, but disabled on Mac OSX and LINUX. To change this setting, go to System > Preferences >Settings > Advanced settings > Peer Connections > Enable mDNS name resolution.
By default, LLMNR is disabled on Windows (Vista or better), but enabled on Mac OSX and LINUX. To change this setting, go to System > Preferences >Settings > Advanced settings > Peer Connections > Enable LLMNR name resolution.

Fixes

Japanese localization on Windows clients

The Manage Network menu on a Windows client did not have a shortcut due to localization issues.

Audio notification for chat messages on Windows clients

Audio notification was not played when a new chat message arrived. This error only occurred if you selected Blink the systray icon for visual notification. You can set your chat settings in System > Preferences > Settings > Advanced Settings > Chat Settings.

Downloading client updates on Windows clients

In some cases, the client found and downloaded the latest updates, but failed to install them due to an MSI installer error. As a result, the existing version of the client was restarted and, therefore, the client continuously searched for and downloaded available updates and tried to install them again. This resulted in an infinite loop of searching for and failing to install updates.
As of this result, the Hamachi client only searches for updates if it did not download updates for two hours.

Logging out on Windows and Mac

In some cases, peers did not appear offline immediately after going offline in a Hamachi network. This issue only occurred on Mac and Windows clients.

Joining and creating networks on Mac clients

After joining or creating a network from the Hamachi client, the window was only closed if you moved the mouse. To join or create a network, on the Hamachi client go to Network > Join Network or Network > Create Network.

Deploy link on Hamachi Mac clients

In version 2.1.0.120 of the Hamachi Mac client, it was not possible to use a deploy link to install the client because links created on a Mac were ignored.

Reconnection issues

The following fixes have been made on Windows, Mac, and Linux clients related to reconnection:

In some cases, the Hamachi client did not try to reconnect after network connection loss. As of this release, the client always tries to reconnect regardless of why the connection was lost.
The Hamachi client tried to reconnect continuously after network connection loss. As of this release, there is a delay between two reconnection attempts.

LogMeIn Hamachi for Windows 2.1.0.166 and Mac 2.1.0.120

Enhancements

Join network timeout message

The Hamachi client now displays a failed join request notification if the following occurs:

The Hamachi user tries to join a network that requires the network owner’s approval
The network owner does not approve the request in two weeks
The request is automatically rejected and the Hamachi client displays a timeout message

Attach client timeout message

A Hamachi client can only be attached to a LogMeIn account if the account holder approves the client user’s request. If the account holder does not respond to the request in two weeks then the Hamachi client displays a timeout message.

Purchasing a license for free networks

You can now purchase a subscription for a free network that was created on the Hamachi client. Right-click on the name of the network and select Buy subscription.

Fixes for Windows

Peer status issue

The Hamachi client stopped working if the Hamachi user hovered the mouse over the status of a peer on the client.

Fixes for Mac

Network menu options

Network menu options were unavailable if you changed a setting in System > Preferences > Settings > Advanced Settings and clicked OK.

LogMeIn Hamachi for Windows 2.1.0.158 and Mac 2.1.0.100

LogMeIn Hamachi offers the following subscriptions:

Free subscription allows you to have eight members in a network
Standard subscription allows you to have 32 members in a network
Premium subscription allows you to have 256 members in a network
Multi-network subscription or a LogMeIn Central subscription allows you to have 256 members in all your networks

Note: The current and maximum number of network members are displayed on the Hamachi client next to name of the network. For example, 11/256 means that there are 11 members in a network that can have up to 256 members.

What if I do not want to renew my subscription?

Standard, Premium, and Multi-network subscriptions are paid subscriptions that allow you to have more than eight members in your network. If your network has more than eight members, you should take the following into consideration before you cancel your subscription:

Your network will not accept any new members.
Only eight members will be active. Other members will be disabled (offline) in your network until you resolve this issue by purchasing a subscription or evicting network members.
Your network will still be fully functional but only for eight randomly selected members.
You can renew your expired subscription any time. For information about purchasing a Hamachi subscription, visit the LogMeIn Hamachi product page at https://secure.logmein.com/products/hamachi/.

What if I never had a paid subscription?

For free networks with more than eight members, existing members remain active, but you will be unable to add new members. For example, a free network that was created with 14 members before introducing Standard, Premium, and Multi-network subscriptions will be fully functional, but it will not accept new members.

Important: If you have more than eight members in a network and you choose to have a free subscription, you will not be able to add new members until you remove some of them from the network.

LogMeIn Hamachi for Mac version 2.1.0.65

New Features

IPv6 support

LogMeIn Hamachi supports IPv6 network protocol.

Enhancements

LogMeIn Hamachi2 renamed

LogMeIn Hamachi² has been renamed to LogMeIn Hamachi.

Removing configuration files during uninstallation

You can remove your LogMeIn Hamachi configuration files by selecting the Remove all settings option during uninstallation.

Dialog for going online in another gateway network

A dialog is now displayed if a client that is already online in gateway network A tries to go online in gateway network B. If the Hamachi user clicks OK to go online in gateway network B then the client automatically goes offline in gateway network A.

Going online in a gateway network

A new dialog is displayed if the client tries to go online in a gateway network when the gateway is offline. In this case, the client can choose to come online when the gateway comes online.

Deploy client from website

The Hamachi client can be deployed from the LogMeIn website.

Fixes

Hostname changed in gateway networks

Clients in a gateway network incorrectly changed their hostnames due to a network conflict issue.

Chat color settings were ignored

Chat color settings were ignored on Hamachi for Mac clients.

Automatic client update issue on OS X 10.7

Automatic client update was not working properly if the client was running OS X 10.7 (Lion). You could only manually update the LogMeIn Hamachi client.

Client did not go online if Preferences window was open

The client could not go online if the Preferences window was open.

LogMeIn Hamachi for Windows version 2.1.0.122

New Features

IPv6 support

LogMeIn Hamachi supports IPv6 network protocol.

Enhancements

LogMeIn Hamachi2 renamed

LogMeIn Hamachi² has been renamed to LogMeIn Hamachi.

Exit menu item was missing from system tray menu

The Exit menu item was removed from the system tray menu in the previous Hamachi or Mac release. It is now re-added to the system tray menu.

Fixes

Join network window lost focus

The Join into a network window lost focus if the client’s join request was approved in another network in the meantime.

Collapse/expand icon did not change from keyboard (+/-), the icon does not align

The collapse/expand icon did not change on the client user interface if you toggled a network with the +/- keys on the keyboard.

Gateway network issues

The following errors occurred in gateway networks:

In some cases, network adapters were not displayed in the Start > Control Panel > Network Connections window if the gateway client either left the gateway network or changed its role to member. In this case, the network bridge of the gateway network was removed.
The client engine unexpectedly stopped running if a member’s role was changed to Gateway on the LogMeIn website.

LogMeIn Hamachi2 for Windows 2.0.3.115

Fixes in LogMeIn Hamachi2 for Windows

TCP tunnel setup

An incorrect IP address was recorded during TCP tunnel setup.

Unregistering UPnP entry

UPnP entries were not unregistered before a new one was registered.

UPnP entries not removed from router

UPnP entries were not removed from the router's settings if the Hamachi2 client was not shut down properly. This occurred for example due to system failure, or network interruption.

Welcome messages in minimal mode

Clients running in minimal mode incorrectly received network welcome messages.

The options in the Network menu were available on the Hamachi2 for Windows client in restricted mode even if joining or creating networks were disabled on the LogMeIn web interface.

You can change these client settings on the web interface by switching to Network mode and then clicking Edit next to the client you want to change. You can modify your client settings on the Settings tab.

LogMeIn Hamachi2 for Mac 2.0.1.50

Enhancements in LogMeIn Hamachi2 for Mac

Browse feature extended

You can now select between Windows File Sharing and Apple File Sharing when you browse a peer’s computer. You can browse on a peer by right-clicking the peer and clicking Browse.

Compatibility with Mediashare

Compatibility with UPnP devices using Mediashare has been improved.

Hamachi2 menu bar icon

The Hamachi2 icon is now displayed on the menu bar.

Fixes in LogMeIn Hamachi2 for Mac

Client window position

The position of the Hamachi2 client was not saved when you closed the application.

Preferences were not always saved

In some cases, the options in the Preferences window were not saved after you changed those.

Option removed from Basic Settings

The Disable UPnP option was removed from the Preferences > Basic settings page.

Second notification message did not respond

Clicking on the notification icon on the systray did not respond if you received two messages of different type and you have already opened the first notification.

Restricted mode options

The Enable online presence option has been removed from the Basic settings page for clients running in restricted mode.

Attaching and detaching the client

The client user interface behaved unexpectedly in the following cases:

• You received an attach or a detach message.

• You detached the client while it was still a member of a network.

• You detached the client while it was running in minimal mode.

Tab key acted as Enter when attaching a client

The Tab key acted as Enter if you attached your client to an existing account in the Attach to LogMeIn Account dialog.

Client User Interface issue

The client user interface was not displayed after Hamachi2 was reinstalled.

Double-click did not ping a peer

In some cases, double-clicking a peer’s name did not ping the peer.

Custom commands

Running custom processes blocked Hamachi2 until the process ended. You can define custom processes to run in Preferences > Settings > Advanced Settings > Interface Settings > Show custom command in peer’s menu.

System message showed incorrect date

In some cases, system messages about restarting Hamachi2 servers displayed incorrect dates.

Hamachi2 log file

In some cases, the Hamachi2 log file contained incorrect entries.

Peer-to-peer tunnel setup

In some cases, it was not possible to establish a peer-to-peer tunnel if there was packet loss during the negotiation phase.

TCP tunnel setup

An incorrect IP address was recorded during TCP tunnel setup.

Incorrect IP address assigned to client

In some cases, the IP address 0.0.0.0. was incorrectly assigned to the client.

Uninstalling Hamachi2

An empty notification window was displayed when you uninstalled the Hamachi2 client.

Warning icon did not open dialog

Clicking on the yellow warning icon did not open the Peer Properties dialog.

Clients did not run in minimal mode

It was not possible to run the Hamachi2 client in minimal mode on a Mac.

Network welcome messages

Network welcome messages were not displayed on Hamachi2 Mac clients.

Network messages were not displayed on system tray

The system tray icon did not blink when a network messages arrived.

Unregistering UPnP entry

UPnP entries were not unregistered before a new one was registered.

UPnP entries not removed from router

UPnP entries were not removed from the router's settings if the Hamachi2 client was not shut down properly. This occurred for example due to system failure, or network interruption.

Menu labels in systray icon

The context menu of the Hamachi2 system tray did not display menu items.

Welcome messages in minimal mode

Clients running in minimal mode incorrectly received network welcome messages.

Network menu options in restricted mode

The options in the Network menu were available on the Hamachi2 for Mac client in restricted mode even if joining or creating networks were disabled on the LogMeIn web interface.

UPnP performance issue

CPU load was unnecessarily high if UPnP was in use.

LogMeIn Hamachi2 for Windows 2.0.3.111

Enhancements in LogMeIn Hamachi2 for Windows

Improved Hamachi2 tunnels

Hamachi2 tunnels are now more robust, which makes it easier to establish peer-to-peer connections between clients with low quality network connections.

Compatibility with Mediashare

Compatibility with UPnP devices using Mediashare has been improved.

Fixes in LogMeIn Hamachi2 for Windows

System notifications were not displayed

System notifications did not appear in the system tray.

Client closed in restricted mode

The Hamachi2 client closed unexpectedly if you switched between basic and advanced modes at System > Preferences > Settings while running in restricted mode.

Incorrect IP address used for P2P

Establishing a tunnel was slow or failed for clients on same LAN if the communication port was set only at System > Preferences > Settings > Advanced Settings > Peer Connections.

Incorrect date format in notifications

In some languages, the date was not displayed correctly in notification messages concerning planned maintenance..

UPnP entries not removed from router

UPnP entries were not removed from the router's settings when the Hamachi2 client was not shut down properly (for example, due to system failure or network interruption).

Incorrect client statistics

In some cases, incorrect client statistics were displayed if the Hamachi2 client was left running for a long time. To view client statistics, right-click on a client and select Details.

Incorrect gateway DNS settings

Secondary DNS server settings overwrote the primary DNS server settings of a gateway client.

LogMeIn Hamachi for Mac version 2.0.1.23

New Feature

Automatic port detection

You can now disable automatic port detection for establishing peer-to-peer connection with other Hamachi clients. When this option is disabled, Hamachi tries to use a relay tunnel with other peers if it cannot establish peer-to-peer connection. You can find the Disable UPnP option in LogMeIn Hamachi > Preferences > Settings on the client.

Enhancements

User interface

The user interface of the client has been improved.

Exit from the Hamachi client

You can only exit from the System menu on the client, not by right-clicking on the Hamachi icon on the system tray.

Fixes

Network representation on the client

When you restarted the client, all networks were expanded. As of this release, networks are expanded or collapsed as they were before restarting the client.

Sending chat messages

It was possible to send empty chat messages.

Uninstalling Hamachi

Uninstalling the Hamachi client did not remove all files from your computer.

Custom peer labels

Custom peer label did not pick up the settings defined in the preferences. You can find these settings in LogMeIn Hamachi > Preferences > Settings > Advanced Settings > Interface Settings.

Join requests

Join requests did not appear on client when a network was set to manual approval.

Saving chat messages

Chat messages were not saved even if the Keep chant messages option was enabled. You can find these settings in LogMeIn Hamachi > Preferences > Settings > Advanced Settings > Chat Settings.

LogMeIn Hamachi2 for Windows version 2.0.3.89

Enhancements

Exit from the Hamachi client

You can only exit from the System menu on the client, not by right-clicking on the Hamachi2 icon on the system tray.

Network attachment notification

A notification message is now displayed when you request your client to be attached to a LogMeIn account.