-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clash 网易云规则 #624
Comments
DOMAIN-SUFFIX,music.126.net,DIRECT 完事 |
clash支持 user agent么 |
前三个规则就够了 |
我就两条,不过只适用在win和android下,mac没去研究,主要是方便啊,代理整个程序的所有流量
|
@johnshuxian 在,这样网易云全部的流量都会走网易云解锁节点,图片加载不出来,部分网易云的歌听不了,你没有这种现象么 |
我这边都是正常的呀 |
@johnshuxian 可不可以交流交流,https://gist.githubusercontent.com/LittleRey/8db43358821177d0ddd2bd047127914a/raw/Netease.yaml 你试试看这个配置可以用么,我有没有写错误 |
解决了吗?代理整个程序不实用啊,一堆图片加载不出来,严重影响使用体验。clash不支持ua是真的难搞,用cidr过滤,一段时间就失效,每次都调试,一个个ip去试,太费劲了。 |
@redn3ck |
@gqbre 现在在探讨安卓clash的规则,兄弟,不是macOS |
@redn3ck 不一样可以试? |
我试过了的,是不行的,安卓只用domain-suffix是不能完全过滤的,所以才有了cidr |
把组面替换成想要在的分组即可,这个操作应该会吧所有的音乐的的链接都进行过滤 |
现在的话,可以使用 PROCESS-NAME
|
@gqbre 大佬,这个在macos也不管用呀 |
很久没用了,等大佬 |
![]() 有用的呀,规则是对的 |
使用 "http" or "sock5"
Clash NeteaseMusic Rules
DOMAIN,p1.music.126.net,DIRECT
DOMAIN,p2.music.126.net,DIRECT
DOMAIN,p3.music.126.net,DIRECT
DOMAIN,p4.music.126.net,DIRECT
DOMAIN,p5.music.126.net,DIRECT
DOMAIN,p6.music.126.net,DIRECT
DOMAIN,p7.music.126.net,DIRECT
DOMAIN,p8.music.126.net,DIRECT
DOMAIN,p9.music.126.net,DIRECT
DOMAIN,p10.music.126.net,DIRECT
DOMAIN-SUFFIX,163yun.com,Netease
DOMAIN-SUFFIX,music.163.com,Netease
DOMAIN-SUFFIX,music.126.net,Netease
DOMAIN-SUFFIX,api.iplay.163.com,Netease
DOMAIN-SUFFIX,apm.music.163.com,Netease
DOMAIN-SUFFIX,apm3.music.163.com,Netease
DOMAIN-SUFFIX,interface.music.163.com,Netease
DOMAIN-SUFFIX,interface3.music.163.com,Netease
DOMAIN-SUFFIX,mam.netease.com,Netease
DOMAIN-SUFFIX,hz.netease.com,Netease
IP-CIDR,39.105.63.80/32,Netease
IP-CIDR,45.254.48.1/32,Netease
IP-CIDR,47.100.127.239/32,Netease
IP-CIDR,59.111.21.14/31,Netease
IP-CIDR,59.111.179.214/32,Netease
IP-CIDR,59.111.181.38/32,Netease
IP-CIDR,59.111.181.60/32,Netease
IP-CIDR,59.111.160.195/32,Netease
IP-CIDR,59.111.160.197/32,Netease
IP-CIDR,59.111.181.35/32,Netease
IP-CIDR,59.111.238.29/32,Netease
IP-CIDR,101.71.154.241/32,Netease
IP-CIDR,103.126.92.132/32,Netease
IP-CIDR,103.126.92.133/32,Netease
IP-CIDR,112.13.119.17/32,Netease
IP-CIDR,112.13.122.1/32,Netease
IP-CIDR,115.236.118.33/32,Netease
IP-CIDR,115.236.121.1/32,Netease
IP-CIDR,118.24.63.156/32,Netease
IP-CIDR,193.112.159.225/32,Netease
IP-CIDR,223.252.199.66/32,Netease
IP-CIDR,223.252.199.67/32,Netease
The text was updated successfully, but these errors were encountered: