mihomo/README.md

235 lines
7.3 KiB
Markdown
Raw Normal View History

2018-06-23 00:44:28 +08:00
<h1 align="center">
<img src="https://github.com/Dreamacro/clash/raw/master/docs/logo.png" alt="Clash" width="200">
2019-02-11 15:55:17 +08:00
<br>Clash<br>
2018-06-23 00:44:28 +08:00
</h1>
<h4 align="center">A rule-based tunnel in Go.</h4>
2018-06-23 00:44:28 +08:00
<p align="center">
<a href="https://travis-ci.org/Dreamacro/clash">
<img src="https://img.shields.io/travis/Dreamacro/clash.svg?style=flat-square"
alt="Travis-CI">
</a>
<a href="https://goreportcard.com/report/github.com/Dreamacro/clash">
2019-02-11 15:55:17 +08:00
<img src="https://goreportcard.com/badge/github.com/Dreamacro/clash?style=flat-square">
2018-06-23 00:44:28 +08:00
</a>
<a href="https://github.com/Dreamacro/clash/releases">
<img src="https://img.shields.io/github/release/Dreamacro/clash/all.svg?style=flat-square">
</a>
</p>
2018-06-10 22:50:03 +08:00
## Features
2018-11-08 20:14:57 +08:00
- HTTP/HTTPS and SOCKS protocol
2018-06-10 22:50:03 +08:00
- Surge like configuration
- GeoIP rule support
2018-09-16 23:08:04 +08:00
- Support Vmess/Shadowsocks/Socks5
2018-08-14 18:06:56 +08:00
- Support for Netfilter TCP redirect
2018-06-10 22:50:03 +08:00
## Install
You can build from source:
```sh
go get -u -v github.com/Dreamacro/clash
```
2018-06-15 17:49:14 +08:00
Pre-built binaries are available: [release](https://github.com/Dreamacro/clash/releases)
2019-02-27 01:02:43 +08:00
Requires Go >= 1.12.
2018-06-10 22:50:03 +08:00
2019-03-30 14:20:04 +08:00
Checkout Clash version:
```sh
clash -v
```
2018-06-15 00:35:33 +08:00
## Daemon
Unfortunately, there is no native elegant way to implement golang's daemon.
So we can use third-party daemon tools like pm2, supervisor, and so on.
2018-06-18 11:31:49 +08:00
In the case of [pm2](https://github.com/Unitech/pm2), we can start the daemon this way:
2018-06-15 00:35:33 +08:00
```sh
pm2 start clash
```
2018-06-18 11:31:49 +08:00
If you have Docker installed, you can run clash directly using `docker-compose`.
[Run clash in docker](https://github.com/Dreamacro/clash/wiki/Run-clash-in-docker)
2018-06-10 22:50:03 +08:00
## Config
2018-10-17 00:51:04 +08:00
The default configuration directory is `$HOME/.config/clash`
The name of the configuration file is `config.yml`
If you want to use another directory, you can use `-d` to control the configuration directory
For example, you can use the current directory as the configuration directory
```sh
clash -d .
```
2018-06-10 22:50:03 +08:00
Below is a simple demo configuration file:
2018-10-03 12:25:24 +08:00
```yml
# port of HTTP
port: 7890
# port of SOCKS5
socks-port: 7891
2018-06-10 22:50:03 +08:00
2018-11-08 20:14:57 +08:00
# redir port for Linux and macOS
2018-10-17 00:51:04 +08:00
# redir-port: 7892
2018-10-03 12:25:24 +08:00
allow-lan: false
2018-10-17 00:51:04 +08:00
# Rule / Global/ Direct (default is Rule)
2018-10-03 12:25:24 +08:00
mode: Rule
# set log level to stdout (default is info)
2018-12-05 21:26:04 +08:00
# info / warning / error / debug / silent
2018-10-03 12:25:24 +08:00
log-level: info
2018-08-12 04:22:14 +08:00
2018-06-18 11:31:49 +08:00
# A RESTful API for clash
2018-10-03 12:25:24 +08:00
external-controller: 127.0.0.1:9090
# you can put the static web resource (such as clash-dashboard) to a directory, and clash would serve in `${API}/ui`
# input is a relative path to the configuration directory or an absolute path
# external-ui: folder
2018-10-17 00:51:04 +08:00
# Secret for RESTful API (Optional)
2018-10-29 20:25:13 +08:00
# secret: ""
2018-10-17 00:51:04 +08:00
# experimental feature
experimental:
ignore-resolve-fail: true # ignore dns reslove fail, default value is true
2019-02-11 15:55:17 +08:00
# dns:
2018-12-05 21:52:31 +08:00
# enable: true # set true to enable dns (default is false)
# ipv6: false # default is false
# listen: 0.0.0.0:53
# enhanced-mode: redir-host
# nameserver:
# - 114.114.114.114
# - tls://dns.rubyfish.cn:853 # dns over tls
# fallback: # concurrent request with nameserver, fallback used when GEOIP country isn't CN
# - tcp://1.1.1.1
2018-12-05 21:26:04 +08:00
2018-10-03 12:25:24 +08:00
Proxy:
2018-06-18 11:31:49 +08:00
2018-10-03 12:25:24 +08:00
# shadowsocks
2018-06-15 00:35:33 +08:00
# The types of cipher are consistent with go-shadowsocks2
# support AEAD_AES_128_GCM AEAD_AES_192_GCM AEAD_AES_256_GCM AEAD_CHACHA20_POLY1305 AES-128-CTR AES-192-CTR AES-256-CTR AES-128-CFB AES-192-CFB AES-256-CFB CHACHA20-IETF XCHACHA20
2018-10-17 00:51:04 +08:00
# In addition to what go-shadowsocks2 supports, it also supports chacha20 rc4-md5 xchacha20-ietf-poly1305
2019-04-23 23:29:36 +08:00
- { name: "ss1", type: ss, server: server, port: 443, cipher: AEAD_CHACHA20_POLY1305, password: "password", udp: true }
2019-02-11 15:55:17 +08:00
# old obfs configuration remove after prerelease
- name: "ss2"
type: ss
server: server
port: 443
cipher: AEAD_CHACHA20_POLY1305
password: "password"
plugin: obfs
plugin-opts:
mode: tls # or http
# host: bing.com
- name: "ss3"
type: ss
server: server
port: 443
cipher: AEAD_CHACHA20_POLY1305
password: "password"
plugin: v2ray-plugin
plugin-opts:
mode: websocket # no QUIC now
# tls: true # wss
# skip-cert-verify: true
# host: bing.com
# path: "/"
2019-03-30 14:20:04 +08:00
# headers:
# custom: value
2018-10-03 12:25:24 +08:00
# vmess
2018-09-16 23:08:04 +08:00
# cipher support auto/aes-128-gcm/chacha20-poly1305/none
2018-10-29 20:25:13 +08:00
- { name: "vmess", type: vmess, server: server, port: 443, uuid: uuid, alterId: 32, cipher: auto }
# with tls
- { name: "vmess", type: vmess, server: server, port: 443, uuid: uuid, alterId: 32, cipher: auto, tls: true }
# with tls and skip-cert-verify
- { name: "vmess", type: vmess, server: server, port: 443, uuid: uuid, alterId: 32, cipher: auto, tls: true, skip-cert-verify: true }
# with ws-path and ws-headers
- { name: "vmess", type: vmess, server: server, port: 443, uuid: uuid, alterId: 32, cipher: auto, network: ws, ws-path: /path, ws-headers: { Host: v2ray.com } }
2018-10-29 20:25:13 +08:00
# with ws + tls
- { name: "vmess", type: vmess, server: server, port: 443, uuid: uuid, alterId: 32, cipher: auto, network: ws, ws-path: /path, tls: true }
2018-09-16 23:08:04 +08:00
2018-10-03 12:25:24 +08:00
# socks5
- { name: "socks", type: socks5, server: server, port: 443 }
2018-12-05 21:26:04 +08:00
# socks5 with authentication
- { name: "socks", type: socks5, server: server, port: 443, username: "username", password: "password" }
2018-10-29 20:25:13 +08:00
# with tls
- { name: "socks", type: socks5, server: server, port: 443, tls: true }
# with tls and skip-cert-verify
- { name: "socks", type: socks5, server: server, port: 443, tls: true, skip-cert-verify: true }
2018-08-12 13:50:54 +08:00
2018-12-05 21:26:04 +08:00
# http
- { name: "http", type: http, server: server, port: 443 }
# http with authentication
- { name: "http", type: http, server: server, port: 443, username: "username", password: "password" }
# with tls (https)
- { name: "http", type: http, server: server, port: 443, tls: true }
# with tls (https) and skip-cert-verify
- { name: "http", type: http, server: server, port: 443, tls: true, skip-cert-verify: true }
2018-10-03 12:25:24 +08:00
Proxy Group:
# url-test select which proxy will be used by benchmarking speed to a URL.
2019-02-11 15:55:17 +08:00
- { name: "auto", type: url-test, proxies: ["ss1", "ss2", "vmess1"], url: "http://www.gstatic.com/generate_204", interval: 300 }
2018-10-03 12:25:24 +08:00
# fallback select an available policy by priority. The availability is tested by accessing an URL, just like an auto url-test group.
2019-02-11 15:55:17 +08:00
- { name: "fallback-auto", type: fallback, proxies: ["ss1", "ss2", "vmess1"], url: "http://www.gstatic.com/generate_204", interval: 300 }
2018-08-12 04:22:14 +08:00
2019-02-15 22:01:11 +08:00
# load-balance: The request of the same eTLD will be dial on the same proxy.
2019-03-30 14:20:04 +08:00
- { name: "load-balance", type: load-balance, proxies: ["ss1", "ss2", "vmess1"], url: "http://www.gstatic.com/generate_204", interval: 300 }
2019-02-15 22:01:11 +08:00
2018-08-12 04:22:14 +08:00
# select is used for selecting proxy or proxy group
# you can use RESTful API to switch proxy, is recommended for use in GUI.
2018-10-03 12:25:24 +08:00
- { name: "Proxy", type: select, proxies: ["ss1", "ss2", "vmess1", "auto"] }
Rule:
2019-02-15 22:01:11 +08:00
- DOMAIN-SUFFIX,google.com,auto
- DOMAIN-KEYWORD,google,auto
- DOMAIN,google.com,auto
2018-10-03 12:25:24 +08:00
- DOMAIN-SUFFIX,ad.com,REJECT
2018-10-29 20:25:13 +08:00
- IP-CIDR,127.0.0.0/8,DIRECT
- SOURCE-IP-CIDR,192.168.1.201/32,DIRECT
2018-10-03 12:25:24 +08:00
- GEOIP,CN,DIRECT
# FINAL would remove after prerelease
# you also can use `FINAL,Proxy` or `FINAL,,Proxy` now
2019-02-15 22:01:11 +08:00
- MATCH,auto
2018-06-10 22:50:03 +08:00
```
## Documentations
https://clash.gitbook.io/
2018-08-12 04:22:14 +08:00
## Thanks
[riobard/go-shadowsocks2](https://github.com/riobard/go-shadowsocks2)
2018-09-16 23:08:04 +08:00
[v2ray/v2ray-core](https://github.com/v2ray/v2ray-core)
## License
2018-08-12 04:22:14 +08:00
[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2FDreamacro%2Fclash.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2FDreamacro%2Fclash?ref=badge_large)
2018-06-10 22:50:03 +08:00
## TODO
2018-08-12 04:22:14 +08:00
- [x] Complementing the necessary rule operators
- [x] Redir proxy
2019-04-23 23:29:36 +08:00
- [ ] UDP support (vmess, outbound socks5)
2018-08-12 04:22:14 +08:00
- [ ] Connection manager