-
Notifications
You must be signed in to change notification settings - Fork 75
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
Clixon-backend lacks rfc 6242 <hello> protocol #532
Comments
This is the internal NETCONF protocol . The external NETCONF interface supports this. |
Further note even when I force ncclient to run on netconf base 1.1, the clixon-backend still fails to send it's server side capabilities to the client and only sends session-id. ncclient debug log:
clixon-backen:
|
Clixon-backend only listens for NETCONF 1.1 chunked messages. When trying to connect via netconf application such as ncclient the connection is never established because of the lack of proper exchange of capability's aka <hello>.
Example using ncclient to connect to clixon-backend using unix_socket:
ncclient:
clixon-backend in D3 mode:
proper framing protocol: https://datatracker.ietf.org/doc/html/rfc6242#section-4.1
The text was updated successfully, but these errors were encountered: