[Not Solved]
Jun 20, 2017, 03:14 AM
(This post was last modified: Jun 20, 2017, 04:55 AM by linuxnoob011.)
Hi all,
Sorry for asking what I expect to be a dumb question. I'm totally new to linux, and so I am sure my struggles are entirely my own fault. Even so, I'm hoping someone remembers back to when they were a total noob and will be willing to lend me a hand.
I am trying to force torrent traffic (client = Deluge) through my vpn. To do so, I am following this HTPC guide: https://www.htpcguides.com/force-torrent...untu-16-04 (I run Ubuntu 16.04, desktop). I made my way through both parts of the guide (except setting up the reverse proxy--if this is what is messing things up, I'm sorry for wasting everyone's time and I'll go set that up and then hide in shame), but Deluge does not appear to be tunneling over the VPN connection: when downloading this TorGuard Check My Torrent IP Address File, the tracker status displays my non-vpn ip address (i.e., the ip address that would be displayed if I ran curl ipinfo.io as my regular user, not the one that would be displayed if I ran curl ipinfo.io as the vpn user). To be clear, when I reached the end of Part I of the guide, my split tunnel appeared to work fine--I ran curl ipinfo.io as the vpn user (i.e., 'sudo -u vpn -i -- curl ipinfo.io') and it returned an ip/location/etc. associated with my VPN (which information differed from the ip information shown by running curlipinfo.io as the regular user).
I hear it is polite when requesting help to let folks know what you have already tried, so here's my attempt at a quick overview:
Can anyone help me troubleshoot my issue?
Sorry for asking what I expect to be a dumb question. I'm totally new to linux, and so I am sure my struggles are entirely my own fault. Even so, I'm hoping someone remembers back to when they were a total noob and will be willing to lend me a hand.
I am trying to force torrent traffic (client = Deluge) through my vpn. To do so, I am following this HTPC guide: https://www.htpcguides.com/force-torrent...untu-16-04 (I run Ubuntu 16.04, desktop). I made my way through both parts of the guide (except setting up the reverse proxy--if this is what is messing things up, I'm sorry for wasting everyone's time and I'll go set that up and then hide in shame), but Deluge does not appear to be tunneling over the VPN connection: when downloading this TorGuard Check My Torrent IP Address File, the tracker status displays my non-vpn ip address (i.e., the ip address that would be displayed if I ran curl ipinfo.io as my regular user, not the one that would be displayed if I ran curl ipinfo.io as the vpn user). To be clear, when I reached the end of Part I of the guide, my split tunnel appeared to work fine--I ran curl ipinfo.io as the vpn user (i.e., 'sudo -u vpn -i -- curl ipinfo.io') and it returned an ip/location/etc. associated with my VPN (which information differed from the ip information shown by running curlipinfo.io as the regular user).
I hear it is polite when requesting help to let folks know what you have already tried, so here's my attempt at a quick overview:
- I ensured my network device is configured to use dhcp. The guide implies that having a static ip address (on the client side) can be problematic. I disabled network manager, which was frustratingly assigning me a static ip address despite my having updated /etc/network/interfaces to configure my network device using dhcp (e.g., the 'ip route list' command showed my ethernet device as static). Ip route list no longer shows my device as static, but I would be happy to run another command and return the result if there is lingering uncertainty. For the avoidance of doubt, my router is set to provide a static ip address to my Ubuntu machine--I can disable this, too, if need be, just let me know.
- I disabled ipv6. I read ipv6 can cause networking headaches, and so I figured this would be a reasonable step. I am happy to re-enable it if you folks think best.
- I flushed my iptable rules and re-configured them as instructed in the HTPC guide. Basically, I was worried that I accidentally messed up the copy/paste the first time around, so I re-did the base configuration (kill vpn connections) and re-wrote the relevant scripts (e.g., iptables.sh).
- I confirmed that the scripts created by the guide actually change my iptable rules. After restarting my machine, I confirmed that my iptables contain the rules I would expect based on the iptables.sh script. It looked fine to me at a glance, but I'm happy to have a more careful look if this is a likely trouble spot.
- I enabled the VPN account, logged into the vpn account, and ran deluge while logged into the vpn account. Deluge appeared properly configured, and downloading the TorGuard file displayed my vpn ip address (i.e., the ip address I would see if I ran 'sudo -u vpn -i -- curl ipinfo.io') under the tracker status. This is the closest I came to success; nonetheless, when I ran deluge as the regular user, the tracker status once again displayed my normal ip address (i.e., the ip address I would see if I ran 'curl ipinfo.io' as my normal user.
- I completely reinstalled ubuntu and re-did the entire split tunnel process as described in the HTPC guide. This wasn't a huge deal to me, as I was working from a recent installation. I was worried that since my Deluge installation slightly predated my split tunnel work, that some wires had gotten crossed (e.g., permissions were set in an inconsistent way).
- I checked my permissions and confirmed that the regular user is in the vpn group and the vpn user is in the regular user group. That is, running the 'groups' on either user shows that each user is in the other's group.
Can anyone help me troubleshoot my issue?