No description
* 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. |
||
|---|---|---|
| apps | ||
| aux | ||
| build-root/scripts | ||
| doc | ||
| docker | ||
| etc | ||
| example | ||
| extras | ||
| fuzz | ||
| include | ||
| lib | ||
| test | ||
| util | ||
| yang | ||
| .gitignore | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| configure | ||
| configure.ac | ||
| LICENSE.md | ||
| Makefile.in | ||
| README.md | ||
Clixon is a YANG-based configuration manager, with interactive CLI, NETCONF and RESTCONF interfaces, an embedded database and transaction mechanism.
See documentation, project page and examples, Travis-CI
Clixon is open-source and dual licensed. Either Apache License, Version 2.0 or GNU General Public License Version 2; you choose, see LICENSE.md.
See CHANGELOG.md release history.
Clixon interaction is best done posting issues, pull requests, or joining the slack channel. Slack invite (updated 5/2 2021)
Clixon is sponsored by Rubicon Communications LLC(Netgate)