When ssu+udp is used in a chain, no other nodes should exist in the chain. When used in a chain, ssu must be the last node of the chain. The behavior of forwarding TCP data is undefined. Ssu can only be used to forward UDP data. If other transport types are specified, SOCKS5 UDP relay protocol is used for data forwarding. In this case, GOST will use shadowsocks UDP relay protocol for data forwarding. gost -L ssu+kcp://:8338īy default, ssu is equivalent to ssu + udp, and the transport layer is the raw UDP protocol. Ssu became a protocol type, so it can be used in combination with transport types. If not supported, switch to the (shadowsocks/go-shadowsocks2). The default value should be sufficient here. User determined: timeout: Connection timeout in seconds. User determined: password: Connection password. User determined: serverport: Shadowsocks listens on this port. When encryption is enabled, the cipher methods in (shadowsocks/shadowsocks-go) will be used first. server: Enter the server’s public IP address. GOST supports AEAD cipher methods based on shadowsocks/go-shadowsocks2, and compatible with cipher methods in older version. Ssu can be used in the chain to forward UDP data: gost -L udp://:5353/8.8.8.8:53 becomes optional. The shadowsocks protocol can be used in combination with various transport types Shadowsocks Over TLS gost -L Over KCP gost -L Server side gost - (2.10+) tunnel time to live, default values is 60s. Server side gost side gost -L=:8080 with transport layer Server side gost side gost -L=:8080 cipherĪs of 2.10.1+, features of ss2 have been merged into ss, the AEAD cipher methods can be used directly in ss, and ss2 is deprecated.Īs of v2.8, GOST supports AEAD cipher based on shadowsocks/go-shadowsocks2. Starting from 2.10.1+, encryption becomes optional. Support for shadowsocks is based on library shadowsocks/shadowsocks-go. Shadowsocks is a protocol type supported by GOST.
0 Comments
Leave a Reply. |