Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-11 Thread Sergio R. Caprile
OK, so you seem to need help with TCP, not with lwIP (yet). I'd like to see a wireshark capture; not a screenshot, the capture file. And please enable logging on lwIP and capture that too. You can post capture files to the list. Regards On 08/08/2014 02:46 p.m., Sergio R. Caprile wrote: Read the

Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-09 Thread Paul Webber
-timer@nongnu.org on behalf of S G goldsi...@gmx.de Sent: Friday, August 08, 2014 4:30 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] LWIP RAW tcp_close, tcp_connect My guess would be that you have manual listen backlog enabled but don't tell the stack to decrement the listen

Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-09 Thread Simon Goldschmidt
Paul Webber wrote: One more question. How does the open listener on my product effect the server when my product tries to open an outbound connection to the server? It doesn't. I thought you had the server running on lwIP. Simon ___ lwip-users

Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-09 Thread Paul Webber
To: Mailing list for lwIP users Subject: Re: [lwip-users] LWIP RAW tcp_close, tcp_connect Paul Webber wrote: One more question. How does the open listener on my product effect the server when my product tries to open an outbound connection to the server? It doesn't. I thought you had the server running

Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-08 Thread Sergio R. Caprile
Read the wiki, and if it is not clear enough, I will change it http://lwip.wikia.com/wiki/Raw/TCP So far, the last user that asked (almost) exactly the same as you did not complain, so it should be OK. ___ lwip-users mailing list lwip-users@nongnu.org

Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-08 Thread Paul Webber
@nongnu.org] On Behalf Of Sergio R. Caprile Sent: Friday, August 08, 2014 1:46 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] LWIP RAW tcp_close, tcp_connect Read the wiki, and if it is not clear enough, I will change it http://lwip.wikia.com/wiki/Raw/TCP So far, the last user that asked

Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-08 Thread S G
My guess would be that you have manual listen backlog enabled but don't tell the stack to decrement the listen backlog after accepting a connection... Simon ___ lwip-users mailing list lwip-users@nongnu.org

Re: [lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-08 Thread Paul Webber
-bounces+pwebber=heat-timer@nongnu.org lwip-users-bounces+pwebber=heat-timer@nongnu.org on behalf of S G goldsi...@gmx.de Sent: Friday, August 08, 2014 4:30 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] LWIP RAW tcp_close, tcp_connect My guess would be that you have manual

[lwip-users] LWIP RAW tcp_close, tcp_connect

2014-08-07 Thread The Webbers
I am using LWIP 1.4.1 two questions: I have made a connection to a server, the transaction looks correct (watching it with Wireshark). The connection opens I send data,the server acks with data, the server data is acked, the server sends fin_ack, I use tcp_close, NULL all callbacks, my fin_ack is