Re: [lwip-users] TCP ACK not received - Probably due to seq no.

[Gaurav Jain]

Pardon me for opening multiple threads. I felt probably a better
subject would suffice and wanted to close that thread but did not find
how to do that.
Yes, I am using the RAW APIs. My port actually works and I know that
because, if I change the mode to immediate loopback mode, i.e. the
data received in packet is sent back to the client. However when I
change the implementation to the store approach, i.e. I write the
entire data received into an onboard memory, and then read it from the
memory to send it back to the client, I am facing this issue.

I have attached the packet capture file. There may be an error in my
understanding of the scenario. Please provide insights.

On Fri, Feb 5, 2016 at 7:09 PM, Sergio R. Caprile <address@hidden> wrote:
> Please do not open multiple threads for the same issue. Let's stay on
> this one as the subject is (probably) more fit.
> No, you don't need to do anything to "reverse the communications flow",
> it is "built into TCP", it is full-duplex in its very own nature.
> Please post a capture file, descriptions are subjective.
> Your description sounds odd to me, seqnos are established at connection
> handshake.
> Do you know your port actually works ? Did you try a known good
> application from the contrib tree ?
> What API are you using ? NO_SYS = ?
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lwip-users

capture_lwip.pcapng
Description: Binary data