Little confused, can this be used for Remote Desktop sharing, like VNC?
DIY IP-KVM Based on Raspberry Pi
31–40 of 91 posts
Re: DIY IP-KVM Based on Raspberry Pi
#32Re: DIY IP-KVM Based on Raspberry Pi
#33Little confused, can this be used for Remote Desktop sharing, like VNC?
It can... but this goes one level lower to the hardware layer... so that you can do things like reboot the computer and view/edit BIOS settings (since you're viewing the same raw HDMI signal that would otherwise show up on a real monitor display). You wouldn't be able view the BIOS with Remote Desktop or VNC because those are not available until after the operating system has launched.
Re: DIY IP-KVM Based on Raspberry Pi
#34i got the V3 a bit ago, was definately worth it for an out-of-box running solution. though the fan settings needed fiddling so as to not make too much noise. KVMD_FAN_ARGS="--speed-idle=50 --speed-low=60 --temp-low=50" anywhoo for those who never and are curious the lag is almost entirely on the return channel, processing the hdmi signal and getting it back to client side. it is definatley useable for programming but…
V4 is a massive improvement in lag. The CM4 doubles the camera interface bandwidth, which was the bottle neck.
How much has video lag improved?
Re: DIY IP-KVM Based on Raspberry Pi
#35Little confused, can this be used for Remote Desktop sharing, like VNC?
IP-KVMs are more useful for fixing remote access without physically interacting servers. In cases where a server is stuck in BIOS, BSoD, wrong IP configured, just waiting for a RETURN key input, etc. and not responding to RDP/VNC/SSH, an operator can log into KVM to unstuck it.
Re: DIY IP-KVM Based on Raspberry Pi
#36I once wanted to build one like this, but for console devkits. That situation was and went, but I did end up wanting to have the same for all windows machines at work and home (Unity dev, so workstations, test runners even servers are desktop windows machines).
My solution was:
-BIOS: auto-power on when power is connected
-Smart power plugs on important computers
-AnyDesk for software on all machines, with unattended password set (connectable even at login screen, less annoying for licenses than Teamviewer)
-(Optional) my own WoL sending / restarting / RAT program for all the machines too
-(Optional) Parsec also installed, to allow remote desktop good enough latency/control wise for actually gaming remotely (which I often did!)
This way, I will never be stuck in a situation that I can't access a machine that I'm away from, unless it's one of those without a smartplug and has somehow hard crashed. Costs less than 20€ per machine. I've NEVER needed to access the bios or similar remotely.
I've recently played around with a lot of SBC's and have a spare capture card and cheaper sbc's that could work as OTG keyboards. Might end up building a crappy version of one of these for fun
Re: DIY IP-KVM Based on Raspberry Pi
#37I'm glad projects like this exist, but I'm too lazy and more than happy to have a Pi provide a serial console and a hardware reset via GPIO over IPv6 for colocated hardware. It's much simpler ;)
Re: DIY IP-KVM Based on Raspberry Pi
#38Earlier quoted context omitted.
<$10 adapter
Server VGA output to HDMI capture input? Needs an active converter in that direction, not a passive pinout-changing one.
/? db9 to USB
https://www.google.com/search?q=db9+to+USB
(RS-232, Serial port, UART, USB-TTL, USB-to-serial adapter: https://news.ycombinator.com/item?id=35120757 )
/? VGA capture card https://www.google.com/search?q=vga+capture+card
/? HDMI capture card USB-A Linux https://www.google.com/search?q=hdmi+capture+card+USB-A+linu...
--
Intel ME Management Engine, Intel AMT, Intel vPro (ME+AMT), AMD Pro; VNC to boot-time BIOS configuration
Intel AMT: https://en.wikipedia.org/wiki/Intel_Active_Management_Techno... :
> AMT is designed into a service processor located on the motherboard, and uses TLS-secured communication and strong encryption to provide additional security.[6] AMT is built into PCs with Intel vPro technology and is based on the Intel Management Engine (ME).[6] AMT has moved towards increasing support for DMTF Desktop and mobile Architecture for System Hardware (DASH) standards and AMT Release 5.1 and later releases are an implementation of DASH version 1.0/1.1 standards for out-of-band management.[7] AMT provides similar functionality to IPMI, although AMT is designed for client computing systems as compared with the typically server-based IPMI.
https://www.reddit.com/r/linux/comments/s41a17/in_2017_amd_p... :
> To understand what PSP and ME can do you need to understand CPU security rings. https://en.wikipedia.org/wiki/Protection_ring . These are different levels of privilege software has on the system.
> Originally the Linux kernel occupies ring 0, which is the level with highest privilege. Then user space would run in some other ring.
> However with things like PSP and ME they have created rings lower then ring 0. Things like Ring -1 and -2. Intel Minix ME runs in -3 ring.
vPro supports VNC over TLS.
coreboot and Libreboot don't support PQ SSH, TLS, VNC, or DASH; https://en.wikipedia.org/wiki/Libreboot, https://en.wikipedia.org/wiki/Coreboot
DASH: Desktop and Mobile Architecture for System Hardware https://www.dmtf.org/standards/dash :
> DASH provides support for the redirection of KVM (Keyboard, Video and Mouse) and text consoles, as well as USB and media, and supports the management of software updates, BIOS (Basic Input Output System), batteries, NIC (Network Interface Card), MAC and IP addresses, as well as DNS and DHCP configuration.
Re: DIY IP-KVM Based on Raspberry Pi
#39I'm glad projects like this exist, but I'm too lazy and more than happy to have a Pi provide a serial console and a hardware reset via GPIO over IPv6 for colocated hardware. It's much simpler ;)
I thought about building one of these, but then I just switched both of my servers to boards with IPMI
Re: DIY IP-KVM Based on Raspberry Pi
#40I like this project but the hardware seems quite overpriced at $300+. Similar for tinypilotkvm.com. In the past I've considered making and selling a cheaper version. Aside from lack of time (or motivation), one thing which discouraged me is that I would feel bad "undercutting" someone selling open hardware.
TinyPilot founder here. I understand the feedback about the price. When I created the original TinyPilot,[0] I wanted a low-priced alternative to the $600 KVM over IP options I was seeing, and now I sell my devices for $400-500/unit. The thing that's tough about selling hardware is that it seems easy to produce a few units cheaply, but creating a sustainable business for it, the costs add up. You have to fulfill orde…
I have been following the TinyPilot project on & off for a while, and I just wanted to say I appreciate your openness as well as your excellent attitude toward feedback. I think many of us (myself included) have been spoiled with various forms of free/open software and have come to expect things to be cheap or free.
But of course github stars and positive reviews won't pay our bills. So it totally makes sense to charge what you are charging for your product. You deserve it, and you're clearly putting in hard and honest work. If and when I need a KVM I will 100% be reaching for a TinyPilot.