LabVIEW
Is there a way to tell if TCP closed because of RST or FIN?
It's very unclear to me how you conclude that this is possible in Python from the link you post. I can't see Python mentioned anywhere in there.
That all said, relaying on such things on your side is the opposite of robust network programming. You do not want to do different code execution depending on if the remote side aborted or ordinarily closed the connection. In both cases you should simply assume that that connection has left your party and while it may return later on, it will do so through a new connection in either case. It will be however important for you to also explicitly close your side of the connection anyhow, such that the TCP FIN handshake can be completed. Otherwise the remote socket may stay lingering in the CLOSE_WAIT state forever. which could prevent you from reconnecting.
While I believe that you can indeed not really distinguish the two connection closures in LabVIEW, even if you could, there is a very big chance that this behavior might be rather platform specific. and might even change between OS versions and socket implementations. In general robust networking code is not about relaying on such minimal distinctions but rather about working with the more generic situation that a connection has been terminated by the peer, normally or not should not really concern your application.
Well, if I understand the TCP state machine correctly, the RST is really only meant to be sent if you try to establish a connection and the remote socket driver can't find an according socket bound to the specific port (or it is lingering in CLOSE_WAIT state). Once you have had successful data transmission between the two sides, the remote side is expected to terminate the connection through a FIN packet.
Of course there might be variations in how this in detail works out depending on the socket implementation, so while logging might possible reveal certain things, it might be actually more platform specific than anything else.
