1#
A group of conscientious CF!
Access address: https://1.1.1.1/
2#
Why have this idea, because can freeload without paying
Some sites have stricter IP restrictions, and cloud vendors' IPs are occasionally whitelisted. Blocking IPs is faster, so I just don't want to be blocked.
I found that the IPs provided by CF are relatively clean, which is quite comfortable. 
3#
clash#
I use clash locally because I need to take over my entire network card traffic. Here is an example using clash:
- Open clash's tun mode and select global proxy.
- Open clash's system proxy mode to proxy CF.
- Check the listening port of clash, which is 7890 in my case.
Cloudflare#
- Enable Cloudflare's proxy mode.
- Enter the port of clash.
You can connect now.
The effect is as follows: 
Notes#
- Is using a secondary proxy not laggy?
No, it's not laggy. Watching 2k videos on YouTube is not a problem.
- Why not connect directly to CF?
I found an interesting problem during testing. If you only connect to CF, it will directly display your real physical location. 
I haven't actually studied why this happens, but there are reference examples online:
https://blog.skk.moe/post/something-about-cf-warp/
Update on May 10th:
The reason for the leakage of the real physical location is IPv6. 
Using the test address provided by CF, you can find that the third line of the IP is your real IP. 
The IPv4 here does go through CF in the United States, but after enabling warp, an IPv6 is used, which is unprotected, it's that simple.
So when testing, if you can still get the real address after enabling warp, it is mostly because your IPv6 is prioritized.
The fix is also simple, disable IPv6.
- Other ways to play
Warp can be used to unlock routes, and there are many ways to unlock IP for VPS. Please search for them yourself. I won't explain them here.
5#
The best solution is to use warp for the VPS, and then the VPS forms a proxy, using the chain proxy of clash to hide the IP.
