An explanation about the xml format in netopeer2 rpc messages

[anoikob]

Hey there. I am running netopeer2 from a docker container. According to the author of the container, I should use this snippet

to communicate with the server. I do, and it works. Suppose I wanna check out the candidate datastore, I should change the "running" to "candidate" and send that message to the server. Here's the issue which I have not been able to solve after looking into the xml documentation here and the netconf protocol's documentation here : What does the "#139" mean, how is it related to the message I'm sending, and what are the 2 ## at the end doing? The documentation and tutorials I've viewed about netconf do not show that.

[michalvasko]

I strongly disagree with the author of the container and suggest you use an actual NETCONF client, not a plain SSH client (which I guess you are using). You can use netopeer2-cli for a simple CLI interface that does not require formatting NETCONF messages manually.

[anoikob]

ok, i'll give that a try, thank you

[anoikob]

Ok it seems to have worked, thanks a lot!

Now I have to figure out the yang language and create files to start editing the candidate and committing stuff. Thanks for your time!