BearShare Forums  

Go Back   Gnutella Forums > Current Gnutella Client Forums > BearShare (Windows) > Host Connections
Register FAQ The Twelve Commandments Members List Calendar Arcade Search Today's Posts Mark Forums Read

Host Connections Discussions related to host connections for BearShare users. Problems connecting? See A technique for connecting with BearShare


Welcome To Gnutella Forums

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, fun aspects such as the image caption contest and play in the arcade, and access many other special features after your registration and email confirmation. Registration is fast, simple and absolutely free so please, join our community today! (click here)

If you have any problems with the Gnutella Forum registration process or your Gnutella Forum account login, please contact us (this is not for program use questions.) Your email address must be legitimate and verified before becoming a full member of the forums. Please be sure to disable any spam filters you may have for our website, so that email messages can reach you.
Note: Any other issue with registration, etc., send a Personal Message (PM) to one of the active Administrators: Lord of the Rings or Birdy.

Once registered but before posting, members MUST READ the FORUM RULES (click here) and members should include System details - help us to help you (click on blue link) in their posts if their problem relates to using the program. Whilst forum helpers are happy to help where they can, without these system details your post might be ignored. And wise to read How to create a New Thread

Thank you

If you are a Spammer click here.
This is not a business advertising forum, all member profiles with business advertising will be banned, all their posts removed. Spamming is illegal in many countries of the world. Guests and search engines cannot view member profiles.



Deutsch? . . . . Español? . . . . Français? . . . . Nederlands? . .
Hilfe in Deutsch, . Ayuda en español, . Aide en français . et . LimeWire en français, . Hulp in het Nederlands

Forum Rules

Support Forums

Before you post to one of the specific Client Help and Support Conferences in Gnutella Client Forums please look through other threads and Stickies that may answer your questions. Most problems are not new. The Search function is most useful. Also the red Stickies have answers to the most commonly asked questions. (over 90 percent).
If your problem is not resolved by a search of the forums, please take the next step and post in the appropriate forum. There are many members who will be glad to help.
If you are new to the world of file sharing please do not be shy! Everyone was ‘new’ when they first started.

When posting, please include details for:
Your Operating System ....... Your version of your Gnutella Client (* this is important for helping solve problems) ....... Your Internet connection (56K, Cable, DSL) ....... The exact error message, if one pops up
Any other relevant information that you think may help ....... Try to make your post descriptive, specific, and clear so members can quickly and efficiently help you. To aid helpers in solving download/upload problems, LimeWire and Frostwire users must specify whether they are downloading a torrent file or a file from the Gnutella network.
Members need to supply these details >>> System details - help us to help you (click on blue link)


Moderators

There are senior members on the forums who serve as Moderators. These volunteers keep the board organized and moving.
Moderators are authorized to: (in order of increasing severity)
Move posts to the correct forums. Many times, members post in the wrong forum. These off-topic posts may impede the normal operation of the forum.
Edit posts. Moderators will edit posts that are offensive or break any of the House Rules.
Delete posts. Posts that cannot be edited to comply with the House Rules will be deleted.
Restrict members. This is one of the last punishments before a member is banned. Restrictions may include placing all new posts in a moderation queue or temporarily banning the offender.
Ban members. The most severe punishment. Three or more moderators or administrators must agree to the ban for this action to occur. Banning is reserved for very severe offenses and members who, after many warnings, fail to comply with the House Rules. Banning is permanent. Bans cannot be removed by the moderators and probably won't be removed by the administration.


The Rules

1. Warez, copyright violation, or any other illegal activity may NOT be linked or expressed in any form. Topics discussing techniques for violating these laws and messages containing locations of web sites or other servers hosting illegal content will be silently removed. Multiple offenses will result in consequences. File names are not required to discuss your issues. If filenames are copyright then do not belong on these forums & will be edited out or post removed. Picture sample attachments in posts must not include copyright infringement.

2. Spamming and excessive advertising will not be tolerated. Commercial advertising is not allowed in any form, including using in signatures.

3. There will be no excessive use of profanity in any forum.

4. There will be no racial, ethnic, or gender based insults, or any other personal attacks.

