Christian Gouret
Christian Gouret
Hello, Does Netopeer2 supports feature local-binding-supported from ietf-tcp-client for call-home : leaf local-address { **if-feature "local-binding-supported";** type inet:ip-address; description "The local IP address/interface (VRF?) to bind to for when connecting...
Hello, Below, a simple scenario fully driven from CLI based on v2.0.35 During this scenario, no any error in NC Server logs. 1) Call Home 2) subscribe with replay =>...
I switched recently to the following software version from the devel branch(v2) : Netopeer2 v2.0.35 Scenario : In CLI, alternative listen/disconnect cmd leads to the following logs at Server level....
View on v2.1.36 With new SSL checks taking place to conform to RFC6125 via [#322](https://github.com/CESNET/libnetconf2/issues/322), listen command needs an additional parameter to pass CN/SAN of part of the NC Server...
Based in Netopeer2 v2.1.36 with following RPC : ``` /tmp/orusim-config.xml sftp://[email protected]/tmp/orusim-config-to-send.xml mysftppasswd ct:secp256r1 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBOSC92eVsX3a9Du5sWoku5swcH5XKxZTZ5Vkgcb9Hj5xcB10UM2zLmo313jdWDV3lyOGQML638i3C6bka58V6Xs= ``` CLI returns following error message : user-rpc --content /opt/dev/xml/o-ran-file-download-orusim-config-ok.xml ly ERROR: Invalid union value "ct:secp256r1"...
Hello, tls_callhome.xml example shared in example_configuration directory is setting both ca-certs and ee-certs. While in in ietf-netconf-server, we have the following specification : refine "client-authentication" { must 'ca-certs **or** ee-certs';...
With netopeer2 in Version 2.2.13, on top of embedded module ietf-crypto-types in revision 2023-12-28, we are loaded same module but in revision 2019-04-29. Seems to be properly supported by the...