Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to seed giant torrents: ProtocolException: Invalid message length received #653

Open
lostmsu opened this issue Apr 15, 2024 · 0 comments
Open

Unable to seed giant torrents: ProtocolException: Invalid message length received #653

lostmsu opened this issue Apr 15, 2024 · 0 comments

Comments

@lostmsu
Copy link

lostmsu commented Apr 15, 2024

MonoTorrent drops all incoming connections with

MonoTorrent.Client.ProtocolException: Invalid message length received. Value was 'XXXXXX'

I suspect this has to do with the fact, that a torrent like this has bitfield that is larger than PeerIO.MaxMessageLength.

Example torrent: https://1drv.ms/u/s!AioR7aFFo_FK1LdTfRnaXd70hiYopw?e=WV7OS6
lostmsu added a commit to lostmsu/MonoTorrent that referenced this issue Apr 15, 2024
@lostmsu
increase MaxMessageSize to 4MiB to support bitfields for larger torrents
a73d3e8 
workaround for alanmcgovern#653
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lostmsu