cloudflare / cloudflare/cloudflared

💡 Allow configuration of a source IP pool to ensure there are enough ports to proxy large numbers of requests

Open
#846 3 comments 0 reactions 0 assignees View on GitHub
Priority: Normal Type: Feature Request
Dominant language
Go
Stars
15.6k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

**Describe the feature you'd like**
We would like to be able to configure cloudflared to use a pool of IPs when communicating with the origin server to avoid exhausting all ports between Established and Time-Wait connections.

We receive a large number of requests per second across two load balancers. Further, we can receive 10s of thousands of requests in a single second during a DDoS event. Before moving to the tunnel, incoming requests to the load balancers originated from a fairly large number of source IPs in CloudFlare's IP blocks (https://www.cloudflare.com/ips/). After moving to the tunnel, we only have one source IP per cloudflared node.

**Describe alternatives you've considered**
We have currently programmed our load-balancers to have 10 IP addresses each, instead of one, to ensure a large space of IP/port pairs. This has increased the complexity of our load balancer configuration, and caused additional complexity in our IP configuration. It would be simpler and more maintainable for us to use a pool of IPs at the cloudflare tunnel node, and return our load balancer's to their original configuration. Further, we would not have to reconfigure our load balancer's other virtual hosts as well, which we have not yet done.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.