[cerberusss]

Fantastic project. Amazing how you overcame each obstacle, and very well written to boot. Kudos.

Quite funny how you brought 1000 ms latency down to 200 ms. I wonder how this compares to iDRAC and that Raritan device.

[mtlynch]

Thanks for reading!

Yeah, it was kind of like the perfect difficulty level for this kind of project. If it was two months of work to get it working at all, I probably would have gotten discouraged, but it worked out that every couple weeks I was rewarded with a breakthrough that substantially improved the latency until it was finally a practical tool.

[cm2187]

I don’t know about iDRAC but I used raritan a bit for some home projects and it’s not super fun. I couldn’t connect it on HDMI when the server was already running, it had to be connected before the boot. For both VGA and HDMI, it sort of works, there is a clunky but functional java desktop application, the screen is often off by a dozen pixels (part of the screen hidden) and the pointer too.

For new servers, I just buy a supermicro motherboard with IPMI and stop worrying. You can set up an IP based firewall within IPMI, so that only a handful of IPs can even connect, plus a very strong password, and I am not too worried about exposing it to the WAN (I know it’s not a great idea but I don’t know any alternative that doesn’t require another U in a datacentre)..

[EvanAnderson]

I've used virtually all of the iDRACs. They're probably in that 200ms area (based on my gut feeling w/ no empirical measurements). They've been fairly responsive in my experience.

[Bnshsysjab]

Out of curiosity do they bring any functionality that this device does not?

[tinco]

I manage a machine that has an AST2500 (competitor to iDRAC in smaller vendors like Gigabyte, it rocks), and I didn't notice latency, so it's probably under 200ms.

[numpad0]

Most iDRAC type products actually use that same Aspeed ASTxxxx with vendor firmwares. If a server reports "Matrox G200e" as display adapter it's it.