[SOLVED] Deluge Thin Client - Using Split Tunneling

[jcsjourney]

Hello all, To Start off, I followed both the Split tunneling and the Reverse Proxy (Deluge) for WebUI posts and have those all working. My main question, would it be possible to use the reverse proxy setup, but for the thin client? Would there be any IP leak or security issues with that? I hate using the WebUI because of its lack of support. In the Port Forwarding Auto Script setup guide for PIA, it says I can check to ensure its working correctly with the ThinClient but doesn't give any setup instructions. Using Ubuntu Server 16.10 currently. Thanks in advance!

[da_guy2]

(Mar 05, 2017, 07:43 AM)jcsjourney Wrote: Hello all, To Start off, I followed both the Split tunneling and the Reverse Proxy (Deluge) for WebUI posts and have those all working. My main question, would it be possible to use the reverse proxy setup, but for the thin client? Would there be any IP leak or security issues with that? I hate using the WebUI because of its lack of support. In the Port Forwarding Auto Script setup guide for PIA, it says I can check to ensure its working correctly with the ThinClient but doesn't give any setup instructions. Using Ubuntu Server 16.10 currently. Thanks in advance!

Can I add a ditto to this?

I was able to get the ThinClient to work locally on the Ubuntu machine, but I'd like all computers on my local network to be able to access the daemon via the ThinClient. Is there a simple change to the IP tables that would allow this?

[drake]

There is a small modification needed to the iptables.sh script in order to make Split Tunnel and Deluge ThinClient from home network working. 

We can use nginx to forward requests, but I would not recommend this. Instead, open the iptables.sh script, and change the local ip (LOCALIP) to a subnet, instead of allowing only the server. 

Code:

sudo nano /etc/openvpn/iptables.sh

If your IP address (of the server) is: 192.168.1.110 then change it to 192.168.1.0/24
Basically you just change the last digit of the ip to 0/24, it should look like this:

Code:

export LOCALIP="192.168.1.0/24"

Restart OpenVPN service or do a reboot, and ThinClient should be able to connect to the Deluge daemon running on the server from the home network range.

Let me know if this worked for you guys. i will update the ThinClient guide with these details soon.

[da_guy2]

(Mar 09, 2017, 09:14 AM)drake Wrote: There is a small modification needed to the iptables.sh script in order to make Split Tunnel and Deluge ThinClient from home network working. 

We can use nginx to forward requests, but I would not recommend this. Instead, open the iptables.sh script, and change the local ip (LOCALIP) to a subnet, instead of allowing only the server. 

Code:

sudo nano /etc/openvpn/iptables.sh

If your IP address (of the server) is: 192.168.1.110 then change it to 192.168.1.0/24
Basically you just change the last digit of the ip to 0/24, it should look like this:

Code:

export LOCALIP="192.168.1.0/24"

Restart OpenVPN service or do a reboot, and ThinClient should be able to connect to the Deluge daemon running on the server from the home network range.

Let me know if this worked for you guys. i will update the ThinClient guide with these details soon.

Thanks! Worked perfect.

[drake]

Excellent, many thanks for the feedback! I will update the ThinClient guide with the Split Tunnel related setup.

[Pyrhic]

(Mar 09, 2017, 01:16 PM)drake Wrote: Excellent, many thanks for the feedback! I will update the ThinClient guide with the Split Tunnel related setup.

Hi Drake,

Sorry to dredge up an old topic, but - this is great, thanks, I've been wondering about this myself for a while! I wanted to ask though if there are any other implications to this? Is it just marginally less secure? Not an issue if you trust all the machines on your network etc? Thanks!