Hi All,
is it possible to define on Dataminer and/or within a protocol the flag to end connection with an end device.
We have a device that doesn't respond to a FIN flag instead only closes connection on the receipt of an RST flag, therefore when DataMiner sends a FIN flag it only half closes the connection and then closes later when Dataminer sends an RST flag as it hasnt recieved the expected response from the device.
Thanks
Hi Ryan,
This seems like a device issue as it does not comply with the TCP standard (RFC9293). I don't think we should have any custom logic in DataMiner to cope with devices that do not follow the standard. Section '3.6 Closing a connection' of RFC9293 defines how connections can be closed. If the device does not respond to a FIN flag, it basically means it does not support the TCP standard.
Hi Michiel, You are 100% correct it doesn’t comply with TCP standards, as confirmed by the manufacturer, hence my question to see if Dataminer supported anyway of defining the close flag for TCP unsupported devices.
Thanks
Hi Ryan,
There is an option to use your own code/libraries to connect to a device from the QActions of the connector. The downside is that it will not go through DataMiner and therefore also bypass certain things (e.g. streamviewer will not be able to show this communication). That way you could have the flexibility to do these things, but I don’t think we should support it in the DM SW as it does not follow a standard.
IMO, the vendor should provide the libraries to communicate to the device if they are not following the standard.
If you believe the device is working according to the standard, then I believe it is best that you create a task in Collaboration with the WireShark capture, this way we know exactly how the device and DataMiner behave.
For example could be the following, but not sure until we know for sure this is the problem: https://www.rfc-editor.org/rfc/rfc2525#section-2.16