If two commands are presented in the same instance (separated by &), remember to use sudo after the & (ex. To run the steps as an elevated user with sudo privileges, prepend each command with sudo. The commands in this guide require root privileges.
SHADOWSOCKS SERVER HOW TO
Data passing through Shadowsocks is encrypted for additional security and privacy.īecause currently, there is no Shadowsocks package available for Ubuntu or CentOS, this guide shows how to build Shadowsocks from the source. Unlike other proxy software, Shadowsocks traffic is designed to be both indiscernible from other traffic to third-party monitoring tools, and also able to disguise as a normal direct connection.
SHADOWSOCKS SERVER FULL
A full setup requires a Linode server to host the Shadowsocks daemon, and a client installed on PC, Mac, Linux, or a mobile device. Shadowsocks is a lightweight SOCKS5 web proxy tool primarily utilized to bypass network censorship and block certain websites and web protocols. This guide shows you how to create a SOCKS5 proxy server with Shadowsocks on Ubuntu and CentOS. pac file server: $ localssjs -pac_update_gfwlist Log verbosely: $ serverssjs -d start -level verbose Start daemon: $ localssjs -d start -b 1080 Start clients that bind at 1088 and will connect to MY.SSSERVER.DOMAIN: $ localssjs -b 1088 -s MY.SSSERVER.DOMAIN h, -help show this help message and exit level LOG_LEVEL log level, default: warn pac_port PAC_PORT PAC file server port, default: 8090 t TIMEOUT timeout in seconds, default: 600 m METHOD encryption method, default: aes-128-cfb l LOCAL_ADDR local binding address, default: 127.0.0.1 p SERVER_PORT server port, default: 8083 s SERVER_ADDR server address, default: 127.0.0.1 Use localssjs -h or serverssjs -h to show cli options: Proxy options: Use serverssjs (server ssjs) to start your remote server. You may prefer to navigate clients page and choose clients for your devices instead of using localssjs.
The localssjs server will also serve a pac file at (by default) for your apps to avoid unnecessary tunnel work. Use localssjs (local ssjs) to start clients to communicate with applications. Shadowsocks-js has been tested in osx and ubuntu 14 but it's also expected to work in It's recommended to use node v6 to achieve better performance. Node implementation is less likely to fail requests in high concurrency situation.Īnd the higher concurrency benchmarks may be meaningless as the bandwidth and network environment would become the actual bottleneck in the real world.ĭo Please point out my faults if I have missed something or get something wrong. It's not a bug, it's a conscious time/space trade-off.Įach request would cost less time to get responsed (even 50% less time in some situations). Node has a different GC strategy but it's, of course, able to keep thousands of connections with a reasonable memory usage. You can get the benchmark details here or even test your own shadowsocks implementation.Īfter some simple benchmarks that compare both the node and python implementation, my conclusion is: Shadowsocks is a light weight and efficient proxy tunnel and nodejs is a very good choice to achieve both flexibility and good performance in this situation.Īnd I have found that many of who are familiar with shadowsocks-nodejs may be curious about the memory usage so that I have finished some simple benchmarks to measure its behavior. Why another Nodejs implementation? (with Benchmark).Yet another shadowsocks implementation for nodejs to help you bypass firewalls.
0 kommentar(er)
