How to use shadowsocks client
- #How to use shadowsocks client how to#
- #How to use shadowsocks client install#
- #How to use shadowsocks client password#
#Find the corresponding parameter positions in it. #Save and exit Configure WGet proxy #Open WGet configuration file Configure Yum proxy #Open the yum.conf configuration file Note: if you don’t need to use an agent, put /etc/profileJust the configuration notes in. Test curl Returning a lot of HTML means that shadowlocks is working properly. Setting proxy environment variables echo -e "export http_proxy=" > /etc/profileĮcho -e "export https_proxy=" > /etc/profile
#How to use shadowsocks client how to#
To do the following steps, you have to learn how to use SSH and WinSCP to connect to the router first. This guide is for DIY purpose and provided as is. Start privoxy service systemctl enable privoxy Shadowsocks (SS) Setting You will learn how to set up shadowsocks server and client on the mini router in this guide. Modify privoxy configuration file /etc/privoxy/config listen-address 127.0.0.1:8118
#How to use shadowsocks client install#
In COPR shadowsocks-libevThe default read location is /etc/shadowsocks-libev/config.jsonWe can refer to the following configuration files for modification as needed: Configure agent Install privoxy yum install privoxy Ln -s libmbedcrypto.so.1 libmbedcrypto.so.0 Add profile Implement ss-localreport errors: ss-local: error while loading shared libraries: libmbedcrypto.so.0: cannot open shared object file: No such file or directoryĮxecute the following command as root: cd /usr/lib64 If you use shadowsocks-libev on your server then you need to use -b parameter-b localaddress - Specify the local address to use while this server is making outbound connections to remote servers on behalf of the clients. If it works normally, skip the frequently asked questions and continue to add the configuration file. Yum install -y shadowsocks-libev Verify installationīefore continuing with the configuration later, we will execute the SS local command on the command line to confirm that shadowlocks and its dependencies are installed correctly. Then we need to enable EPEL first, and then install shadowlocks libev: yum install -y It indicates that the system does not enable EPEL (extra packages for Enterprise Linux). Note: if the installation reports the following errors Error: Package: shadowsocks-libev-3.1.86_64 (librehat-shadowsocks)Įrror: Package: shadowsocks-libev-3.1.86_64 (librehat-shadowsocks) Install shadowsocks-libev: cd /etc//Īfter installation, there will be ss-local, ss-manager, ss-nat, ss-redir, ss-server, ss-tunnelCommand available.Īmong them, as a client, what we need is ss-localHowever, in the following article, we will start shadowsocks through the service file instead of directly connecting with ss-localDealing with orders.
If ordinary users are used, ordinary users are also required to join rootGroup and add before each command sudo。
#How to use shadowsocks client password#
With rootLog in to the server as, or by command sudo su -Enter the password to switch to root. Since there is already a packaged shadowlocks libev in COPR (cool other package repo), we only need a few commands to complete the installation. It is very easy to install shadowsocks clients under CentOS 7 or RHEL (Red Hat Enterprise Linux) 7. You need to install the shadowsock (hereinafter referred to as SS) client on the server to build a “ladder”. For some reason, the server cannot be connected due to network problems due to the installation of software, plug-ins or scripts.