Is listen_interface for VPNs?

General support for problems installing or using Deluge
Airton
New User
New User
Posts: 1
Joined: Tue Oct 30, 2018 8:58 am
OS or Distro: Debian

Is listen_interface for VPNs?

Postby Airton » Tue Oct 30, 2018 9:31 am

Background
I have a Raspbian/Debian system running deluged (1.3.13+git20161), which I access via another Linux box running the deluge front-end. I am trying to force torrents through my VPN, while leaving the UI accessible through the local network.

My understanding is that I should be able to do this selective routing through deluged itself, via listen_interface (also available in the GUI through Preferences > Network > Interface). However, I can't seem to find any clear instructions on how to use this. How precisely should I use listen_interface?

What I've tried

I am using an OpenVPN config, which I have tested by itself and is working fine. I then add no-pull to the OpenVPN config file, and restart it. I attempt to get the IP address of tun0 with

Code: Select all

$ ip route show table main
default via 192.168.1.100 dev eth0
10.15.0.0/16 dev tun0 proto kernel scope link src 10.15.0.2
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.91

or sometimes

Code: Select all

$ ip route show table main
default via 192.168.1.100 dev eth0
10.15.0.0/16 dev tun0 proto kernel scope link src 10.15.0.9
<VPN_public_IP> via 192.168.1.100 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.91

I try to set listen_interface to the IP address above, i.e. 10.15.0.2 or 10.15.0.9, then restart deluged, but I get no incoming connections, and can't connect to anything.

I am aware of other methods to use a VPN with deluged, but the "Interface" method seemed easier. Am I using this setting correctly?

Return to “Support”

Who is online

Users browsing this forum: No registered users and 7 guests