WARP is Cloudflare’s own VPN service, and it’s hosted on their servers. cloudflared is supposed to be a way to access your own resources, whilst on the WARP network. Neither were designed to let you self host a VPN.
WARP’s design considerations with allowing servers to see the original client’s IP may not be for you, which is why I assume you want to host your own service. Creating a VPN like that wouldn’t be using Cloudflare’s service at all, but rather would be competing against it.
If you still want to create your own VPN that’s similar to WARP, I’d suggest reading this blog post from Cloudflare, explaining how WARP is made under the hood. You can use WireGuard / Boringtun (Cloudflare’s implementation of WireGuard) like they have in WARP, or you can use something like OpenVPN.
There’s actually a project by Google called Outline, which is supposed to make it really easy to setup small VPNs for yourself on cloud providers like AWS.
Actually I have no plan of self hosting vpn, warp is enough but i am curious , i know the warp doesn’t show or give static ip but when i connect to warp it connects me to vpc so i why I am not using the VPC public ip.
Secondly can a resource inside the VPC communicate with local machine when using cloudflare warp with tunnel. Local machine to vpc works what about vpc to local machine
What will be the private ip of my local machine when in the VPC ?
A virtual private cloud (VPC) running through cloudflared is quite literally just a network that’s being exposed to WARP. If you want your local machine to be accessible, you can just run cloudflared on your local machine, although I really can’t find see a practical use case for this.