Hi Simon, tcp_nagle_disable() helped. Now there is long delay only when there are also incoming packets while transmitting. This happens only when lwip_netconn_do_writemore() ends with error. That me
Hi Marek There is an automatic back-off mechanism designed to stop nodes flooding the network with small TCP messages called Nagle algorithm. Check if you are being blocked by that. You can turn it o
I spent days debugging the emac driver which is an nxp emac driver but with no success. However diabling the nagle alogrithm improved the performance bt can still see the random delays and retransmis
Am 31. Juli 2018 11:13:00 MESZ schrieb Mike Danby <address@hidden>: Yes. 20 seconds is much too long. I'd expect to see some 100ms Delay. Could it be that your timers aren't running? No. That doesn't
I am using lwip-2.0.2 (socket api) and have an issue which has started after attempting to upgrade from lwip-1.4.1 to lwip-2.0.2. In our server application a socket is setup and receive commands from
Hi Itzik, I have never worked with Android so I cannot help in that area. My options are defined for a small micro with limited resources so I hope I am not confusing you. BR, Noam. From
Hi Itzik, I have never worked with Android so I cannot help in that area. My options are defined for a small micro with limited resources so I hope I am not confusing you. BR, Noam. From
Hi Itzik, I have never worked with Android so I cannot help in that area. My options are defined for a small micro with limited resources so I hope I am not confusing you. BR, Noam. From: lwip-users
Hi Itzik, Ops I missed that J I am attaching my own lwpopts.h I am using FreeRTOS as OS on STMF32xx micro’s. I am running several modules (SDDP, TCP terminal, HTTP, SSH etc… ) with t
Hi Itzik, Ops I missed that J I am attaching my own lwpopts.h I am using FreeRTOS as OS on STMF32xx micro’s. I am running several modules (SDDP, TCP terminal, HTTP, SSH etc… ) with the above sett
Hi Itzik, From participating the group here I have heard many complaining that the driver level is the cause to problems like you are facing. From my own experience I have noticed problems when usin
Hi Itzik, From participating the group here I have heard many complaining that the driver level is the cause to problems like you are facing. From my own experience I have noticed problems when using
Hi Itzik, I see that you have defined: TCP_WND=(100 * TCP_MSS) TCP_SND_BUF=TCP_WND MEMP_NUM_TCP_SEG=TCP_SND_ QUEUELEN If TCP_MSS is defined 536 (default) that means that your TCP_WND is 53,600 bytes
Hi Itzik, I see that you have defined: TCP_WND=(100 * TCP_MSS) TCP_SND_BUF=TCP_WND MEMP_NUM_TCP_SEG=TCP_SND_QUEUELEN If TCP_MSS is defined 536 (default) that means that your TCP_WND is 53,600 bytes ?
Hi All, Firstly, a bit of background: I'm currently evaluating lwip stack in order to determine whether it can fit my needs. The end-goal, is integrating Socket API --> TCP/IP --> PPPoS stack on b
Hi, First of all read the lwip readme and every document you can find. Check the echo server example and see how it is written. 1. If both servers are the same write functions and simply pass paramet
Hello, I hope somebody can help me. I am using lwip 2.0.2 together with freertos 7.0.4. My problem: In my application I immediately have to send many small frames. When I try to send a single frame i
Hi Marco, Added to that, try disabling VJ compression (VJ_SUPPORT = 0), VJ support in 1.4.1 is not working properly. Yup. At least I'm not going for a deep analysis of the issue because I'm confident
Right. Try to put a breakpoint in pppifOutput with a condition that you get there when the 2nd packet is sent (revert your nagle changes before). Then have a look into the pcb to see what segments ar
Hi Simon, I'm not sure what's the right way to do that as there is no option in opt.h, I've commented that out for a test (in tcp_out.c): /* if((tcp_do_output_nagle(pcb) == 0) && ((pcb->flags & (TF_N