TechnoSF ([EMAIL PROTECTED]) wrote:

> 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.

OK, this is quite different from what you said before.  Let me make sure
I've got it straight this time.

You have a gateway with internal IP address 192.168.1.1 and external IP
address A.B.C.D.  It runs NAT or IP masquerading.

You have a LAN of multiple Windows computers with IP addresses
192.168.2.*.  Somehow these are able to talk to your gateway at
192.168.1.1 (implying that you have a netmask of /22 or less, rather
than the traditional /24).

You want to run a Freenet node (transient?  non-transient?) on each of
these Windows machines, and connect them to the larger worldwide Freenet.

If you want to run transient nodes, no special steps are required.
The transient nodes will simply make requests to other Freenet nodes
via NAT/ipmasq, and receive their response packets just like any other
normal TCP/IP connection.

If you want to run real (non-transient) nodes, then it's different.
You'll have to allocate one unique port for each Windows machine,
and forward that port from the gateway to its respective LAN client.
On the LAN client, you'll have to make Freenet listen for FNP requests on
the port that is forwarded to that client.  You will also have to make
sure that the node advertises itself with the public IP of your gateway
(A.B.C.D) and the port number which is being forwarded to that client.

This is documented at
<http://freenetproject.org/cgi-bin/twiki/view/Main/NATSAndFirewalls>,
which is linked from the Freenet documentation web page.

Did I miss anything?

-- 
Greg Wooledge                  |   "Truth belongs to everybody."
[EMAIL PROTECTED]              |    - The Red Hot Chili Peppers
http://wooledge.org/~greg/     |

Attachment: msg00665/pgp00000.pgp
Description: PGP signature

Reply via email to