Its job in the system
A router makes a local forwarding decision, usually selecting an outgoing interface and next hop. It does not need a complete travel itinerary written into each ordinary packet. The forwarding table reflects information learned or configured through routing mechanisms, while the fast packet-handling process applies that information to traffic.
How it works
A packet arrives on one link and is checked and processed. The router looks up a matching destination route and forwards it towards the next hop if policy and resources permit. If the outgoing link is busy, packets may wait in a queue. Queues are finite, so excessive demand can result in drops as well as delay.
Routing and forwarding are related but different. Routing determines reachability and preferred paths; forwarding sends individual packets using the resulting state. When a link fails, routing information may change and a new usable route may become available. Detection and convergence take time, so a diagram that switches paths instantly is a simplification.
A next-hop decision, not a global race
Illustrative example: a router has two possible routes to a fictional destination, and its configured policy prefers one. It forwards traffic using that choice even if a different path looks shorter on a geographic map. If reachability information changes, its choice may change after the appropriate updates. The example does not rank actual providers or calculate delay. It distinguishes the local forwarding decision from the tempting but inaccurate picture of each packet independently searching the entire world for the fastest route.
What it connects to
Routers connect access networks, provider backbones, and interconnections. They rely on link availability, power, configuration, and valid routing information. Endpoints may retransmit lost data, but retransmission cannot create a route where none exists. Network resilience therefore needs both alternate infrastructure and working control behaviour.
Different places, different designs
Large networks often have several suitable paths and may distribute traffic among them. Policy, capacity, and cost can influence route choice; it need not be the geographically shortest or lowest-latency path. Routes in the two directions can differ. The scenario uses one selected path solely to keep the change legible.
Sources & further reading
Original explanations informed by these sources. Diagrams are conceptual; local systems differ.
- RFC 1812: Requirements for IP Version 4 Routers IETF / RFC Editor; F. Baker (editor) · 1995-06 · Source & rights record
- RFC 8200: Internet Protocol, Version 6 (IPv6) Specification IETF / RFC Editor; S. Deering and R. Hinden · 2017-07 · Source & rights record
- RFC 4271: A Border Gateway Protocol 4 (BGP-4) IETF / RFC Editor; Y. Rekhter, T. Li, and S. Hares (editors) · 2006-01 · Source & rights record
- The Internet Way of Networking: Defining the critical properties of the Internet Internet Society · 2020-09-09 · Source & rights record