lwIP issue with remote close of persistent TCP connection
Posted: Fri Jul 14, 2017 1:53 pm
Hello
I have brought in the lib xtcp 6.0.0 and modified the simple webserver demo into a TCP echo server with persistent connection until closed by peer (basically the same as TCP echo service).
I am using circuit based on MC audio board and also running the AVB/TSN stack with TDM master and RGMII, but with 100Mbps support only (GbE removed) per http://www.xcore.com/viewtopic.php?f=26&t=4731&p=24242
I am testing the echo server by opening a telnet connection from a directly connected Mac that can also receive the AVB data. The issue I am seeing is if I run the lwip stack I am not receiving XTCP_CLOSED event when the peer closes telnet, but I do receive the XTCP_CLOSED event in this circumstance if I run the uIP stack. Any idea why this might be the case?
I understand the lwIP stack is supposed to be higher performance than the uIP stack which might be important at some point in time. It's not a huge issue at present but I haven't tested the throughput of the echo server. I only need about 10kbps right now so I suspect (hope) uIP is capable of that unless someone knows why lwIP is not issuing the XTCP_CLOSED event when the peer closes the connection.
Or is there any compelling reason to use lwIP rather than uIP?
I have brought in the lib xtcp 6.0.0 and modified the simple webserver demo into a TCP echo server with persistent connection until closed by peer (basically the same as TCP echo service).
I am using circuit based on MC audio board and also running the AVB/TSN stack with TDM master and RGMII, but with 100Mbps support only (GbE removed) per http://www.xcore.com/viewtopic.php?f=26&t=4731&p=24242
I am testing the echo server by opening a telnet connection from a directly connected Mac that can also receive the AVB data. The issue I am seeing is if I run the lwip stack I am not receiving XTCP_CLOSED event when the peer closes telnet, but I do receive the XTCP_CLOSED event in this circumstance if I run the uIP stack. Any idea why this might be the case?
I understand the lwIP stack is supposed to be higher performance than the uIP stack which might be important at some point in time. It's not a huge issue at present but I haven't tested the throughput of the echo server. I only need about 10kbps right now so I suspect (hope) uIP is capable of that unless someone knows why lwIP is not issuing the XTCP_CLOSED event when the peer closes the connection.
Or is there any compelling reason to use lwIP rather than uIP?