-
Notifications
You must be signed in to change notification settings - Fork 85
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
Cloudflare WARP #173
Comments
Yes this could be integrated as a CI process. PR welcome. |
For an example of how this can be done see https://github.com/X4BNet/lists_vpn/blob/main/.github/workflows/fetch-protonvpn.yml |
So which IPs would be the WARP IPs? |
It can be any, why don't we list all Cloudflare Subnets for Datacenters? Because I'm using WARP and it's assigning all the time this subnet 104.28.207.0/24 |
I don't think this is a suggestible idea. Many users who us this list likely also use cloudflare. If they were to simply block the ips then all of cloudflare wouldn't be usable for users. |
yes but Cloudflare passes the real visitor IP (if you are using Cloudflare as your CDN) |
Hello,
Cloudflare WARP IPs are missing and I believe it's a big problem.
https://bgp.tools/as/13335#prefixes
You can clearly see they are not matching with the IPs Cloudflare uses for proxified traffic with their service https://www.cloudflare.com/ips-v4/#
Else, this could be simply integrated with the Datacenter list only.
The text was updated successfully, but these errors were encountered: