I noticed that you are calling <font face="Arial" size="1"><span style="font-size: 9pt; font-family: Arial;">enet_host_service on the host...are you also calling it on the client?<br><br>Jonathan</span></font><br>-- <br>Piranha are people too.
<br><br><br><br><div><span class="gmail_quote">On 1/20/06, <b class="gmail_sendername">Lee Salzman</b> &lt;<a href="mailto:lsalzman1@cox.net">lsalzman1@cox.net</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It sounds like you're not servicing the host for those 16,000 ms. That's<br>pretty much what would cause that.<br><br>Lee<br><br>Doug Kimzey wrote:<br>&gt; After an eNet client establishes a connection to an eNet Host, the
<br>&gt; client is disconnected after approximately 30 seconds.&nbsp;&nbsp;We have traced<br>&gt; this on the host side to a call to enet_peer_reset in the<br>&gt; enet_protocol_check_timeouts(…) function:<br>&gt;<br>&gt;<br>&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if (outgoingCommand -&gt; roundTripTimeout &gt;= outgoingCommand -&gt;<br>&gt; roundTripTimeoutLimit)<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; event -&gt; type = ENET_EVENT_TYPE_DISCONNECT;<br>&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; event -&gt; peer = peer;<br>&gt;<br>&gt;<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enet_peer_reset (peer);<br>&gt;<br>&gt;<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return 1;<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;
<br>&gt; In this case the roundTripTimeout equals the roundTripTimeoutLimit of<br>&gt; 16,000 ms (or 16 seconds).<br>&gt;<br>&gt;<br>&gt;<br>&gt; I have added a call from the client application to enet_peer_ping(…)<br>&gt; that is on a timer to fire every 2 seconds – but the disconnect still
<br>&gt; occurs.&nbsp;&nbsp;The host runs a perpetual loop that calls enet_host_service(…).<br>&gt;<br>&gt;<br>&gt;<br>&gt; Would you have any suggestions or recommendations?<br>&gt;<br>&gt;<br>&gt;<br>&gt; One thing I noticed from the Cube Legends source is that they added a
<br>&gt; PING / PONG message so that whenever a PING message is received on the<br>&gt; server, it immediately does an enet_peer_send of a PONG message back to<br>&gt; the client.&nbsp;&nbsp;Are there other and better ways to handle "keep-alive" packets?
<br>&gt;<br>&gt;<br>&gt;<br>&gt; -Doug<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; Doug Kimzey<br>&gt;<br>&gt; Software Developer<br>&gt;<br>&gt; DPRA DEFENSE SYSTEMS GROUP<br>&gt;<br>&gt; 10215 Technology Drive, Suite 201
<br>&gt;<br>&gt; Knoxville, Tennessee 37932-3344<br>&gt;<br>&gt;<br>&gt;<br>&gt; Phone:&nbsp;&nbsp; 865.218.4237<br>&gt;<br>&gt; Cell:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;865.382.0307<br>&gt;<br>&gt;<br>&gt;<br>&gt; Email:&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:doug.kimzey@dpra.com">
doug.kimzey@dpra.com</a><br>&gt;<br>&gt; Home:&nbsp;&nbsp;&nbsp;&nbsp; <a href="mailto:mdkimzey@comcast.net">mdkimzey@comcast.net</a><br>&gt;<br>&gt; <a href="http://www.defensesystemsgroup.com">www.defensesystemsgroup.com</a><br>&gt;<br>&gt;
<br>&gt;<br>&gt;<br>&gt; ------------------------------------------------------------------------<br>&gt;<br>&gt; _______________________________________________<br>&gt; ENet-discuss mailing list<br>&gt; <a href="mailto:ENet-discuss@cubik.org">
ENet-discuss@cubik.org</a><br>&gt; <a href="http://lists.cubik.org/mailman/listinfo/enet-discuss">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br><br>_______________________________________________<br>ENet-discuss mailing list
<br><a href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a><br><a href="http://lists.cubik.org/mailman/listinfo/enet-discuss">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br></blockquote></div><br>