Re: Free rider problem

>From: guanying_wang <[email protected]>
> I have figured out a solution, but I have never implemented it. 
> First, I assume the peers bind to unique IP addresses.   So I can just
> remember every IP and their total upload to me, and base on these
> info, decide which peers should I choke.  Another restriction is only
> one connection per ip, because I have to remember IP-total pairs, two
> connections from the same ip will be confusing.

Not quite right. Multiple peers /could/ be NATed behind a single IP
address. If these are bandwidth limited individually behind the NAT, you
could get better bandwidth talking to both. At the same time if you throw
out the port, then you could end up unchoking the wrong one.

At the same time you should be controlling optimistic unchokes to on a
per-address basis so that you avoid the above. This then gets interesting
that an attacker with multiple IP addresses (either all on one machine or
a cluster of systems) could do a group attack against you. Also with a
sufficiently large swarm you could avoid reconnecting to the same peer
twice.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \   (    |         [email protected] PGP 8881EF59         |    )   /
  \_  \   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
    \___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/




------------------------ Yahoo! Groups Sponsor --------------------~--> 
$4.98 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/dkFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/BitTorrent/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/