Re: [lwip-users] Connection abort due to max SYN retries reached

2017-03-23 Thread goldsimon
After looking at the changelog, I also guess it must be your test. What's changed there is that slowtmr checked for == max retries and I've changed it to >=. The old code had the assumption that nrtx was increased in the timer only, but in SYN_SENT, it is increased asynchronously as well.

Re: [lwip-users] Connection abort due to max SYN retries reached

2017-03-23 Thread D.C. van Moolenbroek
Hi, On 3/22/2017 18:11, Axel Lin wrote: I recently found it's easy to get connection abort when I test connecting web server. (test by just repeating send http request) It's easy to get below debug message: tcp_slowtmr: max SYN retries reached Just a guess: could it be that your test is

Re: [lwip-users] Connection abort due to max SYN retries reached

2017-03-22 Thread goldsi...@gmx.de
Axel Lin wrote: It's easy to get below debug message: tcp_slowtmr: max SYN retries reached I tried increase TCP_SYNMAXRTX but it seems does not help. Hmm, we have changed something around there in 2.0.2, could you check how 2.0.1 behaves? Simon

[lwip-users] Connection abort due to max SYN retries reached

2017-03-22 Thread Axel Lin
Hi, I'm using netconn API and running with FreeRTOS. When test my application with current lwip git tree. I recently found it's easy to get connection abort when I test connecting web server. (test by just repeating send http request) It's easy to get below debug message: tcp_slowtmr: max SYN