Haxe wrote: > Even if BearShare ultrapeers are no longer > listed in the bootstrapping databases, shouldn't they appear in my > cache after some network use?
My guess is that Limewire ultras don't connect to Bearshare so when you ping them, they tell you the ultras they're connected to, so you don't get to know about any Bearshares > Question: Is there nothing we could do on our own to prevent BearShare > from vanishing into their own island? This would obviously be bad for > all of us. What I do is open ~/.gtk-gnutella/ultras in a text editor, search for lines which end with :6346 (or 6348 - they're usually Bearshare) and then copy those addresses into the Add box on the GnutellaNet pane of Gtk-Gnutella. It takes a while but eventually one of them will connect. However, Bearshares prefer to connect to other Bearshare ultras and wouldn't choose to connect to a gtk-gnutella, so I only pick up more Bearshares when I drop below my minimum number of peers and start to ping for more. The problem there is that Limewire do choose to connect to me so I wouldn't normally fall below my minimum number of peers. To prevent too many Limewires connecting I set the maximum connections allowed per unique vendor (Preferences> GnutellaNet - it doesn't show that option unless you check the Expert mode box on the User Interface tab) at 68% Andy ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
