Re: [lwip-users] TCP spurious Retransmission and Dup Ack issue

2017-01-15 23:20 GMT+08:00 Axel Lin : > 2017-01-09 21:56 GMT+08:00 Sergio R. Caprile : >> Your sequence number is jumping backwards. >> Most common causes are either one of your apps is trashing memory of you >> have a bad DMA driver. > > Hi Sergio, > >

Re: [lwip-users] TCP spurious Retransmission and Dup Ack issue

2017-01-09 21:56 GMT+08:00 Sergio R. Caprile : > Your sequence number is jumping backwards. > Most common causes are either one of your apps is trashing memory of you > have a bad DMA driver. Hi Sergio, Thanks for your comments. It seems every time before run into

Re: [lwip-users] TCP spurious Retransmission and Dup Ack issue

Your sequence number is jumping backwards. Most common causes are either one of your apps is trashing memory of you have a bad DMA driver. ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [lwip-users] TCP spurious Retransmission and Dup Ack issue

Please don't send such utterly long attachments! This is a public mailinglist. Axel Lin wrote: > Hi, > I'm using netconn API. > While testing lwIPv2.0.1, I found my device seems stuck after running > for a couple minutes. > > My device running lwIP (192.168.0.103) as a tcp client. > A Linux

[lwip-users] TCP spurious Retransmission and Dup Ack issue

Hi, I'm using netconn API. While testing lwIPv2.0.1, I found my device seems stuck after running for a couple minutes. My device running lwIP (192.168.0.103) as a tcp client. A Linux laptop (192.168.0.104) running "netcat -l 8088" to receive data. In my use case, it's one-direction data transfer