Re: [lwip-users] lwIP 1.4.1 stable tcp connection stall

goldsi...@gmx.de writes: Maybe. As a starter, you should disable everything you can in tcp_output (TCP_OUTPUT_DEBUG, TCP_CWND_DEBUG). Then once the error happens, try dumping the lwip_stats plus the whole tcp_pcb that doesn't send any more. There's no function to do

Re: [lwip-users] IPv6 multicast support by Socket API?

Andrey, can you try my patch and tell me if it works? If not, please try to debug it, I was not able to test it at home. TODO: Correctly unregister at socket close, try to fix code duplication with IGMP. Ciao Dirk diff --git a/src/api/sockets.c b/src/api/sockets.c index a50faf5..21f6481 100644

Re: [lwip-users] lwIP 1.4.1 stable tcp connection stall

Bill Auerbach wrote: I can debug some, yes, but I’m no expert on this part of lwIP or TCP. So I need help in what information is best to gather. I can pause when the sending stops and get to these variables. Would output from LWIP_DEBUG_ONs (whichever ones are pertinent) show you anything

Re: [lwip-users] lwIP 1.4.1 stable tcp connection stall

Hi Simon, I see a zero window persist timer bugfix entry in 1.4.1. I can ping-pong 2.0.2 and 1.4.1 and make the error come and go. At first on the NIOS II but being slower and harder to debug I just got the PowerPC converted to 2.0.2 and it’s working there too (as expected). The PowerPC

Re: [lwip-users] time out on last ack

At one point I set up an increment of 10 seconds per check, so 10, 20 , 30 ... and it would never reconnect even after a minute.  For my purposes the "REUSE" was important - same IP address, same port.  And re-establishing connection quickly (within 10 seconds) was also important.  It did not

Re: [lwip-users] time out on last ack

Mike Rosing wrote: > After searching a while I see that the LwIP is waiting for LAST_ACK, but the > server never sends it. I would have expected lwip to time out this PCB eventually (although that can need quite some time). How long did you wait?

Re: [lwip-users] lwIP 1.4.1 stable tcp connection stall

Hey Bill, Great to hear 2.0.2 fixes this. I'm a bit lost thinking about a bug fix. We had some since then I guess, and I would have to dig through the log myself. However, the most obvious would be a zero window where the persist timer doesn't start or somehow doesn't work correctly. Are you

[lwip-users] lwIP 1.4.1 stable tcp connection stall

Hello group, First, thanks to everyone for the continued development and support of lwIP - it been great to see it so active the past few years. This purpose of this message is to notify lwIP 1.4.1 stable users of a problem, and to see if anyone (i.e. developers) knows the bug report that

[lwip-users] Using BOOTP with lwIP

Hello All, I am trying to get BOOTP working with lwIP 1.4.1 stack. I am able to configure the device in STATIC IP address mode and send the BOOTP packet and have the BOOTP server send the BOOTP response. However the call back function for udp does not get invoked. After debugging the same, the

[lwip-users] time out on last ack

A couple weeks ago I posted this question:"I have a situation where the LwIP is a client and I have compiled with SO_REUSE = 1, but the reconnect fails with error -8 (in use).  After searching a while I see that the LwIP is waiting for LAST_ACK, but the server never sends it.  What can I do to

[lwip-users] IPv6 multicast support by Socket API?

Hello lwIP developers, I am using latest lwIP 2.0.2. My application have to use lwIP Socket user API and FreeRTOS. And It have to join IPv4 and IPv6 multicast groups. The IPv4 Multicast is supported very well via the IP_ADD_MEMBERSHIP / IP_DROP_MEMBERSHIP socket options. BUT it looks like the