[bittorrent] Bitfield data... First bits meaning?
alan.mcgovern at gmail.com
Sat Dec 9 10:15:35 EST 2006
Is BitComet the only client that does this? Are you testing this on your
localhost using Bitcomet as a seeder? What happens if you use uTorrent or
If Bitcomet really is a seeder, then it'd be a bit odd if it wasnt sending a
complete bitfield. Is it a setting somewhere to help avoid traffic shaping
as Adrian said?
On 12/9/06, Adrian Ulrich <torrent at blinkenlights.ch> wrote:
> > But what I actually get is:
> > <len=0001+X><id=5><bitfield=00001111111111111111111111000000...>
> > I also know that I'm receiving this bitfield from a BitComet client...
> - How do you know that this client is a seeder?
> - A seeding client may choose to send an incomplete bitfield and
> fillup the missing parts with 'have' messages.
> (Obscure workaround for ill-Traffic-Shaping or Seeding 'help')
> - Verify that you are reading at the correct offset/data using
> a network sniffer like 'wireshark' 
> 1: http://www.wireshark.org/download.html
> (aka Ethereal)
> A. Top posters
> Q. What's the most annoying thing on Usenet?
> BitTorrent mailing list
> BitTorrent at lists.ibiblio.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the BitTorrent