Skip to content

LMS Local Manageability Service

Jump to bottom
Andrew Mello edited this page May 26, 2026 · 1 revision

LMS — Local Manageability Service

LMS proxies the Intel ME interface (/dev/mei0) to localhost:16992 and localhost:16993, allowing WS-Man management of the local machine's AMT without going over the network.

What LMS does and doesn't proxy

Port Protocol LMS proxies?
16992 WS-Man (plaintext) Yes
16993 WS-Man (TLS) Yes
16994 AMT Redirection (cleartext) No — OOB only
16995 AMT Redirection (TLS) No — OOB only

IDER and SOL (Redirection Protocol, 16994/16995) require direct OOB network access to the AMT IP. You cannot use IDER on the same machine via LMS.

Running LMS via Docker

bash scripts/lms.sh build
bash scripts/lms.sh start
bash scripts/lms.sh stop
bash scripts/lms.sh status
bash scripts/lms.sh logs

run.sh auto-starts LMS if the image exists and /dev/mei0 is present.

After LMS is running, connect IMC to localhost instead of the AMT IP.

Requirements

  • /dev/mei0 must be accessible (Intel ME kernel module: mei_me)
  • Check: ls -la /dev/mei0 — if missing, run sudo modprobe mei_me
  • The Docker container needs device access: scripts/lms.sh mounts /dev/mei0 automatically
  • LMS binds to 127.0.0.1 only — not exposed externally

LMS Docker image

Based on Ubuntu 22.04 + pre-built lms-2550.0.0 deb from rgl/lms-binaries.

Native LMS (no Docker)

On Ubuntu/Debian:

curl -fsSL https://github.com/rgl/lms-binaries/releases/download/v0.0.20251226/lms-2550.0.0-ubuntu-22.04.deb -o lms.deb
sudo dpkg -i lms.deb && sudo apt-get install -f -y
sudo systemctl enable --now lms

On Arch (AUR): yay -S intel-lms

Clone this wiki locally