This repository was archived by the owner on Jul 16, 2025. It is now read-only.
- Notifications
You must be signed in to change notification settings - Fork 65
CallHome
michalvasko edited this page Oct 2, 2015 · 1 revision
Call Home is a mechanism for allowing servers to initiate connections to clients. Its configuration is a part of ietf-netconf-server model used by Netopeer. There are so-called applications that can have many servers defined. An application tries to connect to each server (which is, in fact, a client) until a connection and a NETCONF session is established. There are various options in the model that enable to tune the exact behavior.
To try an SSH Call Home, you can use this example configuration.
<netconf xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-server"> <ssh> <call-home> <applications> <application> <name>test</name> <servers> <server> <address>127.0.0.1</address> <port>6666</port> </server> </servers> <host-keys> <host-key> <name>localhost</name> </host-key> </host-keys> </application> </applications> </call-home> </ssh> </netconf> It leaves all the options on default. If you use the listen command in netopeer-cli, a connection will be initiated by netopeer-server. The host-keys container is actually not supported and is ignored by the server, but the model demands it.