Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 328 subscribers
  • Views 596 views
  • Users 0 members are here
Related

TCP server on zedboard shuts down after some interval

Former Member

Hello,

I have created a LWIP TCP server on the zedboard and a TCP client on MATLAB on the host computer(zedboard and host computer are connected over ethernet). The client requests the connection to the server, SYN, SYNACK and ACK packets are delivered successfully and the connection is established. (Packets are monitored on wireshark on the host computer).

 

Now, If the client keeps sending the data continuously to the server, then server receives the data and process them. BUT the server crashes if I take some time interval in sending the data. For example: If I send data from client to server at time 0, and I take a gap of 60 seconds and then try to send the data from client to server, then by this time the TCP server has crashed and it does not receive data.

If I keep sending data continuously then it does not crash, but if I take some time sending the next data, then TCP crashes.

 

can anyone suggest where I am going wrong 

I have been looking over the Internet to find solutions but any help/suggestions would be appreciated.

Thanks

Parents
  • 0

    I can't see anything in your code which would break the connection on the client, unless the recv_callback is used when you are not in the established state, in which case you will be freeing the pbuf, which will likely terminate the connection.

    I have most experience with sockets and RTOS, I would recommend looking into it if your application is going to include more than a couple of network functions, all reasoning here: https://www.xilinx.com/video/soc/networking-with-lwip-focused-free-rtos.html

    As for the TCP Keep Alive, I would read this source to gain the understanding and use a packet sniffer program, such as Wireshark, to see why the connection is closed and by which end. That way you will be able to see where the issue is.

    http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html

    A potentially easier 'high level' fix could be to make the client send a random packet periodically when no streaming is necessary, this could be used as a 'keep alive' to the TCP connection.

    Please note, I cannot be held responsible for any software installation that may or may not cause damage to the installed location. The installation of software is under discretion of the user and with the IT administrators permission.

Reply
  • 0

    I can't see anything in your code which would break the connection on the client, unless the recv_callback is used when you are not in the established state, in which case you will be freeing the pbuf, which will likely terminate the connection.

    I have most experience with sockets and RTOS, I would recommend looking into it if your application is going to include more than a couple of network functions, all reasoning here: https://www.xilinx.com/video/soc/networking-with-lwip-focused-free-rtos.html

    As for the TCP Keep Alive, I would read this source to gain the understanding and use a packet sniffer program, such as Wireshark, to see why the connection is closed and by which end. That way you will be able to see where the issue is.

    http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html

    A potentially easier 'high level' fix could be to make the client send a random packet periodically when no streaming is necessary, this could be used as a 'keep alive' to the TCP connection.

    Please note, I cannot be held responsible for any software installation that may or may not cause damage to the installed location. The installation of software is under discretion of the user and with the IT administrators permission.

Children
No Data