Follow-up Comment #5, bug #12490 (project mldonkey): I think the bug is solved.
In my opinion, it is not a bug that prevents mldonkey from connecting to the Fasttrack Network. I'd rather say it's because of Sharman Networks. I can't warrant it, but in December 2003, I read Sharman Networks was trying to prevent lite versions of kazaa from connecting to their network. It does not detect lightened versions, it stops older versions from connecting to the network. Newer versions of Kazaa which are supernodes would not accept connections from older versions. Of course, some supernodes are still old versions and mldonkey can connect to them, but it has to wait in order to find proper ones. Would it be possible to make mldonkey temporarily identify itself as a Kazaa 3. It may be a first workaround. I will try to provide an Ethereal dump of my K-Lite Resurrection 2.7.2 when it connects. Source: http://en.wikipedia.org/wiki/Kazaa_Lite "There are rumours that new versions of Sharman's Kazaa will prevent Kazaa Lite from connecting to the FastTrack network, but as of early 2005, this hasn't happened." It seems also it's not mldonkey's fault if bootstrap from fm2.imesh.com fails: http://www.filesharinghelp.com/internationalforums/index.php?showtopic=9807# Lite says : "The iMesh node can take a while to respond at times." _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=12490> _______________________________________________ Message post� via/par Savannah http://savannah.nongnu.org/ _______________________________________________ Mldonkey-bugs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/mldonkey-bugs
