Update: Even when copying the current LWIP master state of the top of tcp_process() to my 1.4.1 working copy, the behavior still results in this RST/ACK pingpong.
I fear that something in tcp_receive() has changed as well or even deeper? At least in the referenced bug report, the current state of master seems to have helped. My only idea right now is to blame it on the IP stack of the peer but that is a bit counterproductive right now. Any further ideas or help in this? Kind regards Fabian -----Original Message----- From: lwip-users <[email protected]> On Behalf Of Sergio R. Caprile Sent: Montag, 11. März 2019 13:49 To: [email protected] Subject: Re: [lwip-users] TCP state machine problem? LWIP 1.4.1 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. I guess this is what I remember... not exactly your problem nor a helping hand but perhaps you can start digging here: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsavannah.nongnu.org%2Fbugs%2F%3F48328&data=02%7C01%7Cfabian.koch%40de.abb.com%7C589d34f7bc5246775db008d6a620398d%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636879054661901465&sdata=vrNa%2B%2FWJEbduI0x6jFfNikdNIuCMJNtGmYfw55D6Y9E%3D&reserved=0 _______________________________________________ lwip-users mailing list [email protected] https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.nongnu.org%2Fmailman%2Flistinfo%2Flwip-users&data=02%7C01%7Cfabian.koch%40de.abb.com%7C589d34f7bc5246775db008d6a620398d%7C372ee9e09ce04033a64ac07073a91ecd%7C0%7C0%7C636879054661901465&sdata=j%2BDCwH4vS%2F3i9LSRzaiLzT6GDIUe59p8eesKtlE%2B3kI%3D&reserved=0 _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
