With a DNP3_TG driver configured for use with a dual endpoint, after the master initially established a connection and closed the connection again due to inactivity after the idle timeout, an outstation can successfully connect to the listening endpoint opened by the master. The master however does not accept link status requests or unsolicited responses on the listening endpoint and closes the connection to the outstation again.
With a DNP3_TG driver configured for use with a dual endpoint, after the master initially established a connection and closed the connection again due to inactivity after the idle timeout, an outstation can successfully connect to the listening endpoint opened by the master. The master however does not accept link status requests or unsolicited responses on the listening endpoint and closes the connection to the outstation again.
An issue has been addressed in the DNP3_TG driver where the master did not correctly process unsolicited responses sent from an outstation when the outstation initiated the TCP connection. Now the master also correctly processes unsolicited responses on an outstation initiated connection