I've been investigating a system with two Enet hosts under bad network conditions, and noticed a spurious disconnect at the server.
I've used Enet v.1.3.13 and for simulating bad network I've used netem with configuration "delay 100ms 100ms 5% loss random 45% corrupt 35%" which means a delay of all packets of 100ms a random loss of 45% for all packets and 35% of all packets are corrupt. At first, the network is good and both client and server connects to each other, Enet reports ENET_EVENT_TYPE_CONNECT. Then I apply the bad network and both the client and the server disconnects, Enet reports ENET_EVENT_TYPE_DISCONNECT on both client and server. When the bad network conditions are restored, at first, everything seems to work fine. Enet reports ENET_EVENT_TYPE_CONNECT for both client and server. But then, after some second, I will get a spurios ENET_EVENT_TYPE_DISCONNECT on the server side only. The client still thinks everything is up and running. And I'm stuck in a state that I can only get out from by restarting one of the applications(either the server or the client doesn't matter) This happens almost everytime. I have also noted that if I apply really bad network, for example a random loss of 95% of all packets, and the restore. Then, I havn't seen this strange disconnect. Best regards, Kristin Nielsen Software Developer LHD Applications Rocktec Division Atlas Copco Rock Drills AB Address: Klerkgatan 21 701 91 Örebro Sweden Phone: +46 019 768 25 85 E-mail: [email protected] Visit us at: Follow us at: http://www.atlascopco.com Facebook / Twitter / LinkedIn / YouTube Committed to sustainable productivity
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
