![]() ![]() This is not something that is done with iptables as it only handles traffic packets. Iptables rules should only redirect traffic to shadowsocks if shadowsocks is running. So I assume I'm getting reroute loop (?), but don't understand why. Sudo iptables -t nat -A OUTPUT -p tcp -m owner ! -uid-owner socks_user -dport 443 -j REDIRECT -to-port 1080Īfter that, I can still use the browser if connected directly to the proxy through settings, but after switching to no proxy/system proxy - getting request timeout. sudo iptables -t nat -A OUTPUT -p tcp -m owner ! -uid-owner socks_user -dport 80 -j REDIRECT -to-port 1080 Then I made iptables rules, according to the links above. I made systemd unit to start client on boot from separate user, content of file listed below: ĮxecStart=ss-local -c /etc/shadowsocks-client/config.jsonĪt this point if I'm setting 127.0.0.1:1080 in my browser (firefox) as a socks5 proxy - it works fine. I created admin user for running shadow socks client only. I followed recommendations from this question and this blog, where the answer is pointing to. ![]() The goal is to redirect all requests to 127.0.0.1:1080, where proxy client is running. I also have ubuntu 20.04 on my pc, with shadow-socks client running on it.Ĭurrently using shadow-socks-libev version. I have ubuntu 20.04 vps with shadow-socks server on it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |