ss-server - shadowsocks server, libev port
ss-server
[-uUv] [-h|--help]
[-s
Shadowsocks-libev is a lightweight and secure socks5 proxy. It is a port of the original shadowsocks created by clowwindy. Shadowsocks-libev is written in pure C and takes advantage of libev to achieve both high performance and low resource consumption.
Shadowsocks-libev consists of five components.
ss-server
(1) runs on a remote server to provide secured tunnel service.
For more information, check out shadowsocks-libev
(8).
Set the server’s hostname or IP.
Set the server’s port number.
Set the password. The server and the client should use the same password.
Set the key directly. The key should be encoded with URL-safe Base64.
Set the cipher.
Shadowsocks-libev accepts 19 different ciphers:
aes-128-gcm, aes-192-gcm, aes-256-gcm, rc4-md5, aes-128-cfb, aes-192-cfb, aes-256-cfb, aes-128-ctr, aes-192-ctr, aes-256-ctr, bf-cfb, camellia-128-cfb, camellia-192-cfb, camellia-256-cfb, chacha20-ietf-poly1305, xchacha20-ietf-poly1305, salsa20, chacha20 and chacha20-ietf.
If built with PolarSSL or custom OpenSSL libraries, some of these ciphers may not work.
Run as a specific user.
Start shadowsocks as a daemon with specific pid file.
Set the socket timeout in seconds. The default value is 60.
Use a configuration file.
Refer to shadowsocks-libev
(8) CONFIG FILE section for more details.
Specify max number of open files.
Only available on Linux.
Send traffic through specific network interface.
For example, there are three interfaces in your device,
which is lo (127.0.0.1), eth0 (192.168.0.1) and eth1 (192.168.0.2).
Meanwhile, you configure ss-server
to listen on 0.0.0.0:8388 and bind to eth1.
That results the traffic go out through eth1, but not lo nor eth0.
This option is useful to control traffic in multi-interface environment.
Specify the local address to use while this server is making outbound connections to remote servers on behalf of the clients.
Enable UDP relay.
Enable UDP relay and disable TCP relay.
Resovle hostname to IPv6 address first.
Setup name servers for internal DNS resolver (libc-ares). The default server is fetched from /etc/resolv.conf.
Enable TCP fast open.
Only available with Linux kernel > 3.7.0.
Enable port reuse.
Only available with Linux kernel > 3.9.0.
Enable TCP_NODELAY.
Enable ACL (Access Control List) and specify config file.
Specify UNIX domain socket address for the communication between ss-manager(1) and ss-server(1).
Only available in server and manager mode.
Specify the MTU of your network interface.
Enable Multipath TCP.
Only available with MPTCP enabled Linux kernel.
Enable SIP003 plugin. (Experimental)
Set SIP003 plugin options. (Experimental)
Enable verbose mode.
Print help message.
It is recommended to use a config file when starting ss-server
(1).
The config file is written in JSON and is easy to edit. Check out the SEE ALSO section for the default path of config file.
# Start the ss-server
ss-server -c /etc/shadowsocks-libev/config.json
The config file of shadowsocks-libev
(8) is slightly different from original
shadowsocks.
In order to listen to both IPv4/IPv6 address, use the following grammar in your config json file:
{
"server":["::0","0.0.0.0"],
...
}
ss-server
(1) also does not understand "port_password" field in config file.
If you want to start up multiple server instances with a single config file,
please try ss-manager tool. See ss-manager
(8) for details.
ss-local
(1),
ss-tunnel
(1),
ss-redir
(1),
ss-manager
(1),
shadowsocks-libev
(8),
iptables
(8),
/etc/shadowsocks-libev/config.json
Last updated 2020-09-15 02:30:48 UTC