I've got a similar issue right now with the tm4c.
Tested with putty as a receiver and didn't happen.
With a python app I've had it not happen in 1h but usually it takes less
than 5min, even less than 1min sometimes.
--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html
-0300
>From: "Sergio R. Caprile"<scapr...@gmail.com>
>To:lwip-users@nongnu.org
>Subject: Re: [lwip-users] TCP packet out-of-order
>Message-ID:<8b2070c9-0e63-add8-6249-e7328c316...@gmail.com>
>Content-Type: text/plain; charset=utf-8; format=flowed
>
>I see
...@gmail.com>
To:lwip-users@nongnu.org
Subject: Re: [lwip-users] TCP packet out-of-order
Message-ID:<8b2070c9-0e63-add8-6249-e7328c316...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
I see your out-of-order friend in frame #11 looks very much like frame
#8 revisited. I w
I see your out-of-order friend in frame #11 looks very much like frame
#8 revisited. I would say that is a DMA driver glitch (are you using DMA
?), however, the IP ID field is different, so it looks more like a
resend, due to frame #9 being internally lost; however, this does not
look
Maybe it is just me, but I can't access your link.
Can you post the wireshark capture ?
Also, can you please describe exactly what you are doing and in which
environment ? lwIP 1.4.1 has 3 different APIs, you might or not have an
RTOS, you might be not paying attention to single-threading rules
Hi there,
I am use lwIP 1.4.1 and the test ran for long time before I ran into a
problem with TCP packet out-of-order.
The PC (windows 10) is acting properly but lwip sent out a packet with
out-of-order sequence segment:
This was captured on Wireshark and I saved the data around this event
