Fixed: Hamachi Cannot Get Adapter Config

The Hamachi VPN service has been integrated into the Wireshark install since Wireshark 1.6.3. However, with this integration comes a bug that prevents Hamachi from obtaining its adapter configuration and communicating over the VPN tunnel where applicable.

This bug has been fixed in Wireshark 1.12.2. Upgrading to this version will eliminate this problem for Hamachi users with IPv6 enabled within their virtual adapter settings.

If you are using Hamachi, please upgrade to that version or newer to resolve this issue. If you are not using Hamachi, there is no impact on you.

Before Upgrading: Disable Hamachi

This issue has been discovered in testing, but only with the default configuration of Wireshark 1.12.2 that includes Hamachi support built-in to the installation package.

If you already use Hamachi and are not having an issue with it (and don’t wish to upgrade), please disable it within Wireshark before upgrading to make sure you don’t accidentally run the new release and break your Hamachi connection.

To do this, go to Edit > Preferences… in Wireshark, select Protocols from the top dropdown menu, click “IP,” and uncheck the box next to “Hamachi.” Click “OK” to save your change.

When you are ready to upgrade, download Wireshark 1.12.2 from the following location: https://www.wireshark.org/download.html

After Upgrading: Re-Enable Hamachi

After you have upgraded to Wireshark 1.12.2 or newer, re-enable Hamachi by following the above instructions for enabling it within your preferences.

If you are already using a non-1.12 version of Wireshark and had been having issues with Hamachi before upgrading, then this article does not apply to you.

After you have installed Wireshark 1.12.2, please re-enable Hamachi in Wireshark via the Edit > Preferences… dialog.

If you wish to use Hamachi but do not currently use Wireshark 1.12.2 or higher, you can download and install the latest version of it from: https://www.wireshark.org/download.html

I hope this clears up the situation for users with this particular issue.

Leave a Comment