On tir, 2003-03-18 at 20:36, Lean Fuglsang wrote: > On tir, 2003-03-18 at 20:02, [EMAIL PROTECTED] wrote: > > Quoting Lean Fuglsang <[EMAIL PROTECTED]>: > > > > > First I would like to know how to search the archives... It is pretty > > > cumbersome if I ask questions which have already been answered. > > > > You know... I've grappled with the same question. I haven't been able to > > finagle Google into searching the lists. The best I've found is to load up a > > select archive and then use your browser to search for a specific word. Problem > > with this, of course, is that you're only searching the "subject" and "from" > > headers. It'd be nice if the archives were a) searchable, or at least b) able > > to display all messages (including body) in a flat format. > > > > > I have startet freenet on a server on my localnet. Is it possible for > > > other computers on the localnet to use freenet on the server in a good > > > way. > > > Right now all links is set for 127.0.0.1:8888. Is this hardcoded on the > > > websites? > > > Is it possible for other freenet clients to use the server in a good > > > way? > > > Or is the only solution to manually redirect ports on the clients? > > > > It should be fine. From another computer on your network point your browser to > > the node. (192.168.1.1:8888, or whatever it is). Normally all links on Freenet > > are enoded as "/[EMAIL PROTECTED]", so the browser will automatically tack on the > > preceding 192.168.1.1:8888, like you'd want. > > > > Note, however, that you're going to have to make a few changes to your node. > > You'll have to tell the node to allow incoming connections from > > other-than-127.0.0.1. How to do that can be found here: > > http://freenetproject.org/tiki-index.php?page=FAQ#fproxy-lan > > > > In brief, add this to your freenet.conf (or freenet.ini, for Windows): > > > > mainport.bindAddress=* > > mainport.allowedHosts=127.0.0.1,192.168.1.0/24 > > > > Let me know if you get it to work. > Well, right now I have serious trouble to just to get the server > started. > But when it sporadically works, all adresses is 127.0.0.1:8888. > A bug? > Well, my other troubles is that the server is an AMD 166, well below the > lowest spec... But I really can't imagine this should be a problem. > It is running linux 2.4.20, but got a lot of zoombie processes. So maybe > a restart will help. > Anyway, i can't connect to freenet at the moment, even though it looks > like java is running. I have tried different ports, but it still won't > work. > When I do an nmap on the ports it just show closed. On my desktop, it > shows the ports fine (as sun-answer book). Well, I will keep fiddle with > it. > Btw, I am running java build Blackdown-1.4.1-01. Kaffe worked before the > 5.1 releases, but now it is really unstable and buggy. > It is probably a java problem, that doesn't initiate the ports probably
OK, i just tried the other way around. And shared freenet from my desktop, and joined from my server. This works wonderfully, the links shows as the right ip and port. -- Lean Fuglsang <[EMAIL PROTECTED]> _______________________________________________ Tech mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/tech
