Hacker News Reader

Comment by woofcat | Hacker News Reader

I wonder if when accessing a Cloudflare website if they'll be presenting the website owner with the original origin IP, or passing along the 1.1.1.1 endpoint IP addressed when staying within their network.

View on HN

We'll be presenting the original IP.

If you wish to block or otherwise take action on, e.g., malicious traffic from the IP being used to connect to Warp, you'll be able to do so.

Is this in X-Forwarded-For?

CF-Connecting-IP is what we recommend using.

See https://support.cloudflare.com/hc/en-us/articles/200170986-H... for details.

Which presumably only works if your site is using Cloudflare? Since you wouldn't be MITMing SSL in order to inject this header?

This is correct. It's significantly harder to inject the origin IP into a TCP stream. We have ways [1] of doing it, but it requires some coordination on both sides.

1- https://blog.cloudflare.com/mmproxy-creative-way-of-preservi...

Have you considered enabling this out of band? For example as a network administrator I could verify a CIDR block and receive a real time stream of 5-tuples (err, 7-tuples with the proxy?) destined to my network.

How can they do this?

Are Cloudflare going to be able to decrypt the TLS sessions running over their VPN between me and end-sites, so they can insert this additional HTTP header?

Doesn’t sound feasible.

When most of those sites are hosted by Cloudflare, they already decrypt the TLS session at their load balancers before forwarding the request to the remote endpoint.

And then at some point CF protected sites can dis- or enable to only allow warp VPN users per filter?

Reply on news.ycombinator.com