Ang. RE: [lwip-users] Strange behavior with sockets.

[hans . ronnback]

Im using the latest stable LwIP (1.2.0).

And I have checked it the default tcp_recv_null()
is called (causing the connection to close), but its not.
And I have added a printf() before i
call close() on the socket. Still no result.. Nothing is printed, and the
SYN/SYN,ACK handshake completes but is immediately followed by a FIN,ACK
packet.

//Hans

address@hidden
skrev 2007-06-04 10:32:59 :

> > I'm having a rather strange behavior when using sockets. 
> > One thread that does all kind of intializations is used to setup
a
> listening socket. The thread never reference this socket after the
> initialization is complete. 
> > Another thread is then started to handle incomming connections/traffic
> on the listening socket. However, upon calling lwip_accept() something
> odd is happening. 
> > LWIP first completes the SYN/SYN,ACK sequence, but then follow
up with
> a FIN,ACK, causing the connection to close. 
> 
> Which version are you using? If you're using a recent CVS HEAD version,
> make sure you check it out again since there was a little bug with
a
> recent change to initialization of tcp pcbs which has set some
> connections in the closed state so that they wouldn't accept data.
From
> what you're saying, that _could_ be the reason...
> 
> 
> Simon
> 
> 
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users