Break through GFW blockade with shadowsocks (built on Digital Ocean or AWS)

2017-02-15T00:00:00+00:00

On Digital Ocean</h2>

If you’re a student, try apply for a student pack</a> on GitHub.</li>
Use code of Digital Ocean in student pack to register a new account and buy a droplet at San Fransico (both node 1 & 2 is OK, maybe 2 is better).</li>
Install Fedora 25 (64 bit) on your VPS then do as below:</li> </ol>
Install shadowsocks:
sudo dnf install m2crypto python-setuptools easy_install pip pip install shadowsocks</code></pre> Shadowsocks use a json file as configuration. For all users, this file can be placed in /etc</code>. Use vi /etc/shadowsocks.json</code> to edit the file and fill in contents below:
{ "server":"0.0.0.0", "server_port":"port", "local_address": "127.0.0.1", "local_port":1080, "password":"passwd", "timeout":300, "method":"rc4-md5", "fast_open": false, "workers": 1 }</code></pre> To keep shadowsocks running in background after you cut off SSH connection, you may use supervisor</code>.
sudo dnf install supervisor echo_supervisord_conf > /etc/supervisord.conf</code></pre> Execute vi /etc/supervisord.conf</code> to configure it:
[program:shadowsocks] command=ssserver -c /etc/shadowsocks.json autostart=true autorestart=true user=nobody</code></pre>
Finally, supervisord</code> or supervisord -c /etc/supervisord.conf</code> to start shadowsocks server and visit the project’s homepage</a> on GitHub for a client. For Windows user, try https://github.com/shadowsocks/shadowsocks-windows/releases. For Linux user, shadowsocks-qt5</a> is a good choice. There’re also shadowsocks for Android</a> and shadowsocks for iOS</a>.
Appendix</h3> supervisorctl status</code> for checking all processes’ status controlled by supervisor. supervisorctl stop ssserver</code> for kill a process. supervisorctl start ssserver</code> for start a process. supervisorctl shutdown</code> for killing all processes controlled by supervisor. Known issue</h3> Sometimes shadowsocks works fine in Windows, but your browser can not visit pages in Arch Linux, it is because that too frequently updating libQtShadowsocks</code> brings conflict. To solve this problem</a>, you can downgrade libQtShadowsocks</code> or change the encryption method from AES-256-CFB</code> to AES-256-CTR</code>. On AWS</h2> Creat an EC2 (choose Ubuntu here) instance, and be sure to keep in mind that the key pair should be generated during the process, then download your private key (.pem) file. </li> Change your private key’s priviledge to 400: chmod 400 /path/my-key-pair.pem</code>. </li> Log-in your instance with such command: ssh -i /path/my-key-pair.pem ubuntu@ec2-13-124-234-100.ap-northeast-2.compute.amazonaws.com</code>. </li> Upgrade OS: sudo apt-get update sudo apt-get dist-upgrade</code></pre></li> Install Shadowsocks: sudo apt-get install python-pip sudo pip install shadowsocks</code></pre></li> </ol> You may see this error during installation of Shadowsocks: Traceback (most recent call last): File "/usr/bin/pip", line 11, in <module> sys.exit(main()) File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 215, in main locale.setlocale(locale.LC_ALL, '') File "/usr/lib/python2.7/locale.py", line 581, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting</code></pre> It is caused by wrong language settings. Fix it by export LC_ALL=C</code> (only works in current tty), then try again. </blockquote> Start Shadowsocks server by: sudo ssserver -p 2333 -k password -m rc4-md5 -d start</code> (use 2333</code> as port and password</code> as password, change start</code> to stop</code> if you wanna stop the process).</li> </ol> You should use AES-256-CTR</code> as encryption method at ArchLinux to avoid problems brought by over-updated libqtshadowsocks</code>. </blockquote> Optimization</h3> Break though limit of file open number</h4> Edit limits.conf</code>: sudo vi /etc/security/limits.conf</code>. </li> Add those two lines: * soft nofile 51200 * hard nofile 51200</code></pre></li> Restart the OS. </li> </ol> Improve system performance</h4> Edit sysctl.conf</code>: sudo vi /etc/sysctl.conf</code>. </li> Add these lines: fs.file-max = 51200 net.core.rmem_max = 67108864 net.core.wmem_max = 67108864 net.core.netdev_max_backlog = 250000 net.core.somaxconn = 4096 net.ipv4.tcp_syncookies = 1 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_tw_recycle = 0 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_time = 1200 net.ipv4.ip_local_port_range = 10000 65000 net.ipv4.tcp_max_syn_backlog = 8192 net.ipv4.tcp_max_tw_buckets = 5000 net.ipv4.tcp_fastopen = 3 net.ipv4.tcp_rmem = 4096 87380 67108864 net.ipv4.tcp_wmem = 4096 65536 67108864 net.ipv4.tcp_mtu_probing = 1 net.ipv4.tcp_congestion_control = hybla</code></pre></li> Run sudo sysctl -p</code> to reload settings. </li> </ol> ServerSpeeder</h4> ServerSpeeder cannot be used on Ubuntu 16.04 now. net-speeder</h4> net-speeder will double the network traffic. Not recommended.

Yu Sun - Network

Break through GFW blockade with shadowsocks (built on Digital Ocean or AWS)

`ServerSpeeder</h4> ServerSpeeder cannot be used on Ubuntu 16.04 now.</p> net-speeder</h4> net-speeder will double the network traffic. Not recommended.</p>`

net-speeder</h4>
net-speeder will double the network traffic. Not recommended.</p>