Deluge sending invalid BT message ID's?
Posted: Thu Oct 11, 2007 10:37 pm
Hi - Azureus dev here.
Been noticing recently that there have been some clients that I've connected to which appear to be sending BT messages with invalid ID's.
Added some more debugging code, and I got this:
So far, I've only seen one client (on one IP so far) do this - I'm sitting in some more swarms at the moment to see if there are any other clients which are doing this. Just wondered if you had any ideas?
(Further edit: Just seen what reserved bits are sent in the handshake by Deluge - it seems to support Fast Extensions. I believe that Deluge might be sending "Reject Request" messages without checking that the other client supports them?)
Thanks,
amc1.
Been noticing recently that there have been some clients that I've connected to which appear to be sending BT messages with invalid ID's.
Added some more debugging code, and I got this:
Code: Select all
Unknown BT message id [16]
Deluge 0.5.5 24.12.xxx.xxx Unknown BT message id [16](Further edit: Just seen what reserved bits are sent in the handshake by Deluge - it seems to support Fast Extensions. I believe that Deluge might be sending "Reject Request" messages without checking that the other client supports them?)
Thanks,
amc1.