View Full Version : Can I get some more nodes?
bobhss
September 6th, 2002, 08:08 AM
My list of nodes has the following: connect1.gnutellanet.com:6346
connect2.gnutellanet.com:6346
connect3.gnutellanet.com:6346
connect4.gnutellanet.com:6346
gnotella.fileflash.com:6346
router.limewire.com:6346
public.bearshare.net:6346
gnutella-again.hostscache.com:6346
gnutella.hostscache.com:6346
router.limewire.com:6346
gnet.ath.cx:6346
gnet2.ath.cx:6346
gnet3.ath.cx:6346
gnet4.ath.cx:6346
gnet5.ath.cx:6346
gnutellahosts.com:6346
nova.yi.org:6346
Does anyone else have other ones that I don't know about?
whiff
September 8th, 2002, 08:27 AM
Greg Bildson reports some kind of hardware failure, is directing users to 208.239.76.100 which is a backup cache
Morgwen
September 8th, 2002, 09:40 AM
Originally posted by bobhss
gnotella.fileflash.com:6346
gnutella.hostscache.com:6346
These are dead hostcaches.
router.limewire.com:6346
Is only available for Limewire nodes.
Morgwen
bobhss
September 8th, 2002, 11:01 AM
Thanks guys. Love Gnutella, don't know much about it's inner workings(and don't figure I need to learn it now, just enough to share share share).
Sephiroth
September 8th, 2002, 11:53 AM
You only need ONE of those to get connected... Even if you have everyone thats avaible it wont improve gnutella as all because host caches are just lists of active hosts on the network used so people can easily get connected they dont improve searches and etc at all..
bobhss
September 8th, 2002, 08:39 PM
Yes, I am aware that the host caches only serve to get me connected to the network, but I had a couple of times recently when I couldn't get connected with that list of host caches. My Gnucleus would go through them all and then give me Cache Empty. The Cache would never get above 2.50% full each of my attempts. Usually it'll show Cache Full and I'll be connected to as many nodes as I've specifed if everything is working correctly.
Sephiroth
September 9th, 2002, 04:38 AM
You only get 10 hosts from a host cache so of course it will not fill the cache... Im guessing why it does that is because the hosts in the cache have expired or its been long enough that the program clears it and you have to start over as long as getting hosts and some of your cache filled then you are ok.