What is the difference between a next-hop static route, a directly connected static route, and a fully specified static route in the routing table?

Next-hop shows "via IP (Internet Protocol)". Directly connected shows "is directly connected, interface". Fully specified shows "via IP, interface". The routing table presentation differs because the router resolves each type differently.

How each type appears in show ip route:

Next-hop route:

R1(config)# ip route 172.16.1.0 255.255.255.0 172.16.2.2
→ S    172.16.1.0/24 [1/0] via 172.16.2.2

• Shows the next-hop IP only
• Router must do a recursive lookup to find which interface reaches 172.16.2.2

Directly connected static route:

R1(config)# ip route 172.16.1.0 255.255.255.0 Serial0/1/0
→ S    172.16.1.0/24 is directly connected, Serial0/1/0

• Looks like a connected route but with code "S"
• No recursive lookup — router sends directly out the specified interface
• For Ethernet: router ARPs (Address Resolution Protocol) for the destination IP (not next-hop) — creates excessive ARP traffic

Fully specified route:

R1(config)# ip route 172.16.1.0 255.255.255.0 GigabitEthernet0/1 172.16.2.2
→ S    172.16.1.0/24 [1/0] via 172.16.2.2, GigabitEthernet0/1

• Shows both next-hop AND exit interface
• No recursive lookup needed, ARPs for the next-hop (correct behavior)
• Best choice for Ethernet interfaces

Decision guide:

Go deeper:

• Proxy ARP (Wikipedia) — the per-destination ARP issue on Ethernet that explains why directly-connected static routes misbehave there.