When I run the BearShare 5.1.0.25 Beta without being firewalled as an ultrapeer, I get mixed results from GTK ultrapeers. Some give a message saying not a gnutella member, some auto-ban my ip address, yet at some stage a GTK or more might even connect with my BearShares. There appears to be a lack of consistency.
Code:
Auto Host x.x.x.x:xxxx ("gtk-gnutella/1.1.8 (2015-12-18; GTK2; Linux x86_64)") dropped: response code: 403 'Not a network member'
-- Handshake 1 OUT --
.... (abilities check)
-- Handshake 2 IN --
GNUTELLA/0.6 403 Not a network member\r\n
etc. I can understand GTK not wishing to connect with BearShare due to its very old gnutella technology; lack of deflate & other search handling/cache & connection abilities & approach.
Code:
Auto Host x.x.x.x:xxxx ("gtk-gnutella/1.1.6 (2015-11-08; GTK2; Linux i686)") dropped: response code: 550 'Hostile IP address banned'
-- Handshake 1 OUT --
GNUTELLA CONNECT/0.6\r\n
.... (abilities check)
-- Handshake 2 IN --
GNUTELLA/0.6 550 Hostile IP address banned\r\n
User-Agent: gtk-gnutella/1.1.6 (2015-11-08; GTK2; Linux i686)\r\n
Remote-IP: x.x.x.x\r\n
X-Live-Since: Tue, 22 Dec 2015 20:40:32 -0600\r\n
\r\n Banning the ip address? That's a bit severe!
I'm almost slightly amused because the GTK peer auto-banning my ip I presume also blocks all communications with my ip. That means anywhere up to 15,000 files shared between my three apps (two presently 24/7) will be inaccessible to this GTK host. Also with one app running in DHT, I presume this might also affect both this GTK & possibly it's leafs search results.
I don't mind freeloaders auto-banning me though.
One side-effect of auto-ban is it possibly affecting BearShare's UDP & TCP packet testing.
Code:
Auto Host x.x.x.x:xxxx ("gtk-gnutella/1.1.6 (2015-11-08; GTK2; Linux x86_64)") dropped: response code: 403 'Not a network member
'
-- Handshake 1 OUT --
GNUTELLA CONNECT/0.6\r\n
User-Agent: BearShare 5.1.0b25\r\n
.... (abilities check)
-- Handshake 2 IN --
GNUTELLA/0.6 403 Not a network member\r\n
User-Agent: gtk-gnutella/1.1.6 (2015-11-08; GTK2; Linux x86_64)\r\n
Remote-IP: x.x.x.x\r\n
\r\n This one is same version (except it's 64-bit) as the one that auto-banned yet it responds with a 403 message instead.
Now the extra step of inconsistency:
gtk-gnutella/1.1.8 (2015-12-18; GTK2; Linux x86_64) connected to both of the BearShare's. So did gtk-gnut/1.1.7 (2015-12-13; Lin)
The BearShare community is incredibly small these days; nearing extinction. A year ago up to mid-year this year the number of UP's seen over a week was around 15, now it's around or under 10. Half of those are non-firewalled. Unfortunately it saddens me to see the 24/7 BS UP's are firewalled BS5.1Beta users using forced-UP mode. I can understand GTK blocking out the firewalled UP's, but perhaps a little disappointing the non-firewalled UP's are treated with contempt!
Even the BS leaf population has shrunk from between 300-400 connections between peers down to around 60 or less since a year ago.