Software Update: Hamachi 1.0.0.47

On Hamachi’s forum is a new version of the 1.0 series announced. It is, to be precise, a pre-alpha release carrying version number 1.0.0.47. Through here clicking the new Hamachi will be downloaded as an installation file. Via Hamachi it is possible to make a direct connection, as it were, with the computer of another Hamachi user, without being hindered by any router, gateway or firewall. Via the established connection it is possible to exchange files and play multiplayer games against each other. All connections are between Hamachi clients secured through a certain number of protocols. Below are the changes posted since the program’s last entry in the Meuktracker:

1.0.0.47

• Fixed an issue with Hamachi writing .ini file every 1-2 seconds without any apparent reason for doing so.
• Introduced hamachi-override.ini file.

  hamachi.ini is used and managed by Hamachi. This in particular means that any changes made to this file while Hamachi is running are ignored and written about.

  To add custom settings such as RoutedTunneling, BindTo or TxRate or to override default ones hamachi-override.ini file should be used.

  When Hamachi starts, it first reads hamachi.ini and immediately after this it loads hamachi-override.ini. Any settings found in the latter override any values ​​loaded from former. Hence the name.

  Lastly, Hamachi never modifies hamachi-override.ini file.

• Multiple small fixes in the code that performs a conversion of registry-based configuration into .ini files. When upgrading from pre-1.0.0.45 versions, it is now possible to downgrade back to the original version and run it as usual (ie registry configuration is now kept intact).

1.0.0.46

• Fixed the problem with Hamachi consuming ~10-15% CPU in idle state when there is an active antivirus running on a host machine.

1.0.0.45

• Reworked IPX tunneling part. Previously Hamachi understood 4 types of IPX framing, but used only one to inject peers’ IPX frames into the system network stack. With this version the framing type is also passed with a packet over a tunnel and it is correctly re-created on the receiving end.
• Fixed the problem with Hamachi not going online automatically when it is switched into a service mode.
• Fixed two small bugs in Hamachi network adapter driver. These may or may not resolve the issue of compatibility with Kaspersky ‘real-time network protection’ feature.
• Reworked configuration subsystem not to use Registry anymore. Virtually all Hamachi configuration data is now stored in a disk file(s). The following directory is used by default –
  C:\Documents and Settings\%USER%\Application Data\Hamachi

  Aadded -config command-line argument to allow overriding default configuration location, eg

  hamachi.exe -config “d:\temp\my hamachi backup”

  In particular this switch can be used when running Hamachi under SrvAny.

  This change also means that backing up Hamachi identity now becomes a matter of making a copy of its configuration folder.

  Also, when loading ‘IP aliases’ information, Hamachi now first tries to read aliases.ini file from its config directory and then aliases.txt from its installation directory.

  Lastly, the routed tunneling settings were also moved from the registry to the file. The file is routes.ini; each line starts with peer’s 5.xxx IP followed by one or more ‘proxied’ IPs, ranges and subnets. For example –

  5.1.2.3 10.0.0.102 192.168.1.0/24 192.168.2.10-192.168.2.13

  ‘Known Public Keys’ sub-directory was renamed to ‘RSA Keys’. New ‘Networks’ sub-directorty has been added to the configuration as well as peers.ini file, which caches per-peer settings and information.