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

Add IPv6 private address ranges #2825

Conversation

charles-dyfis-net
Copy link

Presently, Consul is only aware of IPv4 private address ranges; for IPv6, it isn't aware of any of:

  • The loopback address
  • Link-local address ranges (though other work is needed before Consul can successfully use these).
  • Site-local address ranges
  • Unique local addresses (modern replacement for site-local addresses, which were inadequately defined).

This patch adds these four categories.

Presently, Consul is only aware of IPv4 private address ranges; for IPv6, it isn't aware of any of:

- The loopback address
- Link-local address ranges (though other work is needed before Consul can successfully use these).
- Site-local address ranges
- Unique local addresses (modern replacement for site-local addresses, which were inadequately defined).

This patch adds these four categories.
@slackpad
Copy link
Contributor

Hi @charles-dyfis-net thanks for opening a PR. I don't think this code should be in use any more once @sean- merges his pending change to switch over to https://github.com/hashicorp/go-sockaddr.

@charles-dyfis-net
Copy link
Author

Do you know what the ETA is on that? In the interim, I have nodes incorrectly being classified as WAN.

@sean-
Copy link
Contributor

sean- commented Apr 28, 2017

@charles-dyfis-net Can you run a problematic Consul node with the following two options:

-client={{GetPrivateIP}} -bind={{GetPrivateIP}}

and let me know if that works correctly for you without this patch?

@charles-dyfis-net
Copy link
Author

Not at all -- GetPrivateIP is resolving to an IPv4 address on a completely different interface than that used for cluster interconnect.

@sean-
Copy link
Contributor

sean- commented May 1, 2017

If you know the interface name in advance, you could use {{GetInterfaceIP "net1"}} where net1 is the interface name of your cluster interconnect link. Does that work for you, @charles-dyfis-net ?

@magiconair
Copy link
Contributor

I think I can add this as part of #3480 since I've moved that code around anyway.

@magiconair magiconair self-assigned this Sep 20, 2017
slackpad pushed a commit that referenced this pull request Sep 25, 2017
* new config parser for agent

This patch implements a new config parser for the consul agent which
makes the following changes to the previous implementation:

 * add HCL support
 * all configuration fragments in tests and for default config are
   expressed as HCL fragments
 * HCL fragments can be provided on the command line so that they
   can eventually replace the command line flags.
 * HCL/JSON fragments are parsed into a temporary Config structure
   which can be merged using reflection (all values are pointers).
   The existing merge logic of overwrite for values and append
   for slices has been preserved.
 * A single builder process generates a typed runtime configuration
   for the agent.

The new implementation is more strict and fails in the builder process
if no valid runtime configuration can be generated. Therefore,
additional validations in other parts of the code should be removed.

The builder also pre-computes all required network addresses so that no
address/port magic should be required where the configuration is used
and should therefore be removed.

* Upgrade github.com/hashicorp/hcl to support int64

* improve error messages

* fix directory permission test

* Fix rtt test

* Fix ForceLeave test

* Skip performance test for now until we know what to do

* Update github.com/hashicorp/memberlist to update log prefix

* Make memberlist use the default logger

* improve config error handling

* do not fail on non-existing data-dir

* experiment with non-uniform timeouts to get a handle on stalled leader elections

* Run tests for packages separately to eliminate the spurious port conflicts

* refactor private address detection and unify approach for ipv4 and ipv6.

Fixes #2825

* do not allow unix sockets for DNS

* improve bind and advertise addr error handling

* go through builder using test coverage

* minimal update to the docs

* more coverage tests fixed

* more tests

* fix makefile

* cleanup

* fix port conflicts with external port server 'porter'

* stop test server on error

* do not run api test that change global ENV concurrently with the other tests

* Run remaining api tests concurrently

* no need for retry with the port number service

* monkey patch race condition in go-sockaddr until we understand why that fails

* monkey patch hcl decoder race condidtion until we understand why that fails

* monkey patch spurious errors in strings.EqualFold from here

* add test for hcl decoder race condition. Run with go test -parallel 128

* Increase timeout again

* cleanup

* don't log port allocations by default

* use base command arg parsing to format help output properly

* handle -dc deprecation case in Build

* switch autopilot.max_trailing_logs to int

* remove duplicate test case

* remove unused methods

* remove comments about flag/config value inconsistencies

* switch got and want around since the error message was misleading.

* Removes a stray debug log.

* Removes a stray newline in imports.

* Fixes TestACL_Version8.

* Runs go fmt.

* Adds a default case for unknown address types.

* Reoders and reformats some imports.

* Adds some comments and fixes typos.

* Reorders imports.

* add unix socket support for dns later

* drop all deprecated flags and arguments

* fix wrong field name

* remove stray node-id file

* drop unnecessary patch section in test

* drop duplicate test

* add test for LeaveOnTerm and SkipLeaveOnInt in client mode

* drop "bla" and add clarifying comment for the test

* split up tests to support enterprise/non-enterprise tests

* drop raft multiplier and derive values during build phase

* sanitize runtime config reflectively and add test

* detect invalid config fields

* fix tests with invalid config fields

* use different values for wan sanitiziation test

* drop recursor in favor of recursors

* allow dns_config.udp_answer_limit to be zero

* make sure tests run on machines with multiple ips

* Fix failing tests in a few more places by providing a bind address in the test

* Gets rid of skipped TestAgent_CheckPerformanceSettings and adds case for builder.

* Add porter to server_test.go to make tests there less flaky

* go fmt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants