• home > tools > NetTools > FirewallProxy >

    为什么选择Clash:放弃V2ray和shadowsocks

    Date:

    Clash 不是传统意义的代理服务端,它是:多协议代理核心(proxy core)相当于:一个流量调度中心

    首先放弃 shadowsocks,虽然非常简单,非常好用,奈何被Q的太厉害!

    V2ray的隐私层面做的非常好,但是我都是查技术资料——本来这些资料就应该公开访问,奈何被Q了!

    V2ray则更加侧重于支持多样化的加密方式,在安全性方面更具优势。毕竟人家采用了较为新的隐私保护技术,用户上网流量更加难以监控和追踪,敏感时期的可靠性更高。V2ray特别为用户支持和增加了很多自定义的配置选项,这样就可以根据实际需求进行优化和调整。

    V2ray的难度太大,放弃了……

    Clash性能优势

    Clash较为看重的是智能负载均衡和运行机制较为灵活,不用用户进行过多的操作,就能够根据网络环境的变化进行自适应设置,而且所支持的协议种类比较丰富,短时间内就可以快速切换,大大提高了网络效率和速度。


    Clash客户端

    FIClash,https://github.com/chen08209/FlClash

    这个虽然性能上不是那么强,但是英文flutter,多端UI/UX效果差不多

    Clash客户端配置:

    port: 8010
    socks-port: 8081
    redir-port: 8082
    mixed-port: 8084
    allow-lan: false
    mode: rule
    log-level: info
    external-controller: 127.0.0.1:9090
    
    proxies:
      - name: "demo"
        type: ss
        # 替换成自己ip
        server: 122.122.191.154
        port: 8080
        cipher: chacha20-ietf-poly1305
        password: yourPassword
        udp: true
    
    proxy-groups:
      - name: "Proxy"
        type: select
        proxies:
          - demo
          - DIRECT
    
    rule-providers:
      reject:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/reject.txt"
        path: ./ruleset/reject.yaml
        interval: 86400
    
      icloud:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/icloud.txt"
        path: ./ruleset/icloud.yaml
        interval: 86400
    
      apple:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/apple.txt"
        path: ./ruleset/apple.yaml
        interval: 86400
    
      google:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/google.txt"
        path: ./ruleset/google.yaml
        interval: 86400
    
      proxy:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/proxy.txt"
        path: ./ruleset/proxy.yaml
        interval: 86400
    
      direct:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/direct.txt"
        path: ./ruleset/direct.yaml
        interval: 86400
    
      private:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/private.txt"
        path: ./ruleset/private.yaml
        interval: 86400
    
      gfw:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/gfw.txt"
        path: ./ruleset/gfw.yaml
        interval: 86400
    
      tld-not-cn:
        type: http
        behavior: domain
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/tld-not-cn.txt"
        path: ./ruleset/tld-not-cn.yaml
        interval: 86400
    
      telegramcidr:
        type: http
        behavior: ipcidr
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/telegramcidr.txt"
        path: ./ruleset/telegramcidr.yaml
        interval: 86400
    
      cncidr:
        type: http
        behavior: ipcidr
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/cncidr.txt"
        path: ./ruleset/cncidr.yaml
        interval: 86400
    
      lancidr:
        type: http
        behavior: ipcidr
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/lancidr.txt"
        path: ./ruleset/lancidr.yaml
        interval: 86400
    
      applications:
        type: http
        behavior: classical
        url: "https://cdn.jsdelivr.net/gh/Loyalsoldier/clash-rules@release/applications.txt"
        path: ./ruleset/applications.yaml
        interval: 86400
    
    rules:
      - RULE-SET,applications,DIRECT
      - DOMAIN,clash.razord.top,DIRECT
      - DOMAIN,yacd.haishan.me,DIRECT
      - RULE-SET,private,DIRECT
      - RULE-SET,reject,REJECT
      - RULE-SET,icloud,DIRECT
      - RULE-SET,apple,DIRECT
      - RULE-SET,google,PROXY
      - RULE-SET,proxy,PROXY
      - RULE-SET,direct,DIRECT
      - RULE-SET,lancidr,DIRECT
      - RULE-SET,cncidr,DIRECT
      - RULE-SET,telegramcidr,PROXY
      - GEOIP,LAN,DIRECT
      - GEOIP,CN,DIRECT
      - MATCH,PROXY

    具体可以参考:
    https://github.com/Loyalsoldier/clash-rules?tab=readme-ov-file



    Clash服务端

    Clash 不是传统意义的代理服务端,它是:多协议代理核心(proxy core)

    相当于:一个流量调度中心

    超强分流能力(真正核心)

    可以:

    • 国内直连

    • OpenAI走美国

    • YouTube走日本

    • Netflix走专线

    可做“代理负载均衡”


    但是,在伪装上,还是:Trojan + Nginx 真正防封配置





    转载本站文章《为什么选择Clash:放弃V2ray和shadowsocks》,
    请注明出处:https://www.zhoulujun.cn/html/tools/NetTools/throughGFW/9766.html