5. Pictures may be attached to posts and signatures if they are not sexually explicit or offensive. Picture sample attachments in posts must not include copyright infringement.

6. Remember to post in the correct forum. Take your time to look at other threads and see where your post will go. If your post is placed in the wrong forum it will be moved by a moderator. There are specific Gnutella Client sections for LimeWire, Phex, FrostWire, BearShare, Gnucleus, Morpheus, and many more. Please choose the correct section for your problem.

7. If you see a post in the wrong forum or in violation of the House Rules, please contact a moderator via Private Message or the "Report this post to a moderator" link at the bottom of every post. Please do not respond directly to the member - a moderator will do what is required.

8. Any impersonation of a forum member in any mode of communication is strictly prohibited and will result in banning.

9. Multiple copies of the same post will not be tolerated. Post your question, comment, or complaint only once. There is no need to express yourself more than once. Duplicate posts will be deleted with little or no warning. Keep in mind a forum censor may temporarily automatically hold up your post, if you do not see your post, do not post again, it will be dealt with by a moderator within a reasonable time. Authors of multiple copies of same post may be dealt with by moderators within their discrete judgment at the time which may result in warning or infraction points, depending on severity as adjudged by the moderators online.

10. Posts should have descriptive topics. Vague titles such as "Help!", "Why?", and the like may not get enough attention to the contents.

11. Do not divulge anyone's personal information in the forum, not even your own. This includes e-mail addresses, IP addresses, age, house address, and any other distinguishing information. Don´t use eMail addresses in your nick. Reiterating, do not post your email address in posts. This is for your own protection.

12. Signatures may be used as long as they are not offensive or sexually explicit or used for commercial advertising. Commercial weblinks cannot be used under any circumstances and will result in an immediate ban.

13. Dual accounts are not allowed. Cannot explain this more simply. Attempts to set up dual accounts will most likely result in a banning of all forum accounts.

14. Video links may only be posted after you have a tally of two forum posts. Video link posting with less than a 2 post tally are considered as spam. Video link posting with less than a 2 post tally are considered as spam.

15. Failure to show that you have read the forum rules may result in forum rules breach infraction points or warnings awarded against you which may later total up to an automatic temporary or permanent ban. Supplying system details is a prerequisite in most cases, particularly with connection or installation issues.

Violation of any of these rules will bring consequences, determined on a case-by-case basis.


Thank You! Thanks for taking the time to read these forum guidelines. We hope your visit is helpful and mutually beneficial to the entire community.


Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old February 21st, 2014
Lord of the Rings's Avatar
ContraBanned
 
Join Date: June 30th, 2004
Location: Middle of the ocean apparently (middle earth)
Posts: 993
Lord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputation
Default Firewalled BearShare 5.1 Beta Ultrapeers - The Majority

From what I can ascertain, a high percentage of those using BearShare 5.1 Beta are semi/totally-firewalled. Out of 11 BearShare 5.1 Beta peers I was connected to, only 3 such peers had more than one Leaf connected to them (or 2 out of 10 since one peer was mine). The other BS I had running had 3 out of 6 with more than one leaf connected to them (again, one being mine). All were the BS 5.1 beta versions. This suggests their BearShare is firewalled. The only reason an ultrapeer would have less than a few Leaves connected would be because they are firewalled in my own experience. (10 hours later & the ratio was 5/13 non-firewalled overall & 2/10 non-firewalled BS 5.1 beta peers.)
This does not seem to apply to other BS versions because they undoubtedly would not be able to become ultrapeers if their BS was firewalled.

BS 5.1 does not have UPnP support or any other port mapping technology. Thus, to run properly as an ultrapeer, BS 5.1 needs to be port forwarded through a router-modem so messages between hosts are not being blocked. I needed to port forward my router for each of my BearShares running on different Windows systems & using different ports. My five BearShares are not firewalled.

If anybody needs any assistance to port forward your BearShare, you can either ask on this forum or else, ask at the portforward.com website. That site has very good guides for the majority of routers available. ie: Router Port Forwarding Guides - PortForward.com (1) you select your brand of router, skip advertisements by choosing close on next window, (3) select your model of router, (4) select the program you wish to port forward for. Then follow the instructions. Sample images are supplied. The BearShare instructions they supply are for the original BearShare 5 version.

