Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#4746 closed Bug (wontfix)

DHT and PEX not limited by Turtle mode

Reported by: Aethylred Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.42
Severity: Normal Keywords:


When using Turtle mode to schedule idle times for transmission, transmission will continue to do DHT and PEX queries and responses.

This can add up to significant amounts of traffic (Gigabytes!) daily.

This behavior can be observed by setting Turtle bandwidth to 0 upload and download, and switching DHT and PEX on and off while monitoring network traffic.

I suggest that:

  • these features need to conform to the bandwidth limits
  • these features can be disabled during turtle mode

Though this bug does not impair Transmission's functionality it can cause unintentional effects on a Transmissions network performance, or their Internet bill if they have per Gigabyte charges.

Change History (2)

comment:1 Changed 11 years ago by jordan

  • Resolution set to wontfix
  • Status changed from new to closed

Hi Aethylred,

Thanks for the suggestion.

The behavior you're describing is intentional -- we only include piece data in our speed computations. When we included protocol overhead, several people complained that the torrent didn't seem to be downloading as quickly as the speed display indicated. :)

I strongly doubt that PEX will add up to Gigabytes daily. DHT probably has more overhead than PEX, but DHT can be disabled if you are short on bandwidth.

comment:2 Changed 11 years ago by Aethylred

Thanks for your response, but increasingly "disable DHT" means "disable bittorrent" :(

I understand not adding PEX and DHT to speed calculations, but what'd sort this out would be having some options:



That just shuts them off in alt-bandwidth (aka turtle) mode.

Note: See TracTickets for help on using tickets.