Pro-Test TCP BBR mate SS or V2ray on tubing look 1080 is no problem.
V2ray
Both client and server installation are simple, just say the configuration
1, service-side configuration
{
"log": {
... // Configuration log
},
"inbound": {// enter server configuration
"port": 8899, // A client connection port is provided on the server
"protocol": "vmess", // protocol, support ss
"settings": {
"clients": [
{
"id": "fcbaef0f-e3f5-4d64-a12d-0318d0804d69", // Data encryption and decryption keys can be customized
"level": 1,
"alterId": 64
}
]
}
},
"outbound": {// The default exit direction of the server is unlimited, that is, unlimited
"protocol": "freedom",
"settings": {}
},
... // Other configurations, or not
}
2, Client Configuration
{
"inbound": {// Client entry configuration, usually
"port": 1080, // The service port where the client accepts requests forwarded by other programs
"protocol": "socks", // Protocols accepted by the client
"settings": {
"auth": "noauth" // usually local so no authentication is required
}
},
"outbound": {// The client's outgoing direction only needs to correspond one-to-one with the server
"protocol": "vmess", // Encryption protocol passed from client to server
"settings": {
"vnext": [
{
"address": "xxx.xx.xx.xx", // Server address
"port": 8899, // The server listens on the port
"users": [
{
"id": "fcbaef0f-e3f5-4d64-a12d-0318d0804d69", // key required by the server
"alterId": 64
}
]
}
]
}
}
}
Ss
Installation and configuration are very simple, server and client configuration files, service end with Ssserver client with sslocal
pip install shadowsocks
vi /etc/shadowsocks
{
"server":"xxx.xxx.xxx.xxx",
"server_port":8888,
"local_address": "127.0.0.1",
"local_port":1080,
"password":"passwd",
"timeout":300,
"method":"aes-256-cfb",
"fast_open": true,
"workers": 1
}
No startup script due to pip installation
# Server-side similar
[Unit]
Description = Shadowsocks
After = network.target
[Service]
ExecStart = / usr / bin / python / usr / local / bin / sslocal -c /etc/shadowsocks.json
[Install]
WantedBy = multi-user.target
Genpac
Help Ss,v2ray Client Intelligent parsing
pip install genpac
mkdir mypac && cd mypac && touch user-rules.txt
genpac --pac-proxy "SOCKS5 127.0.0.1:1080" --gfwlist-proxy="SOCKS5 127.0.0.1:1080" --output="autoproxy.pac" --gfwlist-url="https://raw.githubusercontent.com/gfwlist/gfwlist/master/gfwlist.txt" --user-rule-from="user-rules.txt"
Ubuntu Setup System Agent Setting-->network-->autoproxy and browser find proxy server Configuration PAC agent is filled in:
/home/sylar/paclist/autoproxy.pac
Privoxy setting
Convert HTTP and HTTPS requests to SOCKS5 send to client, chrome or other browser only need to configure automatic proxy PAC to automatically identify the agent does not need this step, this is for the terminal and other programs to use
apt install privoxy
vi /etc/privoxy/config
listen-address localhost:8118
forward-socks5 / 127.0.0.1:1080 .
sudo /etc/init.d/privoxy start
BASHRC Enable proxy,
Export http_proxy= "http://127.0.0.1:8118"
Export https_proxy= "https://127.0.0.1:8118"
V2ray (ss) + Privoxy + Genpac Science for Linux