Buffalo Forums

Products => Solved Storage Threads => : Sybaris December 30, 2009, 04:19:54 PM

: Peer ID for Linkstation Live Bittorrent Client
: Sybaris December 30, 2009, 04:19:54 PM
   

I  use the inbuilt bittorrent client on my linkstation live successfully on a number of private trackers.  However, one particular site has a whitelist of allowed clients, and blocks all unknown clients from connecting to its tracker.

 

The site admins have asked I provide them with the "peer id" for the linkstation's bittorrent client, so they can add it to their whitelist.  I know it identifies itself as BitTorrent SDK 2.0, but perhaps there is another sort of id for the client?b

 

 

I have a Linkstation Live 1tb LS-CHL running firmware 1.07

 

 

: Re: Peer ID for Linkstation Live Bittorrent Client
: Sybaris January 02, 2010, 05:18:41 AM
   

Anyone?  :smileyindifferent:

 

I need the peer id for the bittorrent client...

: Re: Peer ID for Linkstation Live Bittorrent Client
: Sybaris January 07, 2010, 06:22:17 PM
   

 


A number of clients begin the peer id with a dash followed by two characters to identify the client implementation, four ascii digits to denote version number, and a dash. As with mainline, the remaining bytes are random. An example is -AZ2060-.

 

This is the sort of peer id that I am looking for.  Can anyone help me out with the Peer ID for the linkstation bittorrent client?

 

: Re: Peer ID for Linkstation Live Bittorrent Client
: Colin137 January 09, 2010, 04:14:57 PM

I just ran a packet tracer on my LS-CHL v2 1.21 firmware, the complete peer_id tag is "-BE2000--zYbOMx.PK07" without quotes. The peer id that you're asking for then appears to be "-BE2000--"

: Re: Peer ID for Linkstation Live Bittorrent Client
: Sybaris January 10, 2010, 05:25:32 AM
   

Thank you Colin137.  Thats the one! :smileyvery-happy:

: Re: Peer ID for Linkstation Live Bittorrent Client
: Colin137 January 11, 2010, 05:22:59 PM

You might want to double check yours, just in case it's randomly generated. Run a packet sniffer (wireshark makes it easy) and look for the first broadcast packet sent out by the client.