Clarification for serf_wan documentation (#4459)

* updates docs for agent options

trying to add a little more clarity to suggestion that folks should use
port 8302 for both LAN and WAN comms

* website: clarify language for serf wan port behavior
This commit is contained in:
Jack Pearkes 2018-08-02 10:25:25 -07:00 committed by GitHub
parent dcd7d9b015
commit 5c993a3f5f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 5 deletions

View File

@ -1451,10 +1451,9 @@ port.
* Serf LAN (Default 8301). This is used to handle gossip in the LAN. * Serf LAN (Default 8301). This is used to handle gossip in the LAN.
Required by all agents. TCP and UDP. Required by all agents. TCP and UDP.
* Serf WAN (Default 8302). This is used by servers to gossip over the * Serf WAN (Default 8302). This is used by servers to gossip over the WAN, to
WAN to other servers. TCP and UDP. As of Consul 0.8, it is recommended to other servers. TCP and UDP. As of Consul 0.8 the WAN join flooding feature requires
enable connection between servers through port 8302 for both TCP and UDP on the Serf WAN port (TCP/UDP) to be listening on both WAN and LAN interfaces. See also:
the LAN interface as well for the WAN Join Flooding feature. See also:
[Consul 0.8.0 CHANGELOG](https://github.com/hashicorp/consul/blob/master/CHANGELOG.md#080-april-5-2017) and [GH-3058](https://github.com/hashicorp/consul/issues/3058) [Consul 0.8.0 CHANGELOG](https://github.com/hashicorp/consul/blob/master/CHANGELOG.md#080-april-5-2017) and [GH-3058](https://github.com/hashicorp/consul/issues/3058)
* HTTP API (Default 8500). This is used by clients to talk to the HTTP * HTTP API (Default 8500). This is used by clients to talk to the HTTP