Hamachi:Hamachi-override.ini

From LogMeInWiki

Jump to: navigation, search

Add to: del.icio.us | Digg | Slashdot

Note, the file is actually lowercase letters, disregard the capital H.

Here are the parameters you can activate via hamachi-override.ini . These are features that are not normally on/configured by default. You can also use hamachi-override.ini to override settings in hamachi.ini , however the preferred method for this is in the GUI.

These lines can be entered, one entry per line, in hamachi-override.ini to enable the features on next start of the program. You need to create hamachi-override.ini in the configuration folder manually.

Compression

Premium Feature

Compression 1

When this feature is enabled on both ends of a Hamachi tunnel, the traffic between the two computers is compressed. This saves bandwidth and can help speed up data transfers as well. This is phased out as of version 1.0.2.0 and replaced by settings in the Hamachi:Advanced Peer Menu

Built in Proxy

Premium Feature

HttpProxy  1
HttpProxyPort  8888
HttpProxyAuth  1
HttpProxyUser  someUser
HttpProxyPass  myPassword

These lines all pertain to the built in web proxy. This can be used in cases where you want to use the Hamachi tunnel to secure your web browsing through another computer, such as from Internet cafe's, hotspots, etc. This is not technically a Premium feature, but there is a traffic limitation of 2.5 MB that can be forwarded from the Internet through the proxy. This counter is reset each time Hamachi is started. Premium users do not have this limitation. Only the first entry is required to enable the proxy, the rest are to customize the port, whether to use authentication, and if auth is used, the username and password

This feature does not work properly on Internet Explorer 7 or Firefox 2.0 . Instead, try a free and very robust proxy software called FreeProxy.

Tunnel reset

TunReset 1

This is used if you would like the ability to manually reset the tunnel to a specific peer. Once implemented, you can reset a tunnel by highlighting the desired peer and pressing F5 on your keyboard. Note this is built into the client as of version 1.0.1.x

Routed Tunneling

RoutedTunneling 1

This is used to allow Hamachi to forward packets destined for non-Hamachi addresses through the tunnel. See this link for more information on setting up this feature to bridge networks together. [Routed Tunneling]

Note that this is phased out as of 1.0.2.x in lieu of the Hamachi:Advanced Peer Menu

Custom menu item

CustomMenuItem <label for menu item>
CustomMenuCommand   <command>

These two lines are used to add a custom right click menu item to when you right click on a network peer. The first line is for the Title/Label/Name/etc, the second is for the command itself. The parameter you can pass through Hamachi is $ADDR, which will insert the Hamachi IP into whatever command you use.

A practical example would be using this custom item to add a Remote Desktop Connection context item to your peer right-click menu. This would look like:

CustomMenuItem Remote Desktop
CustomMenuCommand mstsc /v:$ADDR

Keep in mind you have to enable Remote Desktop on the target peer machine to actually access it via this method or directly.

UPnP logging

UpnpLog 1

Turns on UPnP logging. This is useful for troubleshooting pesky Universal Plug and Play issues. Hamachi uses UPnP to try and automatically configure your gateway device (router) to create the port mapping it needs to properly tunnel to your other Hamachi network machines without manual configuration.

Crypto logging

LogCrypto 1

This is used for creating bit-level log of authentication portion of the login sequence as well as both client-server and peer-to-peer key exhanges.

The log filename is crypto.log and it is created in Hamachi configuration directory. It tends to grow very quickly, so keep this in mind when enabling it.

Please use with utmost care as the log contains enough information to re-create exact traffic encryption keys and therefore recover raw network data from an encrypted capture if someone bothers to create it.

Bandwidth Control

RateTx ###
RateRx ###

Use these settings to activate the built-in traffic shaper. RateTx is outbound bandwidth shaping, RateRx is inbound bandwidth rate.

Rates are to be entered in kilobytes per second, with a minimum of 5. Setting either to 0 will allow for unlimited transfer speed.

Automation

Version 1.0.1.4 adds a number of new parameters to the list of those loaded from hamachi-override.ini. In addition to those described in 1.0.1.4 ChangeLog (www.hamachi.cc/changes), the following parameters are also available

AutoNickname <nickname>

The nickname to use during the enrollment step. If this value is present, Hamachi will not show the 'select the nickname' dialog when the client is put online for the first time. Note that in order for to force the client to go online at the first run, just add

AutoLogin 1

to the hamachi-override.ini.

AutoNetwork <network>

The name of the network the client will try to join when it logs in for the first time (ie right after it completes the enrollment)

AutoPassword <password>

The password to go with AutoNetwork.

Logging override

LogFile <path>

You can also set Hamachi to filter the log by specific types. Each value can be added to another to have both types be logged. Example, to log connectivity and UPnP, you'd set LogMask 5.

(general)
LogMask 1
(connectivity, Hamachi generated only)
LogMask 2
(UPnP)
LogMask 4
(Proxy)
LogMask 8

Specifies where to log stuff after the config is processed. if the file does not exist, it's not created.

Error Correction

These settings can be used to correct for tunnels being dropped for inactivity. By default, Hamachi has logic to prevent this, but certain lossy connections may need to be manually corrected for optimum stability and uptime.

KaClient <milliseconds>

The interval in which keepalive traffic is sent to peers, in milliseconds.

KaServer <milliseconds>

The interval in which keepalive traffic is sent to the mediation server. In milliseconds. Minimum 60000 (60 seconds).

ReTunnel <milliseconds>

The threshold of inactivity between peers before Hamachi will request that the mediation server rebuild the tunnel.

Minimum: ReTunnel >= 2*KaClient and ReTunnel >= 30000

BindTo <ip address>

Forces Hamachi to bind its sockets to a specific interface on the machine. This is helpful if you have multiple adapters (plus Hamachi's) and you need Hamachi do to its connectivity over a specific adapter.

Chat Colors

ChatColorLogBack     <color>
ChatColorLogFore     <color>
ChatColorLogSelf     <color>
ChatColorLogPeer     <color>
ChatColorLogSystem   <color>
ChatColorLogNetwork  <color>
ChatColorMsgBack <color>
ChatColorMsgFore <color>
ChatColorLogHistory  <color>
  • Back is a color of a background of both the top chat pane.
  • Fore is a text color of the top pane.
  • Self is a color of local IMs in the top pane, Peer - of the remote ones.
  • System is a color of system messages (such as 'xyz is online').
  • Network is a color of administrative messages when in a network chat mode.
  • MsgBack is the background color of the typing area
  • MsgFore is the text color in the typing area
  • History is a color of a chat log when it is loaded in a top pane via 'Load History' right-click menu option.

<color> is in a hexadecimal format - RRGGBB or RGB - the same format used by HTML, CSS and a multitude of graphical editors. Red is FF0000 or F00, cyan is 00FFFF or 0FF, white is FFF or FFFFFF, black is 000 or 000000, etc

A practical example:

ChatColorLogBack 000000
ChatColorLogFore FFFFFF
ChatColorLogSelf 528B8B
ChatColorLogPeer CFDBC5
ChatColorLogSystem CC99CC
ChatColorLogNetwork C2C2C2
ChatColorLogHistory CDCDCD

Produces this:
image:chat_override.png

Hiding Balloons

Hamachi 1.0.2.x added Windows System Tray Ballons for its notifications. Clients newer than 1.0.2.2 can disable this feature if needed, by adding:

NoTrayBalloons 1
Personal tools