If you want to support Gnutella, but don't have the ressources to share or act as an Ultrapeer, you may have webspace so you can upload a GWebcache.

PHP Cache: http://gnucleus.sourceforge.net/gweb...cgi-0.9.1b.txt

ASP.NET Cache: http://www.guox.de/pub/lynnx.zip

ASP Cache: http://www.guox.de/pub/lynn0.4.zip

Many people stopped running a GWebcache because they were afraid of getting DOSed and overrun by the enormeous amount of requests. This problem was mainly caused by an old malfunctioning client, the problem is fixed now since these buggy versions have been replaced. The rule is: The more caches are online, the lesser requests you will get.
If you are still afraid you might want to check out LynnX, the ASP.NET version of GWebcache. Using LynnX you can limit the requests you want to handle for each hour, if this limit is exceeded your cache will spit out ERRORs thus balancing the load.

Many people have been asking on how to report their new GWebCache to the world. One way to do it is the following:

Get several URLs of caches that you know are working.
Open your favorite web browser. For each of the working caches, enter the following in the address bar:
http://url_of_working_cache?client=TEST&version=1.0&updat e=1&url=http://url_of_your_cache
(where "url_of_your_cache" is of course your cache's actual URL)
Once your cache starts getting requests, you are all set to go. Note that it may take up to a week for your cache to get a normal number of requests.

__________________
Never touch a running system.
www.guox.de

A few working URLS
http://www.zadox.com/gwebcache
http://www.globalspot.net/gcache.php
http://www.netsoc.ucd.ie/~roberth/GnuCache/gcache.php
http://www.guox.de/lynnx.aspx
http://www.wtndrifters.com/gcache.php
http://cs-people.bu.edu/leith/gnuCache/gcache.php

__________________
Never touch a running system.
www.guox.de

taken from: http://gnutellaforums.com/showthread...threadid=21955

Running a Gwebcache on Mac OS X

Salut tout le monde,
I'm here to tell you how to improve the gnutella network by increasing the number of gwebcaches. It can be an interesting pet project for learning how webserving works and for leading you to hosting your website and share photos, videos and infos with friends,family.

What is a gwebcache?
-It is the entry point for gnutella servents such as LW, Acquisition, Bearshare, Gnucleus and many others. When you first download a servant (or if it has been lot of time since you last ran of a client), the servant doesn't have ultrapeers IP to connect too. It then connects to gwebcaches (websites) to retrieve ultrapeers IP so you can connect. Also, you might argue that it is cool to be involved in gnutella expension (It is).

Why adding one cache (gwebcache) if there are already more than 200 caches?
-Because increasing the number of gwebcaches decrease the number of requests for a particulate cache (many are now swamped by requests as requests are high these months for example LW requests have tripled in 6 months). For example if there are 200 caches and 200 000 requests/hour, each cache will be hit 1000 times/hour. However if the number of gwebcaches is higher, say 500, it means 400 requests/hour or a decrease in requests by 60%.

Is it legal?
-Yes. Even in the US! You are only keeping IP addresses of ultrapeers and addresses of other gwebcaches in memory, and gnutella use is not forbidden because there are many legal uses of P2P (Linux distros, your music band…).

What do I need to have a gwebcache?
1)a connection to the internet and a computer nearly always on like 95% of the time.
2)about a gig of bandwidth available per month
3)a fixed IP (ie your address is always static or the same ie 203.25.16.15. You can ask your ISP about it).
OR
if you have a dynamic ip, you have to suscribe to a dynamic DNS provider to register a domain for linking a web address to your machine (I use dyndns.org for updating the IP of my myname.dyndns.org and) and a deamon to update your IP by contacting dynsdns.org each 15 minutes (I use dnsupdate on versiontracker).
4)web sharing enabled in sharing of system preferences
5)PHP enabled (look at http://www.macosxhints.com/article....030124054236237 )
6) a gwebcache script (available at http://www.gnucleus.com/gwebcache/d...cache-0.7.5.zip )
7) Port 80 open:
If you have a router you'll have to forward the port 80 to the lan (ie 192.168.1.100) address of your machine
If you have a firewall, you'll have to open port 80

Installing the gwebcache script:
Put the folder gwebcache-0.7.5 (after unzipping it) in harddrive/library/webserver/documents/
(Documents is the folder you can put an index.html if you want to build your personnal website. Mozilla (mozilla.org) has a composer component that makes it easy to build a basic website)

Verifying if it works:
Go in your web browser, type your website address (or your fixed IP)
ie myname.dyndns.org/gwebcache-0.7.5/gcache.php
You should see a Gwebcache title. If you click on the stats link, you should see the servants that connected to your server last hour and this hour.

Reporting your gwebcache to the rest of the world (you won’t have any hits on your cache if you don’t do this step):
Go at http://gwebcache.jonatkins.com/ in the submit field and copy your address ie myname.dyndns.org/gwebcache-0.7.5/gcache.php

Afterwards (might be days after you reported your cache), you'll be able to verify the strength of your cache by visiting
http://gcachescan.jonatkins.com/

Bonne chance à tous!

For more infos : http://gnucleus.com/gwebcache/ forum about gwebcaches at http://www.c0re.net/gnuforum/viewforum.php?f=7

If you ever intend on taking down your gwebcache site, it's a bad idea to put it up, as can be read about here.

http://www.c0re.net/gnuforum/viewtop...asc&highlight=

I've had mine down for over 2 years and a quick grep of my access logs reveal that there have had 343,141 hits on one site since December 2003.

There is no clear cut way to get out of the cache system, and no amount of 404 error codes will discourage certain apps from using your url.

Yeah it's great at first, but if you need to move it for any reason, or remove it for any reason, you're locked in to that traffic no matter what.

Salut Cradley, I just had to take down my gwebcache this week-end because of a DDOS from Morpheus with GnuDNA 1.0.1.7. Two years ago it was Morpheus 2.x that created the DDOS that you still see. Bad behaved clients have to banned litterally. The moral is ban Morpheus and tell everyone to use something else than that fuc*ing POS. Then, running a gwebcache will be a service I'll be please to provide again. Gnutella badly needs more gwebcaches tought, not less.

Ciao