Deluge Forum

Hi,

My PG2 blocked connection with ip 72.20.34.145 witch is tracked back to BitTorrentInc. It happens exactly after installing Deluge, during the first run. I checked it twice ( installed clean version x2, no other software connecting with internet).
What is purpose of that connection? BitTorrentInc is commonly associated with anti-p2p organizations so sorry for being extra careful...
Hope I ( We) can get info about that.

Take care,
Bye.

rehto wrote:Hi,

My PG2 blocked connection with ip 72.20.34.145 witch is tracked back to BitTorrentInc. It happens exactly after installing Deluge, during the first run. I checked it twice ( installed clean version x2, no other software connecting with internet).
What is purpose of that connection? BitTorrentInc is commonly associated with anti-p2p organizations so sorry for being extra careful...
Hope I ( We) can get info about that.

Take care,
Bye.

please dont start any rumors. we make absolutely no connection to anything besides the trackers in the torrent file and the peers that those trackers tell us about. if you have dht or pex enabled, we also get connections from those. this isnt a deluge thing, it's a tracker or torrent file thing. our code is 100% open for all to see that we never do any kind of spying or reporting of any type. we even provide the blocklist plugin for our users.

markybob wrote:

rehto wrote:Hi,

My PG2 blocked connection with ip 72.20.34.145 witch is tracked back to BitTorrentInc. It happens exactly after installing Deluge, during the first run. I checked it twice ( installed clean version x2, no other software connecting with internet).
What is purpose of that connection? BitTorrentInc is commonly associated with anti-p2p organizations so sorry for being extra careful...
Hope I ( We) can get info about that.

Take care,
Bye.

please dont start any rumors. we make absolutely no connection to anything besides the trackers in the torrent file and the peers that those trackers tell us about. if you have dht or pex enabled, we also get connections from those. this isnt a deluge thing, it's a tracker or torrent file thing. our code is 100% open for all to see that we never do any kind of spying or reporting of any type. we even provide the blocklist plugin for our users.

To be fair when the Deluge starts, mainline dht is enabled. No torrents or other programs are present, connection happens after clean install, while the first program start.

@edit I don't want to harm Your project in any way. I know that Deluge is open- utorrent (BitTorrentInc) closed. I was just suprised to see that connection- dht can be blamed- but I want clean situation.

rehto wrote:To be fair when the Deluge starts, mainline dht is enabled. No torrents or other programs are present, connection happens after clean install, while the first program start.

@edit I don't want to harm Your project in any way. I know that Deluge is open- utorrent (BitTorrentInc) closed. I was just suprised to see that connection- dht can be blamed- but I want clean situation.

deluge remembers some dht nodes, so you can connect to the same ones between sessions. you can delete ~/.config/deluge/dht.state to clear out dht.

markybob wrote:

rehto wrote:To be fair when the Deluge starts, mainline dht is enabled. No torrents or other programs are present, connection happens after clean install, while the first program start.

@edit I don't want to harm Your project in any way. I know that Deluge is open- utorrent (BitTorrentInc) closed. I was just suprised to see that connection- dht can be blamed- but I want clean situation.

deluge remembers some dht nodes, so you can connect to the same ones between sessions. you can delete ~/.config/deluge/dht.state to clear out dht.

As you said to avoid any rumors I would suggest disabling by default dht in clean install of Deluge or some kind of change in a code so that the first dht node that Deluge connects to wasn't mainline one ( I don't know in details how mainline dht works and if it needs to connect to bittorentinc serwers to work).
You must understand it is not fun to see that kind of connection after installing totaly new bt client- especially two times in a row ( pls see my first post, second install was also clean one, so it wasn't problem with repeated dht session).

I'll give it a try- community needs another actively developed bt client, azureus is resource muncher, bitcomet has problems with private trackers, utorrent has some shady connections.

So good luck!

i'm sure it's just a dht node. that's what happens when one of the largest bittorrent programs (utorrent) is owned and opporated by bittorrent inc. but hey, if you're blocking it, like you said you are, then there's nothing to worry about.

markybob wrote:i'm sure it's just a dht node. that's what happens when one of the largest bittorrent programs (utorrent) is owned and opporated by bittorrent inc. but hey, if you're blocking it, like you said you are, then there's nothing to worry about.

yup it's dht, I tested it. Every time with mainline dht on it tries to connect to 72.20.34.145 after Deluge starts. With dht off the problem doesn't exist.
thx for clarifying things up.

@edit maybe You can add solved or something to the topic subject so it wouldn't seem so "bad" :>