Q: Having a fresh installation of netopeer2-server, when I connect to it I see (or something similar):
[ERR]: LN: Failed to set hostkey "genkey" (/tmp/dvcjwz).
A: You are using libssh that was compiled with gcrypt library as the crypto backend. It does not support default SSH keys generated during netopeer2-server installation. To fix, disable support for this backend when compiling libssh so that some other one is used.
Q: When a new NETCONF session is being created, I see the error:
Starting the SSH session failed ()
A: The most likely reason for this is that the SSH key that is used for this session authentication uses an algorithm not supported by your system. The supported algorithms are automatically loaded by libssh from OpenSSH configuration files (more info in ssh_config(5) and sshd_config(5)).
Q: When I try to connect to a server I immediately get a timeout after authenticating:
A: You are probably using libssh version 0.9.3 that includes this regression bug. To solve it, you must use another version.
Q: When I connect to a server, after around 10-20 seconds I get disconnected with an error:
[ERR]: LN: Session 1: inactive read timeout elapsed.
A: There are 2 most common reasons for this error. Either you are not using a NETCONF client to connect (but ssh(1), for example) and the messages received by the server are not properly formatted (even an additional \n can cause this problem). To fix, use a NETCONF client instead. Another reason may be that you are using libssh version 0.9.4. It includes a regression bug that causes this problem and you must use another version to fix it.
Q: When I try to enter authentication tokens, they always echo back even though I set echo off:
A: You are most likely using an older version of libssh which contains a bug. The bug was fixed in libssh 0.9.0, so you must use at least that version.