Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure serf_wan and serf_lan on different addresses #2007

Closed
jorgemarey opened this issue Apr 29, 2016 · 2 comments · Fixed by #2468
Closed

Configure serf_wan and serf_lan on different addresses #2007

jorgemarey opened this issue Apr 29, 2016 · 2 comments · Fixed by #2468
Labels
type/enhancement Proposed improvement or new feature

Comments

@jorgemarey
Copy link
Contributor

I was trying to bind serf_wan on the public address of the servers and serf_lan on the private, but I don't see any way of doing this.

Is there any way to configure these two on different addresses?

@slackpad
Copy link
Contributor

Hi @jorgemarey not currently, sorry about that.

@slackpad slackpad added type/enhancement Proposed improvement or new feature easy labels Aug 10, 2016
@moofish32
Copy link
Contributor

@jorgemarey -- I don't have a test environment up and the failing tests do not appear related to my change. Is there anyway you can help test by building locally?

moofish32 added a commit to moofish32/consul that referenced this issue Oct 10, 2016
…an and lan bind addresses

* updating documentation for serf wan and lan options
Fixes hashicorp#2007
slackpad added a commit that referenced this issue Nov 3, 2016
* * adding cli config and config file support for specifying the serf wan and lan bind addresses
* updating documentation for serf wan and lan options
Fixes #2007

* Cleans up some small things from #2380.

* Uses the bind default for the agent test for Serf WAN and LAN.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Proposed improvement or new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants