* Hello message semantics has been made stricter according to RFC 6241 Sec 8.1, for example: * A client MUST send a <hello> element. * Each peer MUST send at least the base NETCONF capability, "urn:ietf:params:netconf:base:1.1" (or 1.0 for RFC 4741) * The netconf client will terminate (close the socket) if the client does not comply * You can set `CLICON_NETCONF_HELLO_OPTIONAL` to true to use the old behavior of essentially ignoring hellos. * New clixon-config@2020-03-08.yang revision * Added: `CLICON_NETCONF_HELLO_OPTIONAL` * The base capability has been changed to "urn:ietf:params:netconf:base:1.1" following RFC6241. |
||
|---|---|---|
| .. | ||
| clixon_netconf.h | ||
| Makefile.in | ||
| netconf_filter.c | ||
| netconf_filter.h | ||
| netconf_lib.c | ||
| netconf_lib.h | ||
| netconf_main.c | ||
| netconf_rpc.c | ||
| netconf_rpc.h | ||
| README.md | ||
Clixon Netconf
Clixon implements NETCONF as external access, and also as an internal protocol between backend and frontent clients.
For more defails see Clixon docs netconf