Yep, I was trying to avoid using the gateway (say 192.168.1.1) as a lan-wide (HTTP) fproxy and allow the windows clients (lets say the 192.168.2.0 network) to run freenet themselves in a P2P manner and have the gateway 'leek' the 192.168.2.0 traffic. In many respects to mirror an IP network where unknown IP/addresses go through the gateway for routing.
M *********** REPLY SEPARATOR *********** On 5/22/2002 at 18:34 Greg Wooledge wrote: >TechnoSF ([EMAIL PROTECTED]) wrote: > >> I'm actually on Linux and Windows - Linux gateway, windows clients. >> I'm trying to configure a topology where Freenet sits on the gateway >> (with its single non-forwarding port, hopefuly bypassing the need for >> an upgraded to IPTABLES that I do not have the time/skill to do yet) >> and acts as a proxy, if you will, for freenet on the Windows machines. > >No problem. Just put this in the Freenet node's "freenet.conf" file: > >fproxy.allowedHosts=127.0.0.1,192.168.1.1,192.168.1.2,192.168.1.3 > >where 192.168.1.1 is the LAN IP of the gateway box, and 192.168.1.2 (etc.) >are the LAN clients. > >Unfortunately, I don't believe you can use a wildcard or CIDR >specification for a range of IPs. You have to list each one. > >Then, the clients can just go to http://192.168.1.1:8888/ to access the >node on the gateway. > >-- >Greg Wooledge | "Truth belongs to everybody." >[EMAIL PROTECTED] | - The Red Hot Chili Peppers >http://wooledge.org/~greg/ | > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.0.7 (GNU/Linux) > >iD8DBQE87B0BkAkqAYpL9t8RAnlBAJ9z1SLhtotrs/brpgV0PQsDteY2qACdGMp2 >/OEy8ZII7+6EYU5yQS4B3UY= >=7gco >-----END PGP SIGNATURE----- _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
