如果想 youtube 不走 warp 只让 google 走 warp
编辑 config.json
如果你是用的我的脚本 https://github.com/crazypeace/V2ray_VLESS_WebSocket_TLS_CaddyV2
在让
因为
* 根据你自己的小鸡的实际情况, 原生出站是
{"type": "field","outboundTag": "force-ipv6", // force-ipv4 // socks5-warp"domain": ["geosite:youtube"] // ***},{"type": "field","outboundTag": "socks5-warp", // force-ipv4 // socks5-warp"domain": ["geosite:google"] // ***},
能直接这么写的原因是, 在
{"protocol": "freedom","settings": {"domainStrategy": "UseIPv4"},"tag": "force-ipv4"},{"protocol": "freedom","settings": {"domainStrategy": "UseIPv6"},"tag": "force-ipv6"},
==============
参考
rules: [RuleObject]
对应一个数组,数组中每一项是一个规则。对于每一个连接,路由将根据这些规则依次进行判断,当一个规则生效时,即将这个连接转发至它所指定的 outboundTag(或 balancerTag,V2Ray 4.4+)。当没有匹配到任何规则时,流量默认被转发至第一个 outbound。
source: https://www.v2fly.org/config/routing.html#routingobject
后记
根据对
include:androidinclude:blogspotinclude:dartinclude:fastlaneinclude:flutterinclude:golanginclude:google-adsinclude:google-registryinclude:google-scholarinclude:kaggleinclude:opensourceinsightsinclude:polymerinclude:v8include:youtube
也就是说,如果你让 google 躲开人机验证以后,觉得哪部分受拖累比较慢,比如 blogspot,可以用同样的原理。
{"type": "field","outboundTag": "force-ipv6", // force-ipv4 // socks5-warp"domain": ["geosite:youtube", "geosite:blogspot"] // ***},
此评论已被作者删除。
回复删除此评论已被作者删除。
回复删除