[Feature Request] Add VNC Support as an Alternative to the Web Client

[lionB777]

Description:
Adding VNC support to JetKVM would provide an alternative to the web client, enabling full remote control with better interaction capabilities.

Proposed Enhancement:

Implement a VNC server compatible with standard clients (TigerVNC, RealVNC, TightVNC, etc.).

Support mouse input and improve keyboard event handling.

Optimize latency for smooth real-time interaction.

Implement authentication for secure access.

Use Case:
VNC support would offer a more responsive and flexible alternative to the web client, improving usability for remote management and troubleshooting. Additionally, it would allow the machine to be isolated from the network if needed, enhancing security and control.

Would this feature be feasible for a future release? Thanks for considering!

[left2repairlive]

+1 on this feature. VNC is an open protocol, widely used and made for computer remoting, so it is a good pick for this usecase.

It would also allow users that experience issues with the web interface to have a different method to try remoting into their JetKVM. I quickly found some users that could take advantage of this:

• Unable to move the mouse to certain areas #150
• JetKVM video freezes #148
• Full screen should fully capture keyboard #127
• Feature request: Scale stream to fit larger screen windows #121
• iOS browsers mouse in full screen mode #91

[swerveshot]

I would definitely welcome this feature. But just out of curiosity; why VNC and not RDP (FreeRDP or xrdp)? I would think that is a more optimized protocol with lower latency.

[lionB777]

You're right, it would be better, ideally both. But in my request, I thought that for the sake of compatibility it would be better. Since VNC exists on all platforms, I think this approach would be more universal. But I'm not an absolute expert on the subject, so if it can be done, that would be great.

[left2repairlive]

We default to VNC as it is more widespread in the circles are part of

[swerveshot]

We default to VNC as it is more widespread in the circles are part of

Ah that makes sense then.

Too bad though as RDP has some excellent features that VNC does not have. For instance having the ability to resize your client window and then have the server update it's canvas to match the new size. Or am I not up to speed with what's new with VNC?

[gravelfreeman]

Subscribing to this thread. Will order 4x if this ever gets implemented. Would fit perfectly in my workflow!

[quentinmit]

Too bad though as RDP has some excellent features that VNC does not have. For instance having the ability to resize your client window and then have the server update it's canvas to match the new size. Or am I not up to speed with what's new with VNC?

Resizing the desktop like that requires the cooperation of the host OS. Since JetKVM is just consuming the final video stream over HDMI, that would be difficult-to-impossible.

[swerveshot]

Resizing the desktop like that requires the cooperation of the host OS. Since JetKVM is just consuming the final video stream over HDMI, that would be difficult-to-impossible.

That's so true. I hadn't even considered that.

[saibarspeis]

If we get RDP/VNC I will order more. Just received my two KVM devices. Outside of some wonkiness with the USB power delivery it's amazing device so far!

[atsalyuk]

Too bad though as RDP has some excellent features that VNC does not have. For instance having the ability to resize your client window and then have the server update it's canvas to match the new size. Or am I not up to speed with what's new with VNC?

Resizing the desktop like that requires the cooperation of the host OS. Since JetKVM is just consuming the final video stream over HDMI, that would be difficult-to-impossible.

couldnt this be done by just updating the EDID to have an aspect ratio that matches the RDP window?