Closed iGovindY closed 2 years ago
Not sure what the problem is, I first got a NACM error, which was expected. After turning it off some mandatory node was missing.
> edit-config --target running --config
ERROR
type: protocol
tag: access-denied
severity: error
path: /_3gpp-common-managed-element:ManagedElement
message: Access to the data model "_3gpp-common-managed-element" is denied because "tls-test" NACM authorization failed.
> edit-config --target running --config
ERROR
type: application
tag: operation-failed
severity: error
message: Mandatory node "priorityLabel" instance does not exist.
type: application
tag: operation-failed
severity: error
message: User callback failed.
> exit
And I have connected over TLS although I really do not know how that could affect this.
Hi Michal,
only step you might be doing differently is yang install and configure configuration in Keystore, Truststore, netconf-server yangs.
I have included all scripts and yangs in netopeer-crash.tar.gz, no extra step required.
with the below steps, you should be able to reproduce.
cd /tmp
wget https://github.com/CESNET/netopeer2/files/7089845/netopeer-crash.tar.gz
tar -zxf netopeer-crash.tar.gz
cd netopeer-crash/
./sysrepo_reset.sh && ./configure_netconf_server.sh false <server-ip e.g: 10.207.1.21>
netopeer2-server -dv2
netopeer2-cli
connect --tls --host <server-ip e.g: 10.207.1.21> --port 6513 --cert /tmp/netopeer-crash/client.crt --key /tmp/netopeer-crash/client.key --trusted /tmp/netopeer-crash/ca.pem
edit-config --target running --config=/tmp/netopeer-crash/ME_config.xml
ERROR on client
nc ERROR: SSL socket error (Success).
cli_send_recv: Failed to receive a reply.
nc ERROR: Invalid session to read from.
The exact same result, using the current devel
.
Hi,
netopeer server crashes on edit-config with TLS. similar back trace is seen with callhome mode and without callhome mode.
Steps:
/tmp/mm.xml
Netopeer server back trace