Keyboard, mouse, power
Type and point as if you sat at the server, send key combinations such as Ctrl+Alt+Del, and switch the power on, off or reset it where the BMC offers that.
Remote console · KVM over IP
> no java · no browser · no vnc bridge
Many servers that still run fine have a BMC whose console wants a Java applet or a browser from another decade. OldIPMI speaks their protocols itself and shows the screen in a Qt 6 window on your desktop.
Features
Saved connections on the left, the console on the right. Open as many as you like: each runs in its own process, and a live miniature shows what every screen is doing.
Type and point as if you sat at the server, send key combinations such as Ctrl+Alt+Del, and switch the power on, off or reset it where the BMC offers that.
Mount a read-only ISO image as the server's virtual CD-ROM, where the firmware offers virtual media, and install from it.
Passwords stay in KWallet, TLS certificates are verified. Old TLS, HTTP login and unencrypted transport are explicit exceptions, per connection.
Every connection shows its stage. A failed one says why, with a hint what to check: the address, the account, the network.
Ctrl+F filters the list; an address you type there becomes a new connection. A built-in demo console shows everything without any BMC.
GPL-3.0-or-later. A Go engine for the protocols, Qt 6 and Kirigami for the window, no vendor code inside.
Supported BMCs
Choose the console type when you add a server. On Supermicro boards, OldIPMI reads the login page first and sends exactly the form that firmware expects, so it logs in with a single attempt.
X9 to X11 and most X8 boards, Java iKVM or HTML5 console; X12/X13 through Redfish (experimental).
verified: HTML5 console
Older AMI boards such as the Supermicro X8DTU. Newer AMI/ASPEED firmware is implemented but not yet tested on hardware.
verified: X8DTU
Dell PowerEdge servers of the R420 generation. Virtual media is not available for this family yet.
verified: PowerEdge R420
Older Cisco UCS C-series servers. Their text-mode screens are not drawn yet.
verified: graphics modeVerified means real video from that hardware was decoded and checked. Keyboard input has been verified live on the ATEN HTML5 console; pointer, ISO and power so far only against test doubles and the demo console. The exact evidence for every path is in the README. Your BMC is not listed or behaves oddly? Tell us about it.
Screenshots
OldIPMI follows your desktop's light or dark colour scheme, and so do these pictures.
AI agents
OldIPMI ships oldipmi-mcp, an MCP server for AI agents such as Claude Code.
It drives the running window, so you watch everything the agent does.
From the AppImage, copy oldipmi-mcp to a stable place such as
~/.local/bin first: the settings page shows where it is. Only programs of
your own user reach it. Turn it off in Settings or start OldIPMI with
--no-agent-api.
# Settings → AI agents shows the exact path
$ claude mcp add oldipmi -- ~/.local/bin/oldipmi-mcp
# then, for example:
# "Open the console of lab-ami, go into the BIOS
# and check that it boots from the CD-ROM first."
Download
It brings its own Qt and KDE libraries. Its self-test passed on Fedora 43, Ubuntu 22.04 and 24.04 and Debian 12 and 13.
Run this in the directory with the AppImage. It checks the file against the SHA-256 above and starts OldIPMI only if the check prints OK. If it says FAILED, nothing starts: delete that file, download the AppImage again under its original name and run the command once more.
$ printf '%s %s\n' \
742ab6ba3f5e068a64f797eecb6596de93dbb4b115d025f7ee65a7281a330773 \
OldIPMI-0.4.0-x86_64.AppImage | sha256sum -c &&
chmod +x OldIPMI-0.4.0-x86_64.AppImage &&
./OldIPMI-0.4.0-x86_64.AppImage
Without FUSE, the same with one more option:
$ printf '%s %s\n' \
742ab6ba3f5e068a64f797eecb6596de93dbb4b115d025f7ee65a7281a330773 \
OldIPMI-0.4.0-x86_64.AppImage | sha256sum -c &&
chmod +x OldIPMI-0.4.0-x86_64.AppImage &&
./OldIPMI-0.4.0-x86_64.AppImage --appimage-extract-and-run
The checksum file SHA256SUMS, the list of bundled packages and all
earlier versions are on the releases
page. To build it yourself (Qt 6.6 or newer, KDE Frameworks 6, Go), follow the
README; a Fedora RPM
builds with packaging/fedora/build-rpm.sh.
Security
Kept in KWallet or only for the session. Never in profiles, logs, the window or the agent interface; the backend gets them over a private socket.
Certificates are verified. A connection the policy refuses sends no credentials, and every exception is visible on its connection.
OldIPMI changes no BMC setting, firmware, clock or TLS configuration, and never the BMC's Java or HTML5 preference.
These controllers often have flaws that will never be fixed. Keep their management ports on a separate network.
Found a vulnerability? Please report it privately on GitHub, not in a public issue.
Questions
No. It reads the BMC's Java launch file only to learn the console's address and session token, then speaks the protocol itself. No Java, JAR or vendor library is downloaded or run.
The AppImage runs on current x86_64 distributions; it brings its libraries and was tested on Fedora, Ubuntu and Debian. It feels most at home on KDE Plasma, where it also keeps passwords in KWallet.
If it is one of the four families, quite possibly. Try it with the matching console type; if it fails, the error page shows the stage and the message. A BMC report with these helps to support it.
Yes: choose the console type Demo. The demo console runs inside OldIPMI and echoes what you type and click.
No. OldIPMI is a desktop program that talks to your BMCs directly. Nothing goes through this website or any other server, and this website sets no cookies and tracks nobody.