Hot answers tagged

3

Allow first your local connection and your RELATED, ESTABLISHED connections protocols. $ sudo iptables -A INPUT -p tcp -s 127.0.0.1 -j ACCEPT $ sudo iptables -A INPUT -p tcp -m state --state RELATED,ESTABLISHED -j ACCEPT $ sudo iptables -A INPUT -p udp -m state --state RELATED,ESTABLISHED -j ACCEPT $ sudo iptables -A INPUT -p icmp -m state --state ...


2

I've always had issues with iptables redirections (probably my fault, I'm pretty sure it's doable). But for a case like yours, it's IMO easier to do it in user-land without iptables. Basically, you need to have a daemon in your "default" workspace listening on TCP port 8112 and redirecting all traffic to 10.200.200.2 port 8112. So it's a simple TCP proxy. ...


1

Run the command sudo ifconfig. It should return a list of connections, one of them is going to be something like tun0 which is your VPN tunnel. In the tun0 block, there will be an inet addr xxx.xxx.xxx.xxx. Take that inet addr and add it or edit your .rtorrent.rc file (which is probably in your /home directory) such that it reads: bind = xxx.xxx.xxx.xxx ...



Only top voted, non community-wiki answers of a minimum length are eligible