mihomo
mihomo copied to clipboard
Clash.Meta WireGuard 无法正常使用
以CF Warp+生成的wg配置文件为例,我将相同的配置进行了测试,在Premium内核(Windows)里正常使用,结果在Meta内核(安卓端)(Windows未测试)里面出现了只能访问国内网站的情况,不知道问题出在哪里,希望有大佬看到能给解答一下。感谢!
https://github.com/MetaCubeX/ClashMetaForAndroid/issues/71
我也遇到这个问题了。wireguard节点在clash for Windows里正常,在clash Meta安卓里不走代理。
实测,同样的配置文件,WireGuard配置,电脑上正常,手机上不工作。
WireGuard配置,电脑上正常,手机上不工作
遇到了同样的问题 clash verge可以正常使用 cmfa全部直连
我也是这个问题,同样的配置,linux端clash for windows正常,android端无法使用
安卓已经升级到最新版内核,请前往https://github.com/MetaCubeX/ClashMetaForAndroid/releases/tag/Prerelease-alpha 下载使用尝试一下效果
port: 7890 allow-lan: true mode: rule log-level: info unified-delay: true global-client-fingerprint: chrome dns: enable: true listen: :53 ipv6: true enhanced-mode: fake-ip fake-ip-range: 198.18.0.1/16 default-nameserver:
- 223.5.5.5
- 8.8.8.8 nameserver:
- https://dns.alidns.com/dns-query
- https://doh.pub/dns-query fallback:
- https://1.0.0.1/dns-query
- tls://dns.google
fallback-filter:
geoip: true
geoip-code: CN
ipcidr:
- 240.0.0.0/4 proxies:
- {name: "☁️ CFWarp-A",type: wireguard,server: 162.159.195.1,port: 2408,ip: 172.16.0.2,private-key: kIV9Y6OOhkp41RZaVtCGY8c21J/qqyvUIeD80rdGb1o=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true}
- {name: "☁️ CFWarp-B",type: wireguard,server: 188.114.98.120,port: 4198,ip: 172.16.0.2,private-key: kIV9Y6OOhkp41RZaVtCGY8c21J/qqyvUIeD80rdGb1o=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true}
- {name: "☁️ CFWarp-C",type: wireguard,server: 162.159.192.47,port: 3476,ip: 172.16.0.2,private-key: KIV5EsjDNA3mF11Sfedfvy9Xk8man/9MXYdJQxwffEo=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true}
- {name: "☁️ CFWarp-D",type: wireguard,server: 162.159.192.217,port: 3476,ip: 172.16.0.2,private-key: SHVqHEGI7k2+OQ/oWMmWY2EQObbRQjRBdDPimh0h1WY=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true} proxy-groups:
- name: 🚀 节点选择
type: select
proxies:
- ♻️ 自动选择
- 🔯 故障转移
- ⚖️ 负载均衡
- DIRECT
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D
- name: ♻️ 自动选择
type: url-test
url: http://www.gstatic.com/generate_204
interval: 1000
tolerance: 200
proxies:
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D
- name: 🔯 故障转移
type: fallback
url: http://www.gstatic.com/generate_204
interval: 180
proxies:
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D
- name: ⚖️ 负载均衡
type: load-balance
proxies:
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D url: http://www.gstatic.com/generate_204 interval: 300 tolerance: 30 strategy: consistent-hashing commands:
- proxy-groups.⚖️ 负载均衡.proxies=[]proxyNames
- proxy-groups.0.proxies.0+⚖️ 负载均衡 rules:
- DOMAIN,clash.razord.top,DIRECT
- DOMAIN,yacd.haishan.me,DIRECT
- GEOIP,LAN,DIRECT
- GEOIP,CN,DIRECT
- MATCH,🚀 节点选择
安卓手机正常使用,不能使用是写法有问题。
我也有这个问题,电脑端部分配置如”reserved“配置后不正常。且必须打开远端DNS否则非常卡顿或无法加载。 最新版的安卓端(2024年1月27日)在同配置下仍然无法使用,但电脑端正常。
碰到类似问题,很头疼,定位半天,发觉如下问题;规则里一旦有涉及到geolocation,warp行为就很奇怪,貌似命中geolocation规则的地址会直连,没有命中规则才走warp
port: 7890 allow-lan: true mode: rule log-level: info unified-delay: true global-client-fingerprint: chrome dns: enable: true listen: :53 ipv6: true enhanced-mode: fake-ip fake-ip-range: 198.18.0.1/16 default-nameserver:
223.5.5.5
8.8.8.8 nameserver:
https://dns.alidns.com/dns-query
https://doh.pub/dns-query fallback:
https://1.0.0.1/dns-query
tls://dns.google fallback-filter: geoip: true geoip-code: CN ipcidr:
- 240.0.0.0/4 proxies:
{name: "☁️ CFWarp-A",type: wireguard,server: 162.159.195.1,port: 2408,ip: 172.16.0.2,private-key: kIV9Y6OOhkp41RZaVtCGY8c21J/qqyvUIeD80rdGb1o=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true}
{name: "☁️ CFWarp-B",type: wireguard,server: 188.114.98.120,port: 4198,ip: 172.16.0.2,private-key: kIV9Y6OOhkp41RZaVtCGY8c21J/qqyvUIeD80rdGb1o=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true}
{name: "☁️ CFWarp-C",type: wireguard,server: 162.159.192.47,port: 3476,ip: 172.16.0.2,private-key: KIV5EsjDNA3mF11Sfedfvy9Xk8man/9MXYdJQxwffEo=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true}
{name: "☁️ CFWarp-D",type: wireguard,server: 162.159.192.217,port: 3476,ip: 172.16.0.2,private-key: SHVqHEGI7k2+OQ/oWMmWY2EQObbRQjRBdDPimh0h1WY=,public-key: bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=,remote-dns-resolve: false,udp: true} proxy-groups:
name: 🚀 节点选择 type: select proxies:
- ♻️ 自动选择
- 🔯 故障转移
- ⚖️ 负载均衡
- DIRECT
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D
name: ♻️ 自动选择 type: url-test url: http://www.gstatic.com/generate_204 interval: 1000 tolerance: 200 proxies:
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D
name: 🔯 故障转移 type: fallback url: http://www.gstatic.com/generate_204 interval: 180 proxies:
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D
name: ⚖️ 负载均衡 type: load-balance proxies:
- ☁️ CFWarp-A
- ☁️ CFWarp-B
- ☁️ CFWarp-C
- ☁️ CFWarp-D url: http://www.gstatic.com/generate_204 interval: 300 tolerance: 30 strategy: consistent-hashing commands:
- proxy-groups.⚖️ 负载均衡.proxies=[]proxyNames
- proxy-groups.0.proxies.0+⚖️ 负载均衡 rules:
DOMAIN,clash.razord.top,DIRECT
DOMAIN,yacd.haishan.me,DIRECT
GEOIP,LAN,DIRECT
GEOIP,CN,DIRECT
MATCH,🚀 节点选择
安卓手机正常使用,不能使用是写法有问题。
多谢,clash meta for android中正常工作,虽然还是不懂原理是什么