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
On Tue, 2025-11-11 at 20:56 +0100, Daniel Baumann wrote:
> 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
>