Some people seem to think that port forwarding a router is some complex scientific mathematical formula, but it's really not. Some routers require more steps than others. If you need help you can always ask here or at portforward.com.

Once your BearShare is port forwarded properly, you will find very notable improvements in performance for yourself. Your search results will improve & amplify greatly. It will also greatly help the other BS peers & gnutella community. And others will find it easier to connect to you & vice versa. An ultrapeer blocking incoming/outgoing messages is not good for the network. And some of the newer client versions such as GTK-Gnutella will refuse to connect to firewalled ultrapeers. Being connected for 12 days straight whilst firewalled & without being connected to Leaves does not benefit anybody & blocks lots of messages such as others searches passing through your bearshare at same time. (Have you ever done a search & not got many results? Chances are some of your search results were blocked by firewalled ultrapeers nearby you. This is why firewalled ultrapeers rarely have Leaves connect to them.)

Firewalled BearShare 5.1 Beta Ultrapeers - The Majority-bs-5.1-firewalled-ultrapeers.png (click attachment to see larger view) . (I squashed everything up a little in the image to try to keep the image small'ish.)

The attachment above shows BearShare 5.1 Beta ultrapeers (Peers) underlined in green to show those that are obviously firewalled. The background is blue because all hosts have been selected. As you can see looking at the Leaves column far right-side of the image, those peers only have between zero to 2 Leaves each. Despite their good minds to stay connected for long periods, their firewalled status steals much of that help away from the network. There are lots of BearShare Leaves that are unable to become ultrapeers & desparately look for BearShare ultrapeers to connect to (that's the way BearShare was designed.)

Of the 3 beta version peers not firewalled, one is mine running from a different Windows system. You will also see I highlighted being connected to 45 Leaves out of a possible 45 leaves (100%) & also highlighted that my BS 5.1 beta is neither TCP or UDP firewalled.
The Beta with only 35 Leaves had only been connected 19 mins & was still establishing themselves. Though lack of bandwidth can possibly be a cause of not filling up all the leaf allocations. I usually connect to 45 leafs within 5-10 mins. And 37 of those are BearShare leafs. The other leafs are usually ShareAza with lots of shared files.

BearShare is an old gnutella technology that still uses GWebCache to connect with. It's even less suiting to the network when 2/3 to 3/4 of the BearShare ultrapeers are firewalled. It's sort of no wonder why a lot of the UDP port packet send out checks fail because so many of the hosts around the BearShare you are using are themselves UDP firewalled & fail to receive the UDP messages/requests, thus giving your BS the UDP firewall message periodically. I can verify this happening after a restart & first peer connected to was firewalled which gave my UDP firewalled status for an hour (but was then ok. BS only checks once/hr.)

We can only help you if you start by trying and helping yourself first. ... It would be nice if we could clean up the BearShare 5.1 Beta pool of peers to be non-firewalled. I doubt anybody will take notice or the slightest care. As I just might lose interest in keeping up the connection updates for people who simply do not care. I've got lots of other things i could be doing.
Reply With Quote
  #2 (permalink)  
Old February 23rd, 2014
Lord of the Rings's Avatar
ContraBanned
 
Join Date: June 30th, 2004
Location: Middle of the ocean apparently (middle earth)
Posts: 993
Lord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputation
Default

And again. I guess most are from USA. One from Europe. 9 out of 13 BS 5.1 Beta ultrapeers firewalled. Or should I say, 4 out of 13 not firewalled.
I've started to mark on my list those firewalled. Also made adjustments to the connection file for those needing a fresh connection file. Otherwise connecting to a firewalled peer initially will give your BS the idea it is UDP firewalled when it might not be after all. And it's pointless even attempting to connect to firewalled ultrapeers via UDP when such messages will be blocked & thus all firewalled hosts are starting to be removed from the UDP connection list. It's a toss of the coin as to whether your BS sends test packets to a firewalled peer or non-firewalled peer. So I'm shifting the non-firewalled hosts to the top of the list. Yes it does make a difference, if BS thinks it is UDP firewalled, it slows connections down because it seems to communicate to others that it is firewalled when it might not really be. I hope that makes sense. ie: a firewalled ultrapeer affects those around it one way or another by blocking messages.

I did a test between two of my BearShares. One initially showed UDP firewalled, the other not. I was unable to connect them to each other. An hour later when BS rechecked & discovered it was not really UDP firewalled, I then had no problem getting them to connect to each other.

I can verify that when I connect to a non-firewalled BS peer first, my UDP port tests always seem to pass. Whereas if I connect to a firewalled BS peer they fail & need to wait an hour before it re-tests.

Firewalled BearShare 5.1 Beta Ultrapeers - The Majority-bs-beta-firewalled-hosts.png (Those underlined have less than 3 Leaves connected to them because they are firewalled. Most of them have zero Leaves. I feel sorry for any Leaves connected to a firewalled BS 5.1 beta ultrapeer.)

Edit: Here's a very sad ugly situation. 9 Firewalled BS 5.1 Beta ultrapeers. The only non-firewalled BearShares are the two BS Light versions which would not be able to become ultrapeers anyway if they were firewalled:

Firewalled BearShare 5.1 Beta Ultrapeers - The Majority-bs5.1betafirewalledagain.png (this is very damaging to the network with so many firewalled ultrapeers. You will notice that the two BS Light versions have a high number of Leaves through the other peers they are connected to, meaning much better search results. This snapshot was taken from Win2K. I'd be thinking the first peer listed would probably get poor search results. 8 out of 9 of these BS 5.1Beta peers are from USA, the other from Europe.)
Firewalled Ultrapeers cannot utilize the UDP port & thus not function properly as an ultrapeer, & are restricted to limited TCP communications.
Let's hope the USA BearShare 5.1 Beta users can start to change this trend. Yes, that means port forwarding the port BearShare is using (default port used is 6346) in your modem-router.

Last edited by Lord of the Rings; February 25th, 2014 at 03:31 AM. Reason: Added 2nd image
Reply With Quote
  #3 (permalink)  
Old May 20th, 2014
Lord of the Rings's Avatar
ContraBanned
 
Join Date: June 30th, 2004
Location: Middle of the ocean apparently (middle earth)
Posts: 993
Lord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputation
Default

I was somewhat surprised & pleased to see a BearShare 5.1 Beta peer that had been a firewalled peer for the past 5 months suddenly show up as non-firewalled. Plus they were sharing lots of files and over 4 days uptime. Now a totally responsible, respectable and valuable peer for both the BearShare and Gnutella community. Accolades to them for taking the effort.

I first sighted this peer mid-December. I suspect they were previously one of the firewalled culprits in the snapshots in my previous posts above. Good effort of them to become a non-firewalled user. And I have no doubt they are enjoying their experience a lot more with far better results.

I'd been busy over past week (such as with WS tasks) so hadn't used BS for previous 6 days.
Reply With Quote
  #4 (permalink)  
Old June 7th, 2014
Lord of the Rings's Avatar
ContraBanned
 
Join Date: June 30th, 2004
Location: Middle of the ocean apparently (middle earth)
Posts: 993
Lord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputationLord of the Rings has a distinguished reputation
Default

Quote:
Originally Posted by Lord of the Rings View Post
I was somewhat surprised & pleased to see a BearShare 5.1 Beta peer that had been a firewalled peer for the past 5 months suddenly show up as non-firewalled. Plus they were sharing lots of files and over 4 days uptime. ...
Well, that barely even lasted one month. Now that host is TCP & UDP firewalled again. Good luck with that.
I'm guessing they forgot to set up a static internal address so their internal 192. or 10. address did not change between reboots. If it changes then the port forward rule would not work because it was set under a different address. (eg: 10.1.1.3 instead of 10.1.1.2) . .
enough . . . . .
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


LinkBacks (?)
LinkBack to this Thread: http://www.gnutellaforums.com/host-connections/102633-firewalled-bearshare-5-1-beta-ultrapeers-majority.html
Posted By For Type Date
Site Gnutella Forums | www.gnutellaforums.com | BoardReader This thread Refback July 23rd, 2014 07:05 PM


All times are GMT -7. The time now is 12:52 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2015 Gnutella Forums.
All Rights Reserved.