Re: [Netconf] SSH question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Netconf] SSH question



Juergen Schoenwaelder wrote:
On Thu, Jun 18, 2009 at 07:36:34PM +0200, Andy Bierman wrote:
You know about openssh, and the ClientAliveInterval messages
that it sends (keepalive at openssh.com)?  The client is
supposed to send data on the channel before N of these
arrive.

It seems that libssh2 drops these messages.
But if the NETCONF manager wanted to answer,
what can it send to the agent?  whitespace?
an XML comment?

Is the agent supposed to handle (discard) non-PDU messages
received on its channel? What is the most interoperable
way to send data to the agent without actually issuing
an <rpc> and wasting resources?

I think you are confusing protocol layers. The keepalive at openssh.com
messages are sent as part of the SSH Connection Protocol (see RFC
4254) and they should trigger an SSH Connection Protocol reply. They
should never show up in the data stream carried over an SSH channel.
If they do, then the SSH implementation needs to be fixed.


thanks.
you are right -- these are CHANNEL_REQUEST messages,
not CHANNEL_DATA messages. Not sure what libssh2 is
answering with, but it isn't working (yet).


/js


Andy


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.