TCP Server Socket with keep alive / No Timeout INT occurs when client is killed
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: TCP Server Socket with keep alive / No Timeout INT occurs when client is killed
by Eugeny ·
No, everything is correct.
Server waits for incoming packets, and it will be waiting forever until it will receive something - FIN, RST, or data.
You do it manually (0x22), or use keep-alive timer.
Datasheet says:
There will be no keep-alive (neither 0x22 nor automatic using timer) if there was no prior communication.
RE: TCP Server Socket with keep alive / No Timeout INT occurs when client is killed
by oliver28 ·
Thank you for the information.
In fact the TCP server starts sending KEEP ALIVE packets first when a TX packet was transferred by the TCP Server.
RX packets witout response by the server will not start the KA process. (even if KA timer is set or CMD 0x22 is written to the Command Reg.)
I will resolve the detection of those dead connections in an other way. (no activity, after a defined timeout , send 1 Byte TX, this should start the KA process)