[ENet-discuss] WSAENETRESET in enet_socket_receive

[Lee Salzman]

UDP is connectionless. It's all one socket. A socket error for one peer is a socket error for all peers.

On 10/04/2012 04:25 PM, Soren Dreijer wrote:
>
> > Isn't that the same thing as the connection being dropped?
>
> This isn’t the same as WSAECONNRESET. I also don’t believe a UDP connection can “be dropped”.
>
> > Hell, I can't even find any consistent documentation on what this error means, so I'm not even sure what to do about it....
>
> I’ll fire up Wireshark on his computer when I get a chance and look at the actual packets. Maybe the TTL really is messed up.
>
> Also, out of curiosity, should an error like this really cause enet_host_service() to return an error? I mean, shouldn’t enet just consider the connection to that one peer to be dead and send an enet disconnected event for it and then keep working with the other peers?
>
> *From:*enet-discuss-bounces at cubik.org [mailto:enet-discuss-bounces at cubik.org] *On Behalf Of *Stefan Lundmark
> *Sent:* Thursday, October 04, 2012 5:15 AM
> *To:* Discussion of the ENet library
> *Subject:* Re: [ENet-discuss] WSAENETRESET in enet_socket_receive
>
> Isn't that the same thing as the connection being dropped?
>
> And isn't it only sent when you have keep-alives enabled?
>
> On 2012-10-04 11:58, Lee Salzman wrote:
>
> Hell, I can't even find any consistent documentation on what this error means, so I'm not even sure what to do about it....
>
> On Wed, Oct 3, 2012 at 6:26 PM, Soren Dreijer <dreijer at echobit.com <mailto:dreijer at echobit.com>> wrote:
>
> Hi all,
>
> I’m dealing with a user who is having problems with enet. After digging in a bit, it turns out enet_socket_receive() returns -1 because WSARecvFrom() returns WSAENETRESET. Googling around a bit, the error suggests the TTL of the UDP packet was exceeded, but I wanted to see if anybody else has experienced something similar and if they found the cause (or even a fix).
>
> I’m thinking this guy either has a bad protocol filter installed in Windows or his router/ISP is messing something up on the packets.
>
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org <mailto:ENet-discuss at cubik.org>
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>
>
>
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org  <mailto: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