* 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 | ||
| mandatory | ||
| optional | ||
| Makefile.in | ||
| README.md | ||
Yang files
There are three classes of Yang files
- Clixon yang files.
- Mandatory: "Standard" yang files necessary for clixon lib/client/backend to run
- Optional: "Standard" yang files for examples and tests
The first two (clixon and mandatory) are always installed. If you want
to change where the are installed, configure with: --with-yang-installdir=DIR
The third (optional) is only installed if configure flag
--enable-optyang is set. Further, the optional yang files are
installed in --with-opt-yang-installdir=DIR if given, otherwise in
the same dir as the mandatory.