Network config to allow transmission torrent

NETWORK CONFIG TO ALLOW TRANSMISSION TORRENT HOW TO
NETWORK CONFIG TO ALLOW TRANSMISSION TORRENT INSTALL
NETWORK CONFIG TO ALLOW TRANSMISSION TORRENT CODE

What is great about this script is that it will track all data through the device! When you issue sudo iptables -L -v Then make sure these rules persist between reboots with: sudo dpkg-reconfigure iptables-persistent Save the file and then run sudo iptables -F # track any forward (NAT) data for completeness - don't care about interfaces Iptables -A INPUT -i $IFACE_INTERNAL -j ACCEPT

Iptables -A INPUT -i $IFACE_VPN -j ACCEPT # not needed - but added these to properly track data to these interfaces.when using iptables -L -v

Iptables -A OUTPUT -m owner -gid-owner $GROUP -j REJECT Iptables -A OUTPUT -m owner -gid-owner $GROUP -o lo -j ACCEPT Iptables -A OUTPUT -m owner -gid-owner $GROUP -o $IFACE_VPN -j ACCEPT Iptables -A OUTPUT -d $NET -p udp -sport $ALLOW_PORT_FROM_LOCAL -m owner -gid-owner $GROUP -o $IFACE_INTERNAL -j ACCEPT Iptables -A OUTPUT -d $NET -p tcp -sport $ALLOW_PORT_FROM_LOCAL -m owner -gid-owner $GROUP -o $IFACE_INTERNAL -j ACCEPT # Set our rules so the debian-transmission user group can only route through the vpn maybe different - check with 'ifconfig' and change if needed. Sometimes your interfaces eth0, tun0 (which is the vpn) etc.If your local network is not of the form 192.168.1.x Change the NET variable to correspond to your own local network addressing format!!.

NETWORK CONFIG TO ALLOW TRANSMISSION TORRENT CODE

Step 2 - Create the transmission-ip-rules file sudo nano transmission-ip-rulesДЄnd add the text in the code block below starting from #!/bin/bash IMPORTANT

NETWORK CONFIG TO ALLOW TRANSMISSION TORRENT INSTALL

Step 1 - Setup: (Assumes transmission is installed and debian-transmission user therefore exists!) sudo apt-get install iptables Here is a complete 'HOW TO' for NOOBS (using debian) on making sure the debian-transmission user group (i.e transmission) only routes data through the vpnДO NOT use the more lengthy 'How to' for vpn based on complex system scripts.! iptables is THE BEST (and foolproof) METHOD!!! - USING A FEW IPTABLE RULES based on the transmission user and group to control the vpn (not like many more complex 'hack' methods which use systemd scripts, up and down scripts etc.) and it's soooo simple! Sudo ufa allow port udp from localhost to VPNIP port 33442Дoes this logic hold its salt? How would you do it? What would I use for VPNIP, the public IP of the VPN server, or should I specify the local subnet range that the VPN connects me to? Sudo ufw deny port udp from localhost to any port 33442 Sudo ufa allow port tcp from localhost to VPNIP port 33442 Sudo ufw deny port tcp from localhost to any port 33442 I checked out the Ubuntu server guide and I think could do something like this: sudo ufw enable One idea I had would be to force transmission to use a specific port, say 33442, and then only allow traffic to and from that port from the IP address of the VPN server. Instead I was thinking of using ufw, but I have little to no experience with firewalls, and I'm hoping the community can help me out.

NETWORK CONFIG TO ALLOW TRANSMISSION TORRENT HOW TO

I found this question which is similar but I don't want to force all traffic through the VPN and I haven't been able to find a good guide on how to use firestarter from the command line. I'd like to ensure that transmission only sends/receives traffic when the server it runs on is connected to a VPN.

Network config to allow transmission torrent