> I'll say it again: Not supporting firewalls is a massive fault in
> Freenet.
No P2P system actually works through firewalls although some pretend in
various ways. Freenet pretends to work behind a firewall in that you can
run it behind many firewalls, although you can't add value to the network.
You can, however, download whatever you'd like just fine.
It's not really useful to complain about firewalls unless you say what
particular firewall setup you have. Freenet works behind some firewall
settings.
Freenet does not work behind a firewall that won't let you make outgoing
connections to arbitrary ports. If you've got a solution to this problem
then please let me know. No one else has solved it but there are various
workarounds. The various workarounds work for some people and not for
others, depending on your situation.
> of them that are no longer required. A version of Freenet that'll work
> through an HTTP proxy is badly needed.
If you tell me more specifically what your firewall configuration is, I'll
tell you how to work around it. If you can listen on port 80 and open
arbitrary ports then you don't need a special version of Freenet. If you
can listen on port 80 and only open a connection to port 80 then you need
to set up a proxy on another machine. If you can listen on port 80 and
open a connection on port 80 but all non-HTTP traffic is dropped then you
need an HTTP tunneling proxy. If you can only listen on port 80 and not
make connections at all, then you need a proxy that will periodically try
to connect to you.
There is no general magic solution for making Freenet or any P2P system
work behind a firewall. It's not that we're lazy or no one has complained
about this before.
_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/support
