Skip to content

netconf capability wrong #405

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
harveechen opened this issue Mar 20, 2018 · 1 comment · Fixed by #639
Closed

netconf capability wrong #405

harveechen opened this issue Mar 20, 2018 · 1 comment · Fixed by #639

Comments

@harveechen
Copy link

The client advise the base 1.0, however the flag to decide whether data framing mechanism to use is depended on the server response. When base 1.1 is advise by the server, the netconf gets wrong, since the client only advises 1.0 but the flag sets to use data framing mechanism.

Suggest that: in "NetConfSession.cs" add in line 44

"<capability>" + "urn:ietf:params:netconf:base:1.1" + "</capability>" +

@declspec
Copy link
Contributor

declspec commented Jan 9, 2020

Just ran into this as well, makes the whole NetConfClient unusable

EDIT: Side-note, this library is very difficult to work with; virtually everything useful is marked as internal so the chances of implementing any workarounds seems to be virtually zero.

The entire Subsytem implementation is internal, the base ISession is internal, the IServiceFactory is internal. anything that's public seems extremely high-level and doesn't allow you to work with the underlying SSH session.

I thought I might be able to workaround it by modifying the ClientCapabilities XML before connecting, however the INetConfSession is only instantiated when calling Connect() and immediately uses them before you can change them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants