Deluge Forum

Posted: **Sat Mar 11, 2023 7:42 am**

Hello,

I'm failing to understand what's up atm.
I'm using Ubuntu 22.04 Proxmox LXC container with Deluge 2.1.1
I have installed NordVPN:

Code: Select all

Status: Connected
Hostname: fr911.nordvpn.com
IP: 85.245.5.265
Country: France
City: Paris
Current technology: NORDLYNX
Current protocol: UDP
Transfer: 273.34 MiB received, 35.40 MiB sent

Here is the config:

Code: Select all

Technology: NORDLYNX
Firewall: enabled
Firewall Mark: 0xe1f1
Routing: enabled
Analytics: enabled
Kill Switch: enabled
Threat Protection Lite: disabled
Notify: disabled
Auto-connect: enabled
IPv6: disabled
Meshnet: disabled
DNS: 1.0.0.1, 1.1.1.1
Whitelisted ports:
       22 (UDP|TCP)
Whitelisted subnets:
        192.168.1.0/24
        128.0.0.0/1

Yet, if I don't use a SOCKS5 Auth proxy in Deluge, the bottom right corner will show my WAN public IP.

I confirm that the VPN Is up:

Code: Select all

curl ifconfig.me
85.245.5.265

Here is my ip a:

Code: Select all

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0@if63: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 56:ef:13:65:62:5c brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 192.168.1.40/32 scope global eth0
       valid_lft forever preferred_lft forever
3: nordlynx: <POINTOPOINT,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none 
    inet 10.5.0.2/32 scope global nordlynx
       valid_lft forever preferred_lft forever

(IP is randomised)

Also on the top, of the public IP shown in the bottom GUI of deluge, there is also the traffic reflected by NordVPN that doesn't match reality.

If you have some ideas for me to troubleshoot this further it would be great.

Posted: **Sat Mar 11, 2023 8:23 am**

I don't know that VPN protocol(nordlynx, layer on top wg I gather, but only known little bit openvpn). On openvpn, then unless client does tricks to hide local route, and/or kill-switch, then with libtorrent 1.2.4+(there about) you need fix that yourself, because added multi-homing. It looks like same here. Also, quickly googled it, and some tips here https://www.reddit.com/r/nordvpn/commen ... revert_to/

Additionally, I would presume you can bind in/out interfaces in deluge(libtorrent) to your VPN interface name or IP.

What deluge show as IP in statusbar is from libtorrent, and it does some guess work to try find out current IP.

Posted: **Sat Mar 11, 2023 9:46 am**

I was just going to suggest you use the bind outgoing IP address feature as well, mhertz, seems applicable in this situation.

Deluge Forum

Deluge ByPass NordVPN on Ubuntu

Deluge ByPass NordVPN on Ubuntu

Re: Deluge ByPass NordVPN on Ubuntu

Re: Deluge ByPass NordVPN on Ubuntu