I've installed BS in the same network and tried to get some file from it but failed... Downloads return 404 file not found...

Is it something occasional, or does they really bann all or some non-BS servents? or is it just about mutella?

--Max

Follow up: I've tested Gnucleus and Gtk-Gnutella, they both cannot get anything from the Bs server I run in the same net!

Comments?

Since the inception if the BearShare 4.0 series, BearShare has created it's own little island in the Gnutella network. This is due to an accidental change that reworked BearShare's host pirorities.

Did somebody reverse-ingeneered their handshake to get the files shared by BS clients back to the Gnutella community? Or shall we simply ignore results from BS to reduce frustration?

--Max

P.S.: it appears that BS simply parasites on the gnutella network... Shall we, client developers, simply bann'em?

BearShare does have connections with the rest of the Gnutella network, it's just the BearShare clients perfer other BearShare clients over other Gnutella clients.

In response to second comment: No, don't block BearShare. And how does BearShare parasite on the Gnutella network? Using BearShare I still get the same results as the rest of the Gnutella network.

Nope, you missed my point: BS clients CAN download files from the rest of gnutella network, but other clients, like Gnucleus, Gtk-Gnutella, Mutella and I guess more CANNOT download files from BS back. This way the BS subnet in gnutella-net is nothing else than a bunch of freeriders, because they do not share files back to the whole of Gnutella but still consume upload slots. Typical freeriding, nothing else!

With this regard, I propose not to bann them from the net completely, no, but rather just stop sharing files to them. I do realise that it's difficult to do and that if really major clients go for that than the next release of BS will replace User-Agent header in it's download request... but still, something HAS TO BE DONE! This kind of behaviour is just antisocial!


--Max

No, BearShare has limited downloading and uploading capability with the rest of the Gnutella network. In a normal BearShare session, the amount of non-BearShare clients in the horizon may only be 5-10%. This makes it hard for BearShare to find and download / upload files to non-BearShare clients.

Thanks for your help, but I've resolved the issue. The problem appeared because I've started BS on somebody elses PC and had to share files from the network drive. Apparently BS has a bug which stops it from sharing such files? I was constantly getting 404 errors. After I shared local files I could get them with Gnucleus, but not with GtkGnutella.

Anyways, lets say it like that: I've changed my mind for now, we will not bann BS :-))

--Max

Here's a picture. As you can see, BearShare doesn't have many non-bearshare clients in its horizon. (Freepeers means the number of BearShare clients, and Secure means the number of BearShare clients that can use authentication)

Attached Images

nonbs.png (1.1 KB, 404 views)