#1119651 ip addresses for outgoing connections

Package:
deluge
Source:
deluge
Submitter:
Gordon R. Burgess
Date:
2026-07-23 15:27:01 UTC
Severity:
normal
#1119651#5
Date:
2025-10-29 20:22:31 UTC
From:
To:
Dear Maintainer,

   * What led up to the situation?

A call from my network admin, re "strange behavior from my machine"

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I used deluge for its intended purpose, via a magnet (this machine is
configured to only use IPv4)

Running a Torrent Address detection test (https://ipleak.net/) revealed two IP
addresses; both VPN address and my address on the LAN

running the same test with transmission-gtk produced only the expected VPN
address

   * What was the outcome of this action?

I will not use or recommend deluge until i know this is resolved

   * What outcome did you expect instead?

I expected deluge to use the VPN address
#1119651#10
Date:
2025-11-11 19:56:43 UTC
From:
To:
retitle 1119651 ip addresses for outgoing connections
severity 1119651 important
tag 1119651 - security
thanks

Hi Gorden,

thank you for report. When using deluge and vpn (as with any/most other
programs), it depends on in which order you started things.

i.e. can you reproduce it when you start vpn first, and deluge afterwards?

Regards,
Daniel
#1119651#19
Date:
2025-11-11 19:56:43 UTC
From:
To:
retitle 1119651 ip addresses for outgoing connections
severity 1119651 important
tag 1119651 - security
thanks

Hi Gorden,

thank you for report. When using deluge and vpn (as with any/most other
programs), it depends on in which order you started things.

i.e. can you reproduce it when you start vpn first, and deluge afterwards?

Regards,
Daniel
#1119651#24
Date:
2025-11-12 15:20:48 UTC
From:
To:
Hi Daniel - due to my environment, I ALWAYS start the VPN before
starting my bittorrent client, and I have a script running that will
take the bittorrent client down if (when) the VPN goes down - here it
is...

#! /bin/bash

vpn_is_up()
{
    [[ $(ip addr | grep tun0 | grep UP) =~ 'tun0' ]]
}

if vpn_is_up

then echo 'vpn is UP'
date

fi

while vpn_is_up
    do sleep 1
done

echo 'vpn is DOWN'

killall -9 transmission-gtk
killall -9 transmission-qt
killall -9 firefox.real
killall -9 deluge-gtk

date

This issue came to my attention because the network administrator
complained that I was running a bittorrent client.  My VPN connection
was still up, but Deluge reported two IP addresses; one was the address
on my LAN.

(in contrast, Transmission did not do this)

Thanks,

Gordon
#1119651#29
Date:
2025-11-12 15:20:48 UTC
From:
To:
Hi Daniel - due to my environment, I ALWAYS start the VPN before
starting my bittorrent client, and I have a script running that will
take the bittorrent client down if (when) the VPN goes down - here it
is...

#! /bin/bash

vpn_is_up()
{
    [[ $(ip addr | grep tun0 | grep UP) =~ 'tun0' ]]
}

if vpn_is_up

then echo 'vpn is UP'
date

fi

while vpn_is_up
    do sleep 1
done

echo 'vpn is DOWN'

killall -9 transmission-gtk
killall -9 transmission-qt
killall -9 firefox.real
killall -9 deluge-gtk

date

This issue came to my attention because the network administrator
complained that I was running a bittorrent client.  My VPN connection
was still up, but Deluge reported two IP addresses; one was the address
on my LAN.

(in contrast, Transmission did not do this)

Thanks,

Gordon
#1119651#32
Date:
2025-11-12 15:20:48 UTC
From:
To:
Hi Daniel - due to my environment, I ALWAYS start the VPN before
starting my bittorrent client, and I have a script running that will
take the bittorrent client down if (when) the VPN goes down - here it
is...

#! /bin/bash

vpn_is_up()
{
    [[ $(ip addr | grep tun0 | grep UP) =~ 'tun0' ]]
}

if vpn_is_up

then echo 'vpn is UP'
date

fi

while vpn_is_up
    do sleep 1
done

echo 'vpn is DOWN'

killall -9 transmission-gtk
killall -9 transmission-qt
killall -9 firefox.real
killall -9 deluge-gtk

date

This issue came to my attention because the network administrator
complained that I was running a bittorrent client.  My VPN connection
was still up, but Deluge reported two IP addresses; one was the address
on my LAN.

(in contrast, Transmission did not do this)

Thanks,

Gordon