One of the places where I would like to use freenet is behind NAT. I know all about port mapping, but this simply isn't available in this situation.
What is the hope of running Freenet?
I know virtually every other protocol has implemented support for NAT as part of (or before) becoming mainstream... if this doesn't exist in freenet as of now, it might be something important if freenet were to ever become widely used.
No, they haven't. Please try running a web server behind a NAT that you can't forward ports on. Or ssh. Or any number of other client/server protocols.
I was thinking of P2P file transfer protocols. Bittorrent, gnutella, fasttrack, etc. Uploading doesn't always work really great, but downloading is quite decent. Bittorrent seems to have zero problems saturating upstream bandwidth on many torrents that are 100% behind NAT. I classified (mentally) freenet as a P2P, but it's more like a server-to-server for best performance.
To answer your question, freenet stable build 5077, or recent freenet
unstable builds (60077 is current), will work a lot better in such a
situation than previous builds. However, the node will still not be a
proper member of the network because it cannot receive incoming
connections, and thus will not perform as well as it could. I don't
think your anonymity is seriously jeopardized by being behind a NAT, but
I'm not absolutely sure on that one.
Implementing a means for sending a message through the network to tell a
NATted node to open a connection to another node is something that we
might implement, but probably not before 0.6.
I've just downloaded the latest stable build of freenet and we'll see how it works. You'll be hearing from me again.
-Galen
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
