Deluge not using OpenVPN

[dcoryh192]

Hi,

I am trying to route Deluge through my TorGuard OpenVPN. Deluge is running on an Ubuntu 14.04 machine that also serves as a Plex server/XBMC frontend. I don't want all of my computer traffic to go through the VPN, just Deluge.

I have iptables set up with:

Code: Select all

iptables -A OUTPUT -m owner --uid-owner deluge-x -d 192.168.2.0/24 -j ACCEPT
iptables -A OUTPUT -m owner --uid-owner deluge-x -d 127.0.0.1 -j ACCEPT
iptables -A OUTPUT -m owner --uid-owner deluge-x \! -o tun0 -j REJECT

The TorGuard OpenVPN config is

Code: Select all

client
dev tun
proto tcp
remote-random
remote ...
remote ... #bunch of IPs
resolv-retry 5
nobind
fast-io
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
persist-tun
ca globalca.crt
auth-user-pass
comp-lzo
route-delay 5 30
script-security 3 system
mute-replay-warnings
verb 3

This default config routes ALL traffic through the VPN. WIth the iptables set, Deluge works fine.

The problem is when I add the line

Code: Select all

route-noexec

Now OpenVPN connects, I see the tun0 adapter in ifconfig, and my public IP is normal, but deluge sees no traffic at all. Is there something I need to do to Deluge to get it to use the tun0 adapter instead of eth0?

EDIT: So with the default config (ALL traffic through VPN), and no iptables set, everything works fine. With the iptables settings set, Deluge can't find trackers anymore although downloads will continue. When I add route-noexec, then Deluge fails completely

Thanks,
Cory

[srj55]

Having the exact same issue. Were you able to find a solution?

[dcoryh192]

Unfortunately no. Haven't gotten around to it but I think I might just make a VM with the deluge daemon running on it. VPN that whole VM with the default settings since that seems to work.

It's been a while since I've played with this, but I don't think I ever got anywhere else. Certain things will work, but somethings won't. It would be nice if the Bind Interface box let you type in "tun0" or something, but from what I recall that is a thing with libtorrent, so it would need to be fixed there.