Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

Can Tixati Ban Backwards Downloading Peer - 100%, 99%, 98%

by Guest on 2021/07/23 10:56:35 PM    
Hello!

I'm getting a weird one today,

I added this download and this specific peer was 100%, then the peer started going backwards. 100-99-98-97-96% ​then disconnects
I think this is SPOOFING (timewasting) by a client as they do not send any data, only few Kb at most.

Can the DEVs please de-prioritise these users IE apply VL bandwidth or auto-ignore the users who "drop pieces" in this manner?

THANKS!

[21:07:10]  initiating connection
[21:07:13]  securing connection
[21:07:17]  sent handshake
[21:07:27]  error: Timed out logging in
[21:07:27]  stopping
[21:07:56]  starting
[21:07:58]  initiating connection
[21:07:59]  securing connection
[21:08:03]  sent handshake
[21:08:04]  logged in
[21:08:04]  sent bitfield
[21:08:07]  remote is partial seed
[21:08:07]  remote is complete seed
[21:08:07]  received bitfield, 1,025 of 1,025 pieces complete               <----- Remote End declares they have 100%
[21:08:07]  remote unchoked local
[21:08:10]  local interested in remote
[21:08:11]  remote unchoked local
[21:08:12]  attached piece 206                                              <----- OK send Tixati piece 206
[21:08:12]  send block request, piece=206 offset=425,984 size=16,384
[21:08:12]  send block request, piece=206 offset=638,976 size=16,384
[21:08:13]  remote dropped piece 206                                        <----- No you can't have piece 206 (peer then drops to 99%)
[21:08:13]  detaching piece 206
[21:08:13]  send block request cancellation, piece=206 offset=425,984
[21:08:13]  send block request cancellation, piece=206 offset=638,976
[21:08:13]  detached piece 206
[21:08:16]  remote dropped piece 206
[21:08:19]  attached piece 649                                              <----- Send piece 649 instead
[21:08:19]  send block request, piece=649 offset=442,368 size=16,384
[21:08:19]  send block request, piece=649 offset=458,752 size=16,384
[21:08:21]  local unchoked remote
[21:08:24]  sent PEX message
[21:08:26]  remote dropped piece 649                                        <----- No you can't have piece 649
[21:08:26]  detaching piece 649
[21:08:26]  send block request cancellation, piece=649 offset=442,368
[21:08:26]  send block request cancellation, piece=649 offset=458,752
[21:08:26]  detached piece 649
[21:08:28]  remote dropped piece 649
[21:08:30]  attached piece 28
[21:08:30]  send block request, piece=28 offset=884,736 size=16,384
[21:08:30]  send block request, piece=28 offset=901,120 size=16,384
[21:08:32]  remote dropped piece 28                                         <----- No you can't have piece 28 (peer then drops to 98%)
[21:08:32]  detaching piece 28
[21:08:32]  send block request cancellation, piece=28 offset=884,736
[21:08:32]  send block request cancellation, piece=28 offset=901,120
[21:08:32]  detached piece 28
..........
[21:15:03]  error: Connection reset (10053) (10:10053)
[21:15:03]  stopping
[21:15:07]  starting
[21:15:07]  initiating connection
[21:15:09]  securing connection
[21:15:10]  sent handshake
[21:15:12]  logged in
[21:15:12]  sent bitfield
[21:15:12]  remote is partial seed
[21:15:12]  remote is complete seed
[21:15:12]  received bitfield, 1,025 of 1,025 pieces complete               <----- Peer declaring 100% again (repeat 100-99-98% etc)
[21:15:12]  local interested in remote
[21:15:14]  local unchoked remote
[21:15:25]  received PEX message
[21:15:32]  sent PEX message
by Guest on 2023/07/26 05:33:29 PM    
Seeing this again weird behavior,

Backwards downloading, REMOTE SIDE PEER showing = 100%, 99%, 98%, 97%, (peer connection reset) - REMOTE SIDE PEER showing = 100%, 99%, 98%, 97% (etc)


PEER CLIENT = libtorrent/1.2.2.0

[18:22:48]  error: Remote disconnected
[18:22:48]  stopping
[18:22:54]  starting
[18:22:54]  initiating connection
[18:22:54]  securing connection
[18:22:54]  sent handshake
[18:22:55]  logged in
[18:22:55]  sent bitfield
[18:22:55]  remote is partial seed
[18:22:55]  remote has all pieces              <------- PEER supposedly has "100%" (graphic bar chart says 100%)
[18:22:55]  remote is complete seed
[18:22:55]  remote unchoked local
[18:22:55]  local interested in remote
[18:22:55]  attached piece 791
[18:22:55]  remote unchoked local
[18:22:55]  remote dropped piece 791
[18:22:55]  detaching piece 791
[18:22:55]  detached piece 791
[18:22:55]  remote dropped piece 791
[18:22:56]  attached piece 1,028               <------- PEER graphic bar chart says 99% (backwards downloading)
[18:22:57]  remote dropped piece 1,028
[18:22:57]  detaching piece 1,028
[18:22:57]  detached piece 1,028
[18:22:57]  remote dropped piece 1,028
[18:22:58]  attached piece 1,441
[18:22:59]  local unchoked remote
[18:22:59]  remote dropped piece 1,441         <------- PEER graphic bar chart says 98% (backwards downloading)
[18:22:59]  detaching piece 1,441
[18:22:59]  detached piece 1,441
[18:22:59]  remote dropped piece 1,441
[18:23:00]  attached piece 1,025
[18:23:01]  remote dropped piece 1,025         <------- PEER graphic bar chart says 97% (backwards downloading)
[18:23:01]  detaching piece 1,025
[18:23:01]  detached piece 1,025

connection drops then repeat.... (different pieces in logs each time)


Starts back off at 100% again.

Anyone know what the logs are telling us? Pieces are failing hash-check ???
by notaLamer on 2023/08/12 12:29:53 AM    
How does that peer identify itself (client) and where is it hosted (search its IP online and it should point to the company). I suspect its one of the surveillance peers.

See for more info https://forum.tixati.com/offtopic/413




This web site is powered by Super Simple Server