mcaspi Posted June 21, 2012 Report Share Posted June 21, 2012 Sometimes I am connected to throttled peers like other users. At some point uT will ban these peers. So what you get is that throttled users suffer twice, once from their ISP and once from uT. Here is an example of a throttled banned peer.[2012-06-21 12:30:55] .6.250:62369 [uTP](): [bitTorrent 7.6.1 (42.5)]: Got PEX: 1 added/0 dropped[2012-06-21 12:30:55] .6.250:62369 [uTP](): [bitTorrent 7.6.1 (42.5)]: Got PEX: 0 added/1 dropped[2012-06-21 12:30:55] .6.250:62369 [uTP](): [bitTorrent 7.6.1 (42.5)]: Got PEX: 1 added/0 dropped[2012-06-21 12:30:55] .6.250:62369 [uTP](): [bitTorrent 7.6.1 (42.5)]: Got PEX: 0 added/1 dropped[2012-06-21 12:30:55] .6.250:62369 [uTP](): [bitTorrent 7.6.1 (42.5)]: Got PEX: 0 added/1 dropped[2012-06-21 12:30:55] .6.250:62369 [uTP](): [bitTorrent 7.6.1 (42.5)]: Banning peer: too many pex messages. 5 since Thu Jun 21 12:30:55 2012[2012-06-21 12:30:55] .6.250:62369 [uTP](): [bitTorrent 7.6.1 (42.5)]: Disconnect: PEX message flood Link to comment Share on other sites More sharing options...
tufavideo_net Posted July 17, 2012 Report Share Posted July 17, 2012 I do not wish to ban a Pees based upon some silly 5 PEX messages! What can I do about it? I only wish to ban a peer if he run hacked software and running a denial of service attack. Link to comment Share on other sites More sharing options...
mcaspi Posted July 17, 2012 Author Report Share Posted July 17, 2012 Persuade the developers to change the PEX mechanism? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.