netconf connection stays in “close_wait" about netopeer2 HOT 13 OPEN

So what exactly is happening? I would guess the server disconnected the client because of idle-timeout and once the client sends any RPC, this will be discovered, the client closes the socket, and the connection is properly terminated.

from netopeer2.

I got a log（attached） from which I can see that the client actively disconnected and will repeatedly connect and then disconnect. Tracking "Session 10" further reveals that the client creates one ssh session and open multiple channel

netopeer2-server-log.txt

from netopeer2.

Whatever the case, based on what I understand, this TCP state occurs when the connection is closed by one end and not by the other. And unless you can provide more information, I will assume it is the client not closing the connections, which is not something I can help with.

from netopeer2.

According to the TCP state diagram below, we can know netopeer2-server receive the FIN but not send FIN to the remote.

I also noticed that this function(nc_session_free_transport), when dealing with multiple NETCONF session, will not immediately close socket. According to the previous log, we know that the client has created multiple NETCONF session in one SSH session. then close SSH session directly. Does this matter?

from netopeer2.

Okay, then I would suggest you use the current latest release in the master branch (or even the devel) of the projects, I seem to remember some changes in how sockets were handled recently. As for freeing multi-channel SSH sessions, you cannot close the socket unless all the channels (NETCONF sessions) were closed because they all use the same SSH session (the same socket).

from netopeer2.

Has the latest devel branch fixed the above scenario?

So for the client, if the connection netopeer2-server uses multi-channel SSH, does it have to be close channel before closing the SSH session connection?

from netopeer2.

Has the latest devel branch fixed the above scenario?

I cannot guarantee it but it is possible.

So for the client, if the connection netopeer2-server uses multi-channel SSH, does it have to be close channel before closing the SSH session connection?

The NETCONF client is supposed to close all the NETCONF sessions, whatever way they were created. And netopeer2 will internally close the socket (SSH session) once there are no NETCONF sessions using it.

from netopeer2.

New discoveries：
netopeer2-server work threads stuck at "nc_session_free_transport"

from netopeer2.

I am not able to learn more because no libnetconf2 version I have looked at session.c:762 had any code there that could cause a hang. Please specify the version you are using, I thought you have updated to current devel.

from netopeer2.

I use the version of libnetconf2 is v2.1.37. It hangs in the while loop, please see following code

I noticed that the above code has been removed in the new release, so I want to do a patch to remove those code from the current version, but I don't know if it will have any other impact.

from netopeer2.

You are free to apply only a patch but please do not ask for more support. We support only current master and devel versions.

from netopeer2.

Okay, got it. Since updating to the latest devel involves updates to other components, such as openssl, I want to temporarily fix it before updating

from netopeer2.

Then the OpenSSL version you are using is no longer supported, which is a significant security risk.

from netopeer2.