Re: [freenet-support] Freenet not maintaining connections in VM
Original Message Subject: Re: [freenet-support] Freenet not maintaining connections in VM Date: 2014-03-19 07:17 From: dannyf...@openmailbox.org To: Dennis New denn...@dennisn.dyndns.org On 2014-03-18 13:13, Dennis New wrote: On Tue, 18 Mar 2014 09:52:45 +, dannyf...@openmailbox.org wrote: Hi, This is my first post here, so please go easy on anything I miss... I am running freenet on a VM, using VirtualBox. I have obviously forwarded the open/darknet ports. It takes a long time to establish any connections and those that are established are quickly dropped. After several hours, I am left with: Freenet is connecting to the network - this may take a few minutes. Performance will continue to improve during the next few hours. This will happen each time you shut down Freenet for more than a few minutes, so try to leave it running 24 hours a day if possible. We have recently sent 1 announcements, 1 of which are still running, and added 37 nodes (378 nodes have rejected us). We are currently connected to 1 seednodes and trying to connect to another 6. By contrast I shutdown the port forwarding and tested freenet on the physical host. Connections are established very quickly and are maintained well. Any suggestions? Check your wrapper.log in case it mentions a reason for the 378 rejections. And if not, enable logging in the settings, which will be dumped into timestamped files in the log/ subdirectory. Thanks Dennis, I am getting a lot of: Announcement to seednode:port not accepted (version 1459) And a few: Announcement to seednode:port completed (0 added, 3 not wanted, 15 shallow) It looks like build 1459 is not accepting connections from my node. However, I am running 1459. ___ 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
[freenet-support] Freenet not maintaining connections in VM
Hi, This is my first post here, so please go easy on anything I miss... I am running freenet on a VM, using VirtualBox. I have obviously forwarded the open/darknet ports. It takes a long time to establish any connections and those that are established are quickly dropped. After several hours, I am left with: Freenet is connecting to the network - this may take a few minutes. Performance will continue to improve during the next few hours. This will happen each time you shut down Freenet for more than a few minutes, so try to leave it running 24 hours a day if possible. We have recently sent 1 announcements, 1 of which are still running, and added 37 nodes (378 nodes have rejected us). We are currently connected to 1 seednodes and trying to connect to another 6. By contrast I shutdown the port forwarding and tested freenet on the physical host. Connections are established very quickly and are maintained well. Any suggestions? Many thanks ___ 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
Re: [freenet-support] Freenet not maintaining connections in VM
On Tue, 18 Mar 2014 09:52:45 +, dannyf...@openmailbox.org wrote: Hi, This is my first post here, so please go easy on anything I miss... I am running freenet on a VM, using VirtualBox. I have obviously forwarded the open/darknet ports. It takes a long time to establish any connections and those that are established are quickly dropped. After several hours, I am left with: Freenet is connecting to the network - this may take a few minutes. Performance will continue to improve during the next few hours. This will happen each time you shut down Freenet for more than a few minutes, so try to leave it running 24 hours a day if possible. We have recently sent 1 announcements, 1 of which are still running, and added 37 nodes (378 nodes have rejected us). We are currently connected to 1 seednodes and trying to connect to another 6. By contrast I shutdown the port forwarding and tested freenet on the physical host. Connections are established very quickly and are maintained well. Any suggestions? Check your wrapper.log in case it mentions a reason for the 378 rejections. And if not, enable logging in the settings, which will be dumped into timestamped files in the log/ subdirectory. ___ 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
