On Tue, Sep 24, 2002 at 06:55:41AM -0400, Greg Wooledge wrote: > fproxy.port=8888 > fproxy.bindAddress=* > fproxy.allowedHosts=127.0.0.1,192.168.2.1,192.168.2.2,192.168.2.4,192.168.2.20 > > $ netstat -ant | grep 88 | grep LISTEN > tcp 0 0 127.0.0.1:8888 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:8889 0.0.0.0:* LISTEN > > Notice that fproxy's port (8888) is bound only to 127.0.0.1, not to > 0.0.0.0 like nodestatusservlet is. This means that my ability to > browser my node across the LAN just vanished, until I jury-rig something. RTFL. http://hawk.freenetproject.org/pipermail/cvs/2002-September/000654.html (it was announced on devl too). > > Also, nodeinfo (8890) seems to have vanished entirely. Viewing > 127.0.0.1:8888 with lynx seems to indicate that what used to run on > port 8890 is now running on port 8888 -- fine -- but since I can't > get to port 8888 remotely any more, it's not very useful. > > -- > Greg Wooledge | "Truth belongs to everybody." > [EMAIL PROTECTED] | - The Red Hot Chili Peppers > http://wooledge.org/~greg/ |
-- Matthew Toseland [EMAIL PROTECTED] [EMAIL PROTECTED] Freenet/Coldstore open source hacker. Employed full time by Freenet Project Inc. from 11/9/02 to 11/11/02.
msg04011/pgp00000.pgp
Description: PGP signature
