Repository navigation
netconf capability wrong #405
Description
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>" +
Reacted by declspec
Activity
declspec commentedon Jan 9, 2020
Just ran into this as well, makes the whole
NetConfClientunusableEDIT: Side-note, this library is very difficult to work with; virtually everything useful is marked as
internalso the chances of implementing any workarounds seems to be virtually zero.The entire
Subsytemimplementation is internal, the baseISessionis internal, theIServiceFactoryis 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
ClientCapabilitiesXML before connecting, however theINetConfSessionis only instantiated when callingConnect()and immediately uses them before you can change them.