ViRb3
Generated config doesn't use Warp=plus even if I have an active subscription.
Generated config doesn't use warp=plus even if I have an active subscription. I can also confirm that my device was already added properly into my account. When I try to use wgcf's generated config, both trace command and https://cloudflare.com/cdn-cgi/trace says warp=on but if I'll use the official Warp app on PC, it will say warp=plus.
I think this has something to do with the new MASQUE implementation.
On the warp client it'll choose MASQUE instead of Wireguard and Warp=plus
It's been a while since this happened, and some people, like us, are experiencing the same issue and have reported it.
https://github.com/ViRb3/wgcf/issues/85#issuecomment-2620752663 https://github.com/ViRb3/wgcf/issues/85#issuecomment-2600530247 https://github.com/ViRb3/wgcf/issues/85#issuecomment-2621709675
No one knows why Cloudflare removed this feature from WireGuard. I even sent feedback, but unfortunately, Cloudflare doesn't respond easily.
I tried porting the Linux warp client yesterday by extracting the binaries from the .Deb file and put it on OpenWRT. Unfortunately the binaries are compiled expecting to have the Ubuntu C libraries available so there's a bunch of symbols that can't be interpreted. It seems to me the only fix is to somehow get MASQUE to work outside of the warp client, or get a version compiled for OpenWRT.
Hey @iamromulan,
I managed to reimplement the Cloudflare MASQUE protocol and open-sourced some basic proof of concepts. It's not yet production ready as the tunnel is closed if inactive by Cloudflare. But if you use it for regular browsing, it works fine for me in SOCKS5 mode.
Unfortunately it requires a userspace client...
Find it here: https://github.com/Diniboy1123/usque
It would be good to test if the change to warp=on is just cosmetic or if better routes are indeed only available on masque
@totoCZ I did some testing and unfortunately it doesn't seem to be cosmetic only. So I tried to make my masque client stable for production use. So far I am getting decent routes.
I'll have to give Usque a try. Hopefully tonight lol
Gonna attempt to use it in an OpenWRT environment. A cellular module that runs OpenWRT on the modem itself. The Quectel RM551E-GL
Your WARP+ license is valid, but your Linux device is registering as a "child" under your WARP+ account, and Cloudflare does not activate WARP+ on child devices, even if the license key is correct.
Your WARP+ license is valid, but your Linux device is registering as a "child" under your WARP+ account, and Cloudflare does not activate WARP+ on child devices, even if the license key is correct.
so how to fix ? change registration "child" to another or what ?
I'm having the same issue also. It only produces "warp=on" not "warp=plus"
cloudflare says the issue is cosmetic on their end (not correctly switching "on" to "plus" for wiregaurd), traffic still flows through plus - https://community.cloudflare.com/t/1-1-1-1-with-wireguard-not-masque-is-not-picking-up-warp-unlimited-subscription/797012/9
Today I tried it again. I removed the registered device from the Cloudflare Warp account, remove the wgcf-account.toml file and re-do all the steps to register a new client and bind the license key. After all that I was able to generate a profile that let me connect to identify as warp=plus. So the issue seemed to be fixed at the Cloudflare's end, and we only need to recreate the device.
So the issue seemed to be fixed at the Cloudflare's end, and we only need to recreate the device.
I followed your steps to remove and re-create, but still got warp=on. I then went one step further and generated a new license key on the official app before re-creating, and it worked!
Closing this as a duplicate of #85. Please check my latest post there for updates.
