You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
netopeer2-server not connecting to second client #627
I have a test with the following scenario: 1 netconf server in front of 2 netconf clients
client 1 with IP address X
client 2 with IP address Y
netopeer2-server connects to client 1
netopeer2-server connects to client 2
callhome successfully established for both
kill the 2 sessions sucessfully
delete callhome data from sysrepo and unallocate IP addresses for both clients:
18:43:28.370 INFO/UE_APP-OAM/netopeer2-server(PID:2175): [INF]: LN: Session 4: Call Home client "client 1" removed, but an established session will not be terminated.
18:43:28.371 netopeer2-server(PID:2175): [INF]: LN: Session 4: Call Home client "client 1" thread exit.
client 2 with address Y starts listening
reconfigure callhome data in sysrepo for client 1 with remote-address X
netopeer2-server tries to connect to it:
18:47:44.640 netopeer2-server(PID:11205): [INF]: LN: Call Home client "client 1" endpoint "default-ssh" connecting...
18:47:44.640 netopeer2-server(PID:11205): [INF]: LN: Trying to connect via IPv4 to X:4334.
18:47:44.640 netopeer2-server(PID:11205): [INF]: LN: Successfully connected to X:4334 over IPv4.
18:47:54.641 netopeer2-server(PID:11205): [ERR]: LN: **SSH key exchange timeout.**
And it continues to try to connect with same error SSH key exchange timeout.
Maybe the SSH key exhange timeout is normal since there is no client listening with that IP address for now.
Then meanwhile, we configure client 2 with remote-address Y in sysrepo but netopeer2-server doesn't initiate the callhome as expected, there might be a problem here, what do you think?
Activity
Roytak commentedon Aug 24, 2026
Hello, what versions of libnetconf2 and netopeer2 are you using?
yoousra commentedon Aug 24, 2026
Hi,
Using the versions: netopeer2-v2.7.0-12-g2809ede and libnetconf2-v4.1.2-34-g50defb3
Thank you.
Roytak commentedon Aug 28, 2026
Should now be fixed in latest
devel(libnetconf2 v4.5.0).