-
Notifications
You must be signed in to change notification settings - Fork 438
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
util.privateBlocks contains loopback address range #102
Comments
- prefer private networks over link-local and loopback addresses. - fixes hashicorp#102
- prefer private networks over link-local and loopback addresses. - fixes hashicorp#102
- when automatically determining the advertiseAddr use a private IP address if available over a loopback adddress - fixes hashicorp#102
@sean- any thoughts on this one? |
This is the express reason why Lines 25 to 34 in 9800c50
From a correctness perspective, there are a few possible solutions, some more correct than others, but all solutions involve the use of
@woodsaj , can you run the following few commands and see if they're correct for your environment:
|
looks to work correctly. :) |
Ha!, excellent. Thank you for that point of validation. @slackpad, your call now. :) I'm game for PRing this at some point unless you beat me to it. As far as impact, Consul already has a vendor dependency on |
Yep I'll pull this through Serf and Consul - /cc @dadgar for Nomad. |
Should be fixed at this level by #108. |
When determining the advertiseAddr the IP of each network interface is examined to see if it is a privateIP.
The set of privateIp ranges that the addresses are evaluated against include the loopback address range (127.0.0.0/8).
When iterating over the interface addresses, the loopback address (127.0.0.1) is always returned first on my system (Ubuntu 14.04- 3.13.0-100-generic #147-Ubuntu).
As a result, 127.0.0.1 is always selected as the privateIP address to advertise to peers, which results in the peers being unable to communicate with each other.
I really think that the loopback range should be removed from the privateBlocks or at the very least moved to the end of the slice so that all other private Ip ranges are checked first.
The text was updated successfully, but these errors were encountered: