[ENet-discuss] Enet client showing wrong connection status with server.

Faisal Khan faisal.nust at gmail.com
Tue Jan 30 10:39:42 PST 2007


Hi Kevin,

Thanks for the reply. The problem was that host_service not being called as
occassionaly as it should be. After fixing this, it worked fine.
--
Faisal

On 1/29/07, Kevin Gadd <kevin.gadd at gmail.com> wrote:
>
> Are you sure this is not a case of the client's connection being
> terminated due to client inactivity, perhaps by an ISP or router? I have
> never had this problem with enet. Have you tried it over a local area
> network?
>
> It may also be that you are calling host_service with an extremely long
> timeout and the client process itself is timing out in such a way that it
> never wakes back up, but that's just speculation.
>
> On 1/29/07, Faisal Khan <faisal.nust at gmail.com> wrote:
>
> > Hi,
> >
> > I am facing a problem while sending packets from a client to server. The
> > problem is after some time of inactivity, server disconnects the client. But
> > somehow client is not being informed of this connection break. 'peer->state'
> > always show as connected. (Value 4)
> >
> > Running packet capturing tool revealed that during the silent period ,
> > server sends some packets (probably ping requests) to client but client did
> > not respond to these probes.
> >
> > My question is, Do we always need to send some data over time to keep
> > this virtual connection alive? Or am I missing something in connection
> > setup?
> >
> > Thanks in advance!
> >
> > --
> > Faisal
> > _______________________________________________
> > ENet-discuss mailing list
> > ENet-discuss at cubik.org
> > http://lists.cubik.org/mailman/listinfo/enet-discuss
> >
> >
> >
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cubik.org/pipermail/enet-discuss/attachments/20070130/165d36e3/attachment.htm 


More information about the ENet-discuss mailing list