2 entries are registered on port 654. It is a well-known port (0–1023) — assignments here are IANA's, and a service found on one is usually the service that was assigned it.
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :654 | Media Management Protocol | TCP | Network Services | caution | 10.2k |
| :654 | Ad hoc On-Demand Distance Vector (AODV) | TCPUDP | Network Services | safe | 0 |
Media Management Protocol (MMP) on port 654 facilitates the management, control, and distribution of media content across networked environments. It enables communication between media servers and clients, supporting a range of commands and functions to organize, retrieve, and deliver audio, video, and related content efficiently within media management systems.
port 654 as Media Management Protocol →AODV uses port 654 for on-demand route discovery and maintenance in mobile ad hoc IP networks.
port 654 as Ad hoc On-Demand Distance Vector (AODV) →The registry says what 654 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.
ss -ltnp | grep ':654\b'lsof -nP -iTCP:654 -sTCP:LISTENnetstat -ano | findstr :654On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 2 entries above.
A port number is not a service. Anything may listen on 654 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.
contribute an entry