Just add: nodeinfo.bindAddress=*
to the config file. On Mon, Sep 09, 2002 at 12:51:05PM +0200, Philipp L wrote: > several people noticed that they are no longer able to access their > node remotely. SOMETHING WITH THE NEW GATEWAY I S WRONG (or has > changed!) > I'm posting this to the devl list because no one seems to care what's > going on in the support list anyway. > As far as I know, the problem looks like this: a lot of people had this > "fproxybindaddress=*" in their conf file to acess their node from other > pcs in their LAN. > I think this opened port 8888 (usually) for everyone. But when I try to > connect to the "new" gateway, I ACTUALLY GET REDIRECTED TO PORT 8890!!! > And fproxybindaddress doesn't do anything with port 8890, as far as I > know! the connection gets rejected, and that's it. I can acess the node > from localhost of course. > > PLEASE FIX THIS! Or post the conf file of hawk.freenetproject.org, so > we can see how you're doing it... > > thanks > > Phil > > > _______________________________________________ > devl mailing list > devl at freenetproject.org > http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl -- Ian Clarke ian at freenetproject.org Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ Personal Homepage http://locut.us/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020909/80de4cda/attachment.pgp>
