search

ViRb3 / wgcf

🚤 Cross-platform, unofficial CLI for Cloudflare Warp
MIT License
6.31k stars 699 forks source link

wgcf cannot be used anymore? #367

Closed zstdadi closed 11 months ago

zstdadi commented 11 months ago

CF has added some private bits in wireguard protocol, so wgcf cannot be used anymore？

./wgcf register ./wgcf generate cp wgcf-profile.conf /etc/wireguard/wgcf.conf wg-quick up wgcf

After run "wg-quick up wgcf", wgcf NIC is up, 172.16.0.2 is up, but cann't ping 172.16.0.1, cann't connect ipv4 network.

refer this: https://iedon.com/2023/07/13/992.html

ViRb3 commented 11 months ago

Works fine here. You are likely in a high abuse region where wgcf is blocked. Check #158.

zstdadi commented 11 months ago

It's nothing with abuse. cannot use wireguard with wgcf'config, but warp-cli connect is OK.

refer this: https://iedon.com/2023/07/13/992.html

有关为何第三方客户端的 wgcf 无法使用(无法 handshake) 的说法有这么一个：虽然 Warp 客户端使用了 WireGuard 协议，但是在 WireGuard 协议中的 Reserved 字段加入了 特殊值①，导致 Cloudflare 可以检测是否是官方客户端。最近看到 GitHub 中的 一些脚本② 已经开始尝试魔改 WireGuard Go，来支持指定 Reserved 字节，不过本文撰写时，尚无稳定可用的发布，尚处于开发中的样子。

ViRb3 commented 11 months ago

The private/reserved bits are only checked in high abuse regions. As I said, I verified yesterday and wgcf works great for me in two different western countries without the need of those bits. For reasons explained in the issue linked above, I'm afraid that I cannot help with bypassing this limitation.

zstdadi commented 11 months ago

Thank you for your help!