Transmission supposedly reporting "fake traffic", got banned by Tracker

[ChrisKalania]

One of my "anti leech trackers" banned all recent versions of Transmission because it is supposedly reporting incorrect traffic. They only mention it in combination with Synology, but I guess they have no way to actually figure out what Transmission is running on, so all OSes are affected.

We noticed a lot of abnormal traffic events recently.
And, many users who got involved in those events, are using Transmission on Synology.
We have banned Transmission 2.77 and 2.82, and IT DOESN'T MEAN OTHER VERSIONS OF TRANSMISSION ARE SAFE.
We recommend using uTorrent instead.
Stop using Synology + Transmission NOW. Or, your client might report fake traffic to tracker, and you'll got your account banned.

------------------------------------------------------------------------------------

UPDATE: Transmission 2.84 and 2.42 on Synology have the same problem. We will ban those versions of Transmission soon.

[cfpp2p]

http://sourceforge.net/p/transmissionda ... dfad/#5c1a

[ChrisKalania]

Well, not really a solution for the underlying problem of Transmission reporting incorrect traffic (assuming there actually is one). I now switched to Deluge to avoid trouble.

[cfpp2p]

I've been using transmission on a private tracker for years with good standing and it has never reported false data. I did contact them to find out any experience they might have had with transmission reporting false data ( that didn't seem like user intentionally misreporting transfer statistics ) and sadly the result was yes. The issue seems to be a rare but frequently enough single announce events would contain a report of EXACTLY 8 exa byes transferred ( 9,223,372,036,854,775,808 ).

http://en.wikipedia.org/wiki/Tera-

1 exa byte = 2^60 = 1152921504606846976

http://stackoverflow.com/questions/3706 ... urn-0-mean
http://www.gnu.org/software/libc/manual ... d-NaN.html
-Wdiv-by-zero -- https://gcc.gnu.org/onlinedocs/gcc-3.2/ ... tions.html

64 bit integer
negative infinity
2^63 = 9223372036854775808

2^63 / 1 exa byte = 2^3 = 8 exa bytes

It was confirmed that in some (maybe all) cases Synology was involved so it seems like somehow Synology and transmission result in a divide by zero option, a ~0, negative infinity, or otherwise NaN value resulting to the announce.

I don't see any indication of an

underlying problem of Transmission reporting incorrect traffic

in the code but seemingly a problem with the Synology system or compile.

I now switched to Deluge to avoid trouble.