vncproxy icon indicating copy to clipboard operation
vncproxy copied to clipboard

Aten iKVM Support / encoding

Open BirknerAlex opened this issue 3 years ago • 1 comments

Hey,

I wanted to use the proxy but I got the following error when connecting with NoVNC to it. The upstream VNC server is a DELL iDRAC 8 KVM VNC server.

When connecting the VNC Proxy closes with this message:

[Error] ClientConn.MainLoop: bad message type, 250
[Warn ] ClientConn.MainLoop: exiting!
[Error] ClientUpdater.Consume (vnc-server-bound, SegmentFullyParsedClientMessage): problem writing to port: write tcp 10.10.16.2:38510->10.10.16.10:5901: use of closed network connection
[Error] IServerConn.Handle: listener consume err write tcp 10.10.16.2:38510->10.10.16.10:5901: use of closed network connection

Even If a ignore this message type 250 with continue (just testing) it continues the connection but fails then with:

[Error] MsgFramebufferUpdate.Read: unsupported encoding type: 134219775, 
[Error] ClientConn.MainLoop: error parsing message, MsgFramebufferUpdate.Read: unsupported encoding type: 134219775, 
[Warn ] ClientConn.MainLoop: exiting!
[Error] ServerConn.handle error: EOF

It seems "Aten iKVM" isn't supported, can we add this to the project? Sadly I am not familiar with the VNC protocol at all and I would give you any information I can provide or even giving access to a test server.

There are projects out there which are doing the encoding / translating already:

  • https://github.com/thefloweringash/aten-proxy
  • https://github.com/kelleyk/noVNC/tree/bmc-support/core/ast2100

I have also seen you have another project vnc2video which also supports Aten KVM.

BirknerAlex avatar Oct 07 '21 07:10 BirknerAlex

I'd love to see this as well. Supermicro IPMI using an Aten chip.

dsully avatar Sep 08 '23 15:09 dsully