- This release fixes a bug that caused a network driver crash on Windows 8.1/2012 R2.
- This release fixed an issue that caused the service to start slowly on some computers.
# Bug fixes
* When installing to Windows XP, the engine configuration directory path is set correctly
* LMIGuardian now installs properly to 64-bit devices
* LogMeIn Guardian is now integrated with Hamachi. If Hamachi crashes, you can use LMI Guardian to send error reports to LogMeIn.
* Configuration has been moved to another directory to enable OS upgrades (e.g. from Windows 7 to Windows 8)
* Users on Windows 8 and above can now enable gateway mode.
* Tunnel reset being sent to mobile client peers
* Unexpected client reset
* Unexpected service closing
* For some OS X clients, gateway networks were not releasing routes upon logout or network disable
* Could not browse peer if VPN Alias address was set
# This release of the Hamachi client for Windows fixes a number of bugs, including the following:
- Hamachi ui.exe will no longer use excessive CPU resources when the Hamachi service is set to start manually
- The notification dialog no longer hides other dialogs
- The link in the notification regarding network capacity now properly communicates the ID of the network that needs to be upgraded
* 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.
* 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.
* 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.
* 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.
* 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.
* 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 18.104.22.168 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.
- 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.