clixon/apps/netconf
Olof hagsand 5692072d36 * Fixed: [CLIXON is not waiting for the hello message #184](https://github.com/clicon/clixon/issues/184)
* 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.
2021-03-10 14:18:16 +01:00
..
clixon_netconf.h Copyright 2021 2021-01-13 14:40:34 +01:00
Makefile.in Copyright 2021 2021-01-13 14:40:34 +01:00
netconf_filter.c Copyright 2021 2021-01-13 14:40:34 +01:00
netconf_filter.h Copyright 2021 2021-01-13 14:40:34 +01:00
netconf_lib.c Copyright 2021 2021-01-13 14:40:34 +01:00
netconf_lib.h Copyright 2021 2021-01-13 14:40:34 +01:00
netconf_main.c * Fixed: [CLIXON is not waiting for the hello message #184](https://github.com/clicon/clixon/issues/184) 2021-03-10 14:18:16 +01:00
netconf_rpc.c Copyright 2021 2021-01-13 14:40:34 +01:00
netconf_rpc.h Copyright 2021 2021-01-13 14:40:34 +01:00
README.md NETCONF README: https://github.com/clicon/clixon/issues/185 2021-03-07 15:29:33 +01:00

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