Document adding a route on non-Weave hosts #2219
Conversation
| ###<a name="export-route"></a> Exporting Services to the wider network | |||
|
|
|||
| If you want hosts that are not running Weave Net to access services | |||
| exposed as above, on each of those machines: | |||
|
Q4 in https://github.com/weaveworks/weave/blob/master/site/faq.md needs updating. |
|
Updated; PTAL |
| @@ -10,6 +10,7 @@ This section contains the following topics: | |||
| * [Binding Services](#binding) | |||
| * [Routing Services](#routing) | |||
| * [Dynamically Changing Service Locations](#change-location) | |||
| * [Exposing the Weave Network More Widely](#export-route) | |||
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
|
I have moved the whole section to |
| @@ -38,6 +38,20 @@ Exposed addresses can also be added to weaveDNS by supplying fully qualified dom | |||
| host2$ weave expose -h exposed.weave.local | |||
| 10.2.1.132 | |||
|
|
|||
| ###<a name="routing"></a>Routing from another host | |||
|
|
|||
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
|
Updated per comments. |
| * `<exposing-host>` is the address of the machine on which you ran `weave expose`. | ||
|
|
||
| >**Note:** You must ensure that the [IP subnet](site/how-it-works/ip-addresses.md) | ||
| used by Weave Net does not clash with anything on those other hosts. |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
|
Updated the FAQ and "subnet used by Weave Net", and squashed. |
ping @abuehrle for doc review