"Risky Connections" blocked by McAfee NetGuard

[haljmp1]

Hello,

Deluge appears to be making "Risky Connections" even when idle that Mcafee NetGuard is detecting and "Blocking".

Why is Deluge making outgoing connections to IPs when no torrents are active?

Has anyone had this issue before?

Is it something a bittorrent client naturally does? Does it make connections even when no torrents are active? It's odd because I had just downloaded deluge and haven't even used it to torrent anything yet. It's never torrented a single thing and it's making outgoing connections?

Thanks

[Shryp]

Any specifics on what is being blocked?

There is a check for updates option.
Also, there is stuff like DHT and UPNP and NAT-PMP that are enabled by default.
The client/daemon nature of how it works connects back to itself locally by IP,

[haljmp1]

Any specifics on what is being blocked?

There is a check for updates option.
Also, there is stuff like DHT and UPNP and NAT-PMP that are enabled by default.
The client/daemon nature of how it works connects back to itself locally by IP,

Today it attempted to connect to http://www.mcafee.com/threat-intelligen ... 42.53.31.1

Anyone know why?

Edit:

Does anyone have a good guide on exactly how DHT works? Would it explain connections being made even when idle?

[Shryp]

The IP appears to be from China, but I have no idea why you would be connecting to it. I found this thread with a little more information, but judging on the context and time it was posted I am going to guess it is you.
https://community.mcafee.com/message/379681

DHT will always be active when enabled. Even if you are not downloading anything you are connecting to the network. Essentially it is a separate network that you get connected to and peers share tracker data among themselves so if a tracker goes down you can still download stuff.
http://bittorrent.org/beps/bep_0005.html
http://www.libtorrent.org/dht_extensions.html
http://en.wikipedia.org/wiki/Distributed_hash_table