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. 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." greg at wooledge.org | - The Red Hot Chili Peppers http://wooledge.org/~greg/ | -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020924/1f5d6fc9/attachment.pgp>
