On Dec 6, 2010, at 8:37 PM, Skinner Family wrote:
> Yes, there is a lot more to this networking stuff than I ever imagined. I
> made the above changes per the comments below and 12 hours later, no
> improvement :-(
> At this point I need to determine if the problem is with Freenet, my router
> or firewall. I can turn off the firewalls and at least eliminate that
> possibility. Thanks.
>
> S.
>
> -----Original Message-----
> From: support-boun...@freenetproject.org
>> Dear Support:
>>
>> I installed Freenet 24 hours ago and continue to get the Route Not Found
>> error.
>> ...
>> (2) I know nothing about forwarding ports, but I set 8888 as the start
>> port and 46185 as the end port - traffic is allowed both ways.
>
> This might be the problem:
>
> - on port 8888, the internal http server is running on your PC
> ("localhost" ip adress 127.0.0.1); this port need/must not be forwarded
> on the router
>
> Okay... have fixed.
>
> - if 46185 is the port that freenet says it's running opennet on, THIS
> (and only this) port has to be forwarded from the router to the PC
> (check that you're using the correct local IP, like 192.168.0.1 or
> something .. you find it e.g. in the status report of your ethernet
> network connection or by typing "ipconfig" in the command line window.
>
> The port forwarding config on the router for HTTP requires a start port, and
> end port, and the local IP. I've used port 80 and 46185 and have set the
> local ip.
This is definitely NOT what you want to do. From what you said, I know that
your port forwarding configuration will not work. You want both the in-port and
the out-port to be 46185. If you have the in-port set to 80 and the out-port as
46185, that means that incoming connections will only be accepted on port 80,
and before they get to your computer they will be rerouted to port 46185. So no
Freenet nodes will be able to connect to you through 46185 until you fix the
configuration.
As Skinner Family wrote, this port is the only one that you need forwarded, but
it has to be done correctly.
> - do not use trigger ports: port triggering implies that the ports are
> closed after a time again - you want the port constantly open for
> freenet (you're running a server, after all!)
>
> Yeah... good point. I've removed all port triggering.
>
> All in all - read up the wiki pages and your router manual thoroughly
> (again).
> As at part of the wiki isn't an easy read, I would give you a link to
> easy-to-understand networking basics, yet, I don't have one at hand
> atm., sorry.
>
> A.
_______________________________________________
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
