Port 654Ad hoc On-Demand Distance Vector (AODV)

AODV uses port 654 for on-demand route discovery and maintenance in mobile ad hoc IP networks.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 994 of 3,454 · top 29%

also known as aodv, RFC 3561

1 other service is registered on port 654. compare all 2

Technical Details

what runs on :654

AODV is defined by RFC 3561 and normally sends routing messages over UDP port 654; although the registry lists both TCP and UDP, TCP is not used for normal AODV operation. Route Requests (RREQ), Route Replies (RREP), Route Errors (RERR), and optional HELLO messages support on-demand discovery and maintenance of hop-by-hop routes. AODV has no conventional connection handshake or encryption layer, and its messages use protocol-defined binary fields rather than an application stream framing protocol.

Security Information

exposure of :654

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

network services averages 2.7 across 1,193 ports — this one sits 0.7 below.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

AODV assumes a trusted or otherwise protected ad hoc routing environment. An exposed implementation can be targeted with forged route messages, route disruption, blackhole or sinkhole behavior, and resource-exhaustion traffic; it should generally be restricted to the intended ad hoc or mesh interfaces and never exposed broadly to the public Internet.

the 8 most looked-up other ports in network services — 1,193 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted