What Runs on Port 1132
Port 1132 is officially registered with IANA for KVM-via-IP management.1 KVM stands for Keyboard, Video, Mouse—the three things you need to control a computer. KVM-via-IP extends that control over a network, letting you manage remote servers as if your keyboard and mouse were plugged directly into them.
When a server freezes at the BIOS level, SSH won't help you—the operating system isn't even running yet. Port 1132 carries the protocol that gives you access before the OS loads, during boot, and even when everything has crashed.
How It Works
Traditional KVM switches were physical boxes with cables running to multiple servers. You'd flip a switch to control different machines from one console. KVM-via-IP does the same thing over the network.
The KVM-via-IP device sits between the server and the network. It captures the video output, intercepts keyboard input, and translates mouse movements. Everything flows through port 1132 to your management console. You see exactly what the server's monitor shows. You type, and the server receives those keystrokes as if you were physically there.
This works at the hardware level—below the operating system, below the network stack. Even if the server kernel panics or the network drivers crash, port 1132 still works because it's talking to the hardware directly.
Why Port 1132 Exists
Before KVM-over-IP, a crashed server meant someone had to physically go to the machine. At 3am. In a data center. To press Ctrl+Alt+Delete or watch the boot sequence scroll by.
Port 1132 exists because that's an absurd way to run infrastructure. It's the reason you can:
- Reboot a frozen server from home
- Watch BIOS messages during startup without driving to the data center
- Install an operating system on a machine in another city
- Recover from boot failures without "hands-on-keyboard"
The protocol solves the most frustrating problem in server management: the machine is broken in a way that makes it unreachable through normal channels, and you need to see what it sees.
The Registered Ports Range
Port 1132 lives in the registered ports range (1024-49151). These ports are assigned by IANA to specific services when someone requests them. They're not as universally recognized as well-known ports (0-1023), but they're still officially designated.
The KVM-via-IP protocol was important enough that someone filed the paperwork to get port 1132 reserved. It means when you see traffic on 1132, there's a good chance it's KVM management—not random application chatter.
Security Considerations
Port 1132 is dangerous if exposed to the Internet. It provides physical-level access to servers—everything an attacker sitting at the keyboard could do, they can do through this port.
KVM-via-IP sessions should be:
- Restricted to management networks, never public-facing
- Protected with strong authentication
- Encrypted (many implementations use their own encryption or tunnel through VPNs)
- Logged and monitored
If you find port 1132 open on a public IP address, that's a misconfiguration. This port belongs behind firewalls, accessible only to administrators who need it.
Checking What's Listening
To see if anything is listening on port 1132:
On Linux/Mac:
On Windows:
If you find something listening and don't know why, check whether you have KVM-over-IP hardware on your network. Not all KVM implementations use port 1132—some vendors use proprietary ports—but it's the officially registered choice.
Related Ports
- Port 443 (HTTPS): Many modern KVM-over-IP devices use web interfaces on 443 instead of dedicated protocols on 1132
- Port 5900 (VNC): Another remote desktop protocol, but operates at the OS level rather than hardware level
- Port 3389 (RDP): Microsoft's remote desktop protocol, also OS-level
The difference: VNC and RDP require the operating system to be running. Port 1132's KVM-via-IP works whether the OS is alive or dead.
Frequently Asked Questions About Port 1132
Was deze pagina nuttig?