On Mon, 2003-09-22 at 10:24, Bogdan Butnaru wrote: > I write this message because I noticed there is a clash between the > Amphetadesk (sourceforge.net/projects/amphetadesk/) URIs and those of > Freenet (www.freenetproject.org). Both seem to use URIs beginning with > 127.0.0.1:8888.
Quick history review. In older times, FProxy used to suck (much worse). I wrote fcpproxy, an HTTP interface written in C with an FCP back end, and set the thing to listen on port 8888 by default. This just felt like a nice easy-to-remember port number, and I blithely chose it without doing much of a search on other software that also ran http on port 8888. FCPProxy ran much faster than FProxy, but had very little filtering. Also, it wasn't 100$ stable. Some time later, the in-node FProxy had a massive rebirth, to the point of delivering very acceptable performance, tons of extra features, while retaining its diligent filtering of potentially compromising content (eg javascript, non-freenet links etc). It was set to listen on port 8888 by default, to encourage users away from fcpproxy and back to FProxy. Naturally, people using Freenet 0.4 and 0.5 switched back to FProxy. More and more, we are going to see issues of port clashes with other software. In this scenario, you have two choices: 1) Change 'Amphetadesk' to listen on a port other than 8888 2) Change Freenet's FProxy to listen on a port other than 8888. If you want to do the latter, then edit your freenet.conf (or freenet.ini) file, look for a line which reads: mainport.port=8888 Change that to the number of a spare port and restart your node. Note, however, that there might be some URLs outside of Freenet which are hard-coded to port 8888. Eg, mainstream web pages which talk about something on Freenet, and provide an in-freenet link, without mentioning the need to edit the port. In such cases, if something other than FProxy is listening on 8888, you'll get 'interesting' results. If so, you'll have to copy the link, paste to your browser address bar, and change the 8888 to wherever you've changed FProxy. Don't regard this as a design fault. While many standard services have been settled on specific ports (eg SMTP=25, HTTP=80, HTTPS=443 etc), there are a great many software packages which aren't standardised, and cope by providing easy ways to change the listening port. Cheers David _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
