Changes between Version 21 and Version 22 of MTO

Timestamp:

11/26/13 13:34:50 (11 years ago)

Author:

jorisborgdorff

Comment:

--

MTO

@@ -1 +1 @@
 [[PageOutline]]
 = Using MTO =
-The MUSCLE Transfer Overlay (MTO) is a daemon for forwarding traffic from MUSCLE 2. This service is often required when MUSCLE 2 is must communicate between several sites with firewall restrictions. On each site, a MTO should be placed on a node that is accessible within the cluster and from the outside world. Often, clusters have an interactive node that is suitable for this purpose.
+The MUSCLE Transfer Overlay (MTO) is a daemon for forwarding traffic from MUSCLE 2. This service is often required when MUSCLE 2 must communicate between several sites with firewall restrictions. On each site, a MTO should be placed on a node that is accessible within the cluster and from the outside world. Often, clusters have an interactive node that is suitable for this purpose. At least one of the interactive nodes should be able to accept connections from outside the cluster, the other interactive nodes only have to be able to connect to another cluster.
 
-If MTO is already installed, set up, and connected between all relevant sites, all that is needed from MUSCLE to use the MTO is to add the `--intercluster` flag to the command-line:
+If MTO is already installed, set up, and connected between all relevant sites (see the next paragraph), all that is needed from MUSCLE to use the MTO is to add the `--intercluster` flag to the command-line:
 {{{
 muscle2 -mc model.cxa.rb --intercluster sub1
@@ -11 +11 @@
 muscle2 -c model.cxa.rb --intercluster -M 10.0.0.200:5002 sub2
 }}}
-For convenience, the `--intercluster` flag also has the shorthand `-i`.
+For convenience, the `--intercluster` flag has the shorthand `-i`.
 = Configuration files =