bug+enhancement req: Summary of wgcf vs the "official" warp-cli from cloudflare

[succeedmr123]

Dear,

here is a summary diff of bugs/ regressions in fucntionality vs. the official client and the user can not find a way to enable them in wgcf. Please advise. Thank you very much in advance in the name of many users looking to contrib, help, or just use these functionalities

1. Warp is off although the steps to install the key were followed. There is no instruction to turn warp on within this doc. Why?
2. What we can witness in the official Linux Cloudflare clent are 4 modes: Warp, warp+DoH, warp+DoT, HTTPS+DoT, HTTPS+DoH. There is no menition in docs here how to enable these. That indirectly implies that these API functionality is not implemented yet
3. What can be noticed is that at the time of writing Cloudflare now allows functionalities such as split tunnel , Teams, Cloudflare Zero Trust mode.. things are developing. On the other hand, what we can find here is warp or DoH only. What is desirable is to closely autofollow and autoimplement full cloudflare functionalities on an API level as it changes. As it can be witnessed, it seems to be doable. If Victor needs any help with this, I am quite willing to help out bring it where it needs to be.

Thanks for implementing the redesigned client at all in the first place, we should and are grateful in for the effort in any case!

P.S:
In case anyone asks "then why not to use the official client" ...in that case, we should point towards doing a bit more thorough assesment of an app;

• few very alarming things privacy and security wise would emerge
• that app as such need to be installed in your production system which is insofar unacceptable in the present form
• fully free+open source app may be freely asessed by security analysts for privacy and security intrusiveness

That about sums it up. thanks all for your ATTN:

[diwu1989]

The official cloudflare client runs Wireguard in user-space, whereas the wgcf configuration can use the kernel mode Wireguard driver.

The cloudflare official client has some more robust failover behavior from personal usage, and I use it on Mac & Windows for convenience, but on servers that need Warp access, I use wgcf with kernel wireguard for performance and ease.

It's also possible to use the wgcf profile with a OpenWRT router to provide full house Warp at the router level.

[dongle-the-gadget]

Using Cloudflare's client also handles server routing, so if Cloudflare connects you with a re-routed server, the official client is currently the only way to go (unless if you modify unofficial clients to also handle routing).