search

kelleyk / noVNC

A fork of noVNC that adds support for the ATEN iKVM "AST2100" (0x57) video encoding, as used by the BMCs in recent SuperMicro servers. (See the "bmc-support" branch.)
http://novnc.com
Other
86 stars 16 forks source link

KVM connection no longer working after upgrading to bmc-support branch #3

Open jleroy opened 7 years ago

jleroy commented 7 years ago

First of all, thank you Kevin for your hard work on the RFB protocol. This is really appreciated. 👍

Since I've updated my noVNC setup from commit 63cc01f796ed7df80c537269f9f4855ab7df5169 (lastest commit from bmc-support-old branch) to eb386b7672b1cef4ca02c9da769d5d08beefd0ab (latest commit from bmc-support branch), I can no longer connect to any of my servers.

I get a red banner in noVNC with the following error message: Unsupported server.

Here's the output of my browser's console (latest version of Google Chrome on macOS 10.12.3):

util.js:66 Data URI scheme cursor supported
util.js:64 >> RFB.constructor
util.js:64 >> Display.constructor
util.js:64 User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36
util.js:64 Browser: webkit 537.36
util.js:64 Setting viewport to full display region
util.js:64 << Display.constructor
util.js:64 >> Keyboard.allKeysUp
util.js:64 << Keyboard.allKeysUp
util.js:66 Using native WebSockets, render mode: canvas rendering
util.js:64 << RFB.constructor
util.js:64 New state 'connecting', was ''.
util.js:64 >> RFB.connect
util.js:66 connecting to ws://localhost:6080/websockify
util.js:66 Detected binaryType support in WebSockets
util.js:64 << RFB.connect
util.js:64 >> WebSock.onopen
util.js:66 Server choose sub-protocol: binary
util.js:64 Starting VNC handshake
util.js:64 << WebSock.onopen
util.js:66 Server ProtocolVersion: 003.008
util.js:64 Sent ProtocolVersion: 003.008
util.js:64 Server security types: 16
util.js:64 Authenticating using scheme: 16
util.js:66 Detected ATEN iKVM server (using heuristic #0 -- older Winbond/Nuvoton or Renesas BMC?).
util.js:70 Failed when connecting: Unsupported server (Unknown SecurityResult)
Util.Error @ util.js:70
_fail @ rfb.js:627
_handle_security_result @ rfb.js:1139
_init_msg @ rfb.js:1367
_handle_message @ rfb.js:693
_recv_message @ websock.js:386
util.js:64 New state 'disconnecting', was 'connecting'.
util.js:64 >> RFB.disconnect
util.js:64 >> Keyboard.allKeysUp
util.js:64 << Keyboard.allKeysUp
util.js:66 Closing WebSocket connection
util.js:66 Encoding stats for this connection:
util.js:66 Encoding stats since page load:
util.js:66     COPYRECT: 0 rects
util.js:66     TIGHT: 0 rects
util.js:66     TIGHT_PNG: 0 rects
util.js:66     HEXTILE: 0 rects
util.js:66     RRE: 0 rects
util.js:66     RAW: 0 rects
util.js:66     ATEN_AST2100: 0 rects
util.js:66     ATEN_ASTJPEG: 0 rects
util.js:66     ATEN_HERMON: 0 rects
util.js:66     ATEN_YARKON: 0 rects
util.js:66     ATEN_PILOT3: 0 rects
util.js:66     JPEG_quality_med: 0 rects
util.js:66     compress_hi: 0 rects
util.js:66     DesktopSize: 0 rects
util.js:66     last_rect: 0 rects
util.js:66     Cursor: 0 rects
util.js:66     QEMUExtendedKeyEvent: 0 rects
util.js:66     ExtendedDesktopSize: 0 rects
util.js:66     xvp: 0 rects
util.js:66     Fence: 0 rects
util.js:66     ContinuousUpdates: 0 rects
util.js:64 << RFB.disconnect
util.js:64 New state 'disconnected', was 'disconnecting'.
util.js:64 Clearing disconnect timer
util.js:64 >> WebSock.onclose
util.js:64 << WebSock.onclose

Here's the list of motherboard tested:

All of these motherboard worked with the bmc-support-old branch, none works with the bmc-support branch.

willglynn commented 7 years ago

I second this -- bmc-support-old works (63cc01f796ed7df80c537269f9f4855ab7df5169), bmc-support doesn't (eb386b7672b1cef4ca02c9da769d5d08beefd0ab) -- on:

disaster123 commented 7 years ago

Same here with X9SRH-7F

otupman commented 7 years ago

I've the same here with a X10SDV-TLN4F