Re: [freenet-support] I'll help you with Freenet as soon as I understand it, too
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:/ 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
Re: [freenet-support] I'll help you with Freenet as soon as I understand it, too
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/ | msg00665/pgp0.pgp Description: PGP signature
Re: [freenet-support] I'll help you with Freenet as soon as I understand it, too
[Unix version] Worked a treat Greg, thanks. 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. Cheers M *** REPLY SEPARATOR *** On 5/22/2002 at 06:15 Greg Wooledge wrote: TechnoSF ([EMAIL PROTECTED]) wrote: So, Bob, Dwight har far did you get? After a couple of hours of trial and error, and a couple of searching the net, I think my node runs! Next, trying to figure out what its node key is... The Windows installer creates myOwn.ref in the Freenet directory. That's your node reference. If you didn't use the Windows installer (e.g., you're not on Windows), then use (in Unix Bourne shell): CLASSPATH=whatever/freenet.jar export CLASSPATH java freenet.node.Main --export myOwn.ref Of course, you can name it whatever you wish. -- 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) iD8DBQE862/OkAkqAYpL9t8RAp4ZAKDIzC2PS86jZ9FsZSpZXlXE9MRejACdElGw EU0tvfOzY7o8jPcSVEz1zag= =e2iW -END PGP SIGNATURE- ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] I'll help you with Freenet as soon as I understand it, too
Me too... After watching Freenet for quite a while, I've now recently been in a position to try it out. While by no means technically illiterate, I, as may others I expect, will try and use Freenet (as other interesting projects) by installing first, reading the degrees of documentation second (!RTFM). And this is by far what I find is missing in these interesting projects, a hook of documentation to catch ones interest, enable basic deployment/configuration and reel one in to participate on the real work. So, I am going to notate my findings trying out Freenet, and what I have done to get something working, though I'm not quite sure how much and if it's behaving itself. But if Dwight and Bob care to do the same, perhaps we can assimilate something that we and perhaps other would find useful for a first-time deploy and figure out what are the question we have that others, too, might have. So, Bob, Dwight har far did you get? After a couple of hours of trial and error, and a couple of searching the net, I think my node runs! Next, trying to figure out what its node key is... M *** REPLY SEPARATOR *** On 5/21/2002 at 15:09 Dwight Hines wrote: From: =?iso-8859-1?q?Bob=20Yarwood?= [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [freenet-support] Freenet For Beginners Can anyone help an absolute beginner to find a simple text on elementary Freenet - a sort of Freenet For Dummies or Idiot's Guide to Freenet, so to speak. I can't find anything in the online bookshops, so I wonder how you all became so expert in a subject for which there are no textbooks - even Freenet's own Help files mostly haven't been written yet! (Actually I wouldn't mind the job of writing some Help files, but obviously I have to understand it all myself first). This is a solid good point here. I'm in the same boat. I need to know this stuff before I go to the switch over. d ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
