The information contained in this article has been verified as up-to-date on the date of the original publication of the article. HashiCorp endeavors to keep this information up-to-date and correct, but it makes no representations or warranties of any kind, express or implied, about the ongoing completeness, accuracy, reliability, or suitability of the information provided.
All information contained in this article is for general information purposes only. Any reliance you place on such information as it applies to your use of your HashiCorp product is therefore strictly at your own risk.
Issue description:
When using Transparent Proxy on a service, Consul creates a virtual IP in the range 240.0.0.0/4.
In the unlikely event that this Virtual IP is used by other services in the same network, there can be an IP address conflict.
At the moment, this range is hardcoded in Consul and cannot be customized.
Suggested Solutions:
Currently we have an open Feature Request (FR) under Transparent proxy ip range is not configurable #22595 to make this IP range customizable.
Possible Workarounds:
- Not use this IP range in other services not managed by Consul on the network
- Use explicit upstreams instead of Transparent proxy.