#CLASHX SHADOWSOCKS INSTALL#

Port of HTTP(S) proxy server on the local end When a request, or say packet, comes in, Clash routes the packet to different remote servers (“nodes”) with either VMess, Shadowsocks, Snell, Trojan, SOCKS5 or HTTP protocol. In this chapter, we’ll cover the common features of Clash and how they should be used and configured.Ĭlash works by opening HTTP, SOCKS5, or the transparent proxy server on the local end. YAML is designed to be easy to be read, be written, and be interpreted by computers, and is commonly used for exact configuration files. You can now move forward to the next chapters of this wiki in which we’ll cover the configuration syntax of Clash.Ĭlash uses YAML, YAML Ain’t Markup Language, for configuration files.

#CLASHX SHADOWSOCKS INSTALL#

$ go install binary is built under $GOPATH/bin You can either grab the pre-built binaries of Clash from or build locally.Ĭlash requires Golang 1.17 or a higher version. TUN mode on macOS, Linux and Windows. Doc.Comprehensive HTTP RESTful API controller.

Deploy Clash on your Internet gateway with iptables.

Remote providers, allowing users to get node lists remotely instead of hardcoding in config.

Supports automatic fallback, load balancing or auto select node based off latency

Remote groups allow users to implement powerful rules.

Rules based off domains, GEOIP, IPCIDR or Process to forward packets to different nodes.

Built-in DNS server that aims to minimize DNS pollution attack impact, supports DoH/DoT upstream and fake IP.

VMess, Shadowsocks, Trojan, Snell protocol support for remote connections.

Local HTTP/HTTPS/SOCKS server with authentication support.

Clashx shadowsocks