Port forwarding works just fine. I ran Freenet behind an ISDN router (Zyxel 100IH)OK. This is set up to forward ports to a particular PC. I used a version of W2K, and did not have to do anything special. If Netmeeting work for you, then Freenet should as well.
JL -----Original Message----- From: [email protected] [mailto:freenet-dev-admin at lists.sourceforge.net]On Behalf Of Michael Wiktowy Sent: Wednesday, August 16, 2000 03:43 To: freenet-dev at lists.sourceforge.net Subject: Re: [Freenet-dev] RE: Freenet behind NAT Well, I have freenet node v.0.2 running on my shitty router box (previously a 486/33, now a 486/66 with 32 MB RAM) and it seems to be running just fine. I am not sure how it will hold up with more freenet popularity (it should be fine if freenet scales like it should) or with all the crypto coming in v.0.3. I read Oskar's response to your problem and wasn't sure if he was saying that port forwarding would work or not. I don't see why forwarding your incoming freenet port to your internal box wouldn't work (port 19114 in most cases). You can do this by intalling the port forwarding IPChains module ... assuming that your router is running linux. Other connection ports should be masqueraded properly provided they were initiated by the internal node. I may be forced to try it if v.0.3 proves to be too much for my shitty box. Mike > Date: Wed, 16 Aug 2000 10:50:43 +1200 (NZST) > From: Stephen Blackheath <stephen at blacksapphire.com> > > All, > > I'd like to be able to do exactly this too, because my firewall runs on a > shitbox that hasn't enough memory or hard disk to run a Freenet node. I > don't want put my big box directly on the Internet for semi-obvious > reasons that would be too long and boring to explain here. > > I can't see how (if you're using port forwards) the Freenet node can > definitively know what IP address and port it should advertise itself as > unless you tell it. Surely the same problem exists if you've got a > dynamic IP address - you'll want to advertise yourself as a name, not an > IP address. > > ? > > Steve > > On Tue, 15 Aug 2000, lists wrote: > > > Hi, > > > > Nobody answered this. I looked in the code and this looks harder than I > > thought - the code seems to rely on getting the node's IP address from the > > socket address of tcpConnection's all over the place and its not clear when > > this address is used for inclusion in a message (and should be spoofed with > > the router's address) and when it is used for other purposes and should be > > left alone. > > > > I would really like to fix this as I am behind an ISDN router/firewall and > > cannot run a node otherwise. I'm quite happy to fix it but I could really do > > with being pointed in the right direction. > > > > Thanks > > Degs > > > > > > > > Hi, > > > > > > Is it possible to run a node behind a NAT router with port forwarding? ie > > > does the node listen only on 11914, and can you configure it to set its IP > > > address in outgoing freenet messages to match the router's IP address? If > > > not how hard would this be to do - I may have a go. > > > > > > Thanks > > > Degs > _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
