Hi
I am using neorouter free on a few PC with windows XP.
I have upgraded 2 of them to 1.7.0 to try to resolve problems with unstable connection. I am supervising the connections with big brother with ping every 5 min. The connectins can be stable for a day of more. But from time to time the connection starts to go up and down a few times per hour for several hours.

A snapshot of the NR service log:
2012-05-05 17:29:42,257|02288|01400|W|Timeout::Fail to create p2p channel: Key Exchange.
2012-05-05 17:29:42,257|02288|01400|W|CPeerObj::OnError -2139029490 on 0x700000a
2012-05-05 17:44:41,206|02288|04664|W|CPeerObj::OnError -2147014842 on 0x500000a
2012-05-05 17:44:43,660|02288|04664|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 17:51:55,743|02288|03764|W|CPeerObj::OnError -2139029491 on 0x500000a
2012-05-05 17:55:12,386|02288|04664|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 17:59:07,061|02288|03764|W|CPeerObj::OnError -2139029491 on 0x500000a
2012-05-05 18:09:41,554|02288|04664|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 18:14:41,526|02288|04296|W|CPeerObj::OnError -2147014842 on 0x500000a
2012-05-05 18:20:02,202|02288|04296|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 18:25:12,222|02288|04296|W|CPeerObj::OnError -2147014842 on 0x500000a
2012-05-05 18:34:41,745|02288|04296|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 18:39:41,842|02288|04296|W|CPeerObj::OnError -2147014842 on 0x500000a
2012-05-05 18:45:02,034|02288|04296|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 18:49:42,475|02288|03776|W|Timeout::Fail to create p2p channel: Key Exchange.
2012-05-05 18:49:42,475|02288|03776|W|CPeerObj::OnError -2139029490 on 0x500000a
2012-05-05 18:59:41,826|02288|04296|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 19:04:42,158|02288|04296|W|CPeerObj::OnError -2147014842 on 0x500000a
2012-05-05 19:10:01,647|02288|04296|W|CPeerObj::OnError -2147014842 on 0x700000a
2012-05-05 19:15:12,276|02288|04296|W|CPeerObj::OnError -2147014842 on 0x500000a

10.0.0.5 has neorouter 1.7 and 10.0.0.7 has neorouter 1.7.
The log is from 10.0.0.1 that has neorouter 1.7.

What is the reason behind this behaivour?
I cannot find any list of the error codes that can help the understanding of the log.
Regards Jan

Hi Jrox,

Thanks for your log. From your log information, I can see your network may be unstable or some other reasons cause NeoRouter clients re-connect each other.

Here is the meaning of the error code:
-2139029491 - 8081000d P2P peer shutdown
-2139029490 - 8081000e P2P peer tunnel timeout
-2147014842 - 80072746 Winsock error, "Connection reset by peer", or "An existing connection was forcibly closed by the remote host"

NR clients always keep a connection to the server and it try to create P2P connection to the peer when an application ( like ping or other apps) connects to the peer. If it fails to create the P2P connection, the peers will use the relay mode to communicate each other. There are various reasons causing P2P fail and the main reason is the network issue. If the peers cannot handshake properly, you will see the peer-shutdown or timeout error code, even the connection is broken.

So in your case, I'm guessing:
1.For some reason, your network would be very very busy or broken. This may cause NR client think it lost connection to the server and start the re-connection process. Note: NR client has the heart-beat mechanism to detect the healthy status to the server.

2.When NR client re-connects to the server, it got a chance to retry P2P connection, but failed, if the network is still not stable. That's what you saw the P2P errors.

Beside physical network issue, such P2P software as BitTorrent, may abuses the network bandwidth and cause NR clients having unstable bandwidth.

If you can put some traffic control on your network, it would be helpful.

Thanks,
KevinZ - NeoRouter team

Hi
Thanks for the info. I will look into my network and try to understand if there can be any reasons that bandwidths are limited.

It seems from your answer that limited bandwidths can cause problems for neorouter.
Is there any minimum bandwidth to make neorouter connections stable?
Also how long is the time-out and can it make sense to try to optimize them?
Regards Jan

Hi Jrox,

There is no minimum bandwidth or limited bandwidths to the NeoRouter clients, but if you don't have a traffic control, it may cause NeoRouter clients have no chance to send the heart-beat packets periodically, then cause it timeout and close the connection.

The heart-beat between NR client and server is 3 times X 15 seconds interval = 45 seconds. If each peer cannot receive the echo from the other in 45 seconds, it may actively close the connection and reconnect.

You can turn it off by setting TcpHeartBeatMode=0. For detailed information, please refer to
http://www.neorouter.com/wiki/index.php ... ationFiles


Thanks,
KevinZ - NeoRouter team