= Configuration files =

The MUSCLE Transfer Overlay (MTO) is a daemon for forwarding traffic from MUSCLE 2. This service is often required when MUSCLE 2 is run on several sites with firewall restrictions. On each site, a MTO should be placed on a node that is less strict in its firewall policies, but that can be accessed from other MTO nodes. Often, clusters have an interactive node that is suitable for this purpose.

MTO's configuration is stored in two files:
 * global topology file (`MUSCLE_HOME/etc/mto-topology.cfg`)
{{{
// Comment
# Comment

# host definiton
# <name> <address> [<port>]
# if port is ommited, this MTO will not listen for incomming connections

A localhost
B localhost 5100
C localhost
D localhost 5300
}}}
 * local mto config file ( `MUSCLE_HOME/etc/mto-config.cfg`)
{{{
# Name of this MTO as in mto-copology.cfg
myName = A

# Port range for clients of this MTO
# Clients may register listening ports only from this range.
# This range must not overlap any other MTO's range.
localPortLow    = 5002
localPortHigh   = 5099

# Port and address where this MTO will listen for client requests.
# Port and address for other MTO's is located in the topology file.
internalPort    = 5001
internalAddress = private-address
}}}

For MUSCLE 2 commands, the second file is of importance: it implies that it can only use a limited port range on a given cluster, and how it should contact the MTO. To make this information available to MUSCLE 2, create the file `MUSCLE_HOME/etc/muscle.defaults` matching the `mto-config.cfg` file, containing
{{{
export MUSCLE_MTO=private-address:5001
export MUSCLE_PORT_MIN=5002
export MUSCLE_PORT_MAX=5099
}}}

When MUSCLE_HOME/etc/muscle.profile is sourced, these variables are then also set.
= starting MTO =
 * debug mode 
{{{
   ./bin/mto --debug
}}}
 * deamon mode
{{{
 ./bin/mto
}}}
= Example setup =