Has anyone else been seeing similar issue, monitored via LWIP debug stats, high counts of TCP receive packet drops?
The Exosite TCP client eventually uses up all available HEAP memory on the XL-TM4C1294XL launch pad in trying to re connect to the server. No amount of Tweaks to (lwipopts.h) can augment high counts of (bad) packets coming from the internet, server or server network.
During morning and afternoon hours the Exosite client has a typical & very low count of receive packet drops. Client often runs for hours without interruption or (PCB) memory leaks. Our internet provider states packet loss is coming from an up stream source.
Do not believe the ISP is being completely honest. Believe TCP traffic shaping is causing packet delay frame corruption that only effects the Exosite http client SYNC ability when UDP has a bind to TCP stack. The Ethernet client with a UDP bind other than a DNS Broadcast has heap memory leak issues that escalate with packet loss. Oddly DNS is using UDP whether enable in LWIP or not.
LWIP 1.4.1 appears to default into a UDP broadcast schema when no UDP bind is configured.