explain that peer can be specified as fqdn and contain optional port

Closes #137.
This commit is contained in:
Matthias Radestock committed 2014-10-25 19:51:06 +01:00
1 parent e9c5b2c3ea
commit 007b68c206
2 files changed
+6 -5

No files matched your search

+3 -3
View File
@@ -87,9 +87,9 @@ We repeat similar steps on $HOST2...
The only difference, apart from the choice of IP addresses for the
weave router and the application container, is that we tell our weave
that it should peer with the weave on $HOST1 (specified as the IP
address or hostname by which $HOST2 can reach it). NB: if there is a
firewall between $HOST1 and $HOST2, you must open port 6783 for TCP
and UDP.
address or hostname, and optional `:port`, by which $HOST2 can reach
it). NB: if there is a firewall between $HOST1 and $HOST2, you must
open port 6783 for TCP and UDP.
Note that we could instead have told the weave on $HOST1 to connect to
$HOST2, or told both about each other. Order does not matter here;
+3 -2
View File
@@ -3,7 +3,7 @@ set -e
usage() {
echo "Usage:"
echo "weave launch <cidr> [-password <password>] <peer_host> ..."
echo "weave launch <cidr> [-password <password>] <peer> ..."
echo "weave run <cidr> <docker run args> ..."
echo "weave start <cidr> <container_id>"
echo "weave attach <cidr> <container_id>"
@@ -15,7 +15,8 @@ usage() {
echo "weave stop"
echo "weave reset"
echo
echo "where <cidr> is of the form <ip_address>/<routing_prefix_length>"
echo "where <cidr> is of the form <ip_address>/<routing_prefix_length>, and"
echo " <peer> is of the form <ip_address_or_fqdn>[:<port>]"
exit 1
}