Topic lessonTopic: networking foundations
IPv4 next hops: direct delivery and Ethernet frames across a router
A next hop is the neighbor to which a packet is delivered next. For an on-link destination, that neighbor can be the destination itself. For a destination on another link, the selected route may first send the packet to a router. Compare these cases using a specified IPv4 and Ethernet configuration.
Use a route note and topology to explain the next recipient and frame destination for direct and routed delivery.
An IP address specifies a network-layer destination; a MAC address is used on an Ethernet link. A frame is a unit delivered on that link. Review the lesson on names, IP addresses, MAC addresses and ports. These are fixed fictional values, with no configuration, commands or connections.
Identify the links, interfaces and supplied routes
A link supports direct delivery to a neighbor. It is distinct from a subnet address range or a device enclosure. This example has one router with two interfaces, one attached to each of two links.
| Interface | IPv4 | MAC | Link |
|---|---|---|---|
| Host A | 192.0.2.10/24 | 00:00:5e:00:53:10 | Link 1 |
| Host B | 192.0.2.20/24 | 00:00:5e:00:53:20 | Link 1 |
| Router, Link 1 interface | 192.0.2.1/24 | 00:00:5e:00:53:01 | Link 1 |
| Router, Link 2 interface | 198.51.100.1/24 | 00:00:5e:00:53:02 | Link 2 |
| Host C | 198.51.100.20/24 | 00:00:5e:00:53:30 | Link 2 |
Host A has an on-link route for 192.0.2.0/24 and a route to 198.51.100.0/24 via 192.0.2.1 on Link 1. The router has an on-link route to 198.51.100.0/24 on Link 2. Assume no competing routes or other selection rules for these two destinations. The CIDR lesson covers prefix arithmetic.
- Host A → Host B: Link 1Link 1: directly to B
- Host A → Router: two interfacesLink 1: to router interface L1
- Router: two interfaces → Host C: Link 2Link 2: interface L2 to C
- Host A
- 192.0.2.10 / MAC …:53:10
- Host B: Link 1
- 192.0.2.20 / MAC …:53:20
- Router: two interfaces
- L1 192.0.2.1 / L2 198.51.100.1
- Host C: Link 2
- 198.51.100.20 / MAC …:53:30
Deliver directly to B on the same link
To send from A to B at 192.0.2.20, the supplied route selects direct delivery on Link 1. The next-hop IP is also B’s 192.0.2.20. With B’s address mapping known, the frame destination is 00:00:5e:00:53:20.
Read destination fields separately on the two links to C
When A sends to C at 198.51.100.20, its first neighbor is 192.0.2.1, selected by the route. The frame on Link 1 goes to the router’s Link 1 MAC. The IP destination is C.
When the router forwards to C, it uses its Link 2 interface. That frame has the router’s Link 2 MAC as its source and C’s MAC as its destination. The destination in the first Ethernet frame is not one address used throughout the whole route.
- Link 1: A to router → Link 2: router to CForwarding uses a different frame on the outgoing link
- Link 1: A to router
- MAC …:53:10 → …:53:01 / IP dst 198.51.100.20
- Link 2: router to C
- MAC …:53:02 → …:53:30 / IP dst 198.51.100.20
| Delivery segment | Source MAC | Destination MAC | IP destination |
|---|---|---|---|
| A → B: direct on Link 1 | …:53:10 | …:53:20 | 192.0.2.20 |
| A → router: Link 1 | …:53:10 | …:53:01 | 198.51.100.20 |
| Router → C: Link 2 | …:53:02 | …:53:30 | 198.51.100.20 |
Tables and diagrams omit the shared 00:00:5e:00 MAC prefix. Match each suffix to the full interface table. The shortened notation does not denote a different address.
Separate next-hop selection from address resolution
In this IPv4/Ethernet example, routing determines the next neighbor, and delivery uses that neighbor’s Ethernet address. ARP resolves this mapping. A cached mapping can be reused; a new ARP request is not necessary for every packet.
IPv6 uses Neighbor Discovery for neighbor link-layer address resolution. ND also covers router discovery and neighbor reachability; it is more than IPv4 ARP with another name.
A forward-path diagram does not establish a reply or web response
The diagrams explain the next recipient for a specified destination. Replies from C to A need their own routing and traffic-control conditions. A neighbor address mapping also does not establish a successful HTTP response or user authentication.
List the source and destination → selected route → next neighbor’s interface → frame destination on that link. Use separate evidence for the reply and application state.
Read the next recipient in three situations
Choose an option to see the result and explanation.
Check, then explain in your own words
- Explain the supplied route and next hop for A → B and A → C.
- Match router interfaces L1 and L2 to the interface table.
- Read source and destination MAC fields separately from the IP destination in the two frames to C.
Check your understanding: How do you read the IP destination separately from frame destinations on the way to one target?
Separate the final IP destination from the next recipient on each link.
B is its own next hop for direct delivery in this example. On the way to C, Link 1 delivers to router interface L1, and Link 2 carries a frame from interface L2 to C. Retain the conditions; a forward-path explanation does not establish a reply or application success.
Sources and conditions checked
Primary references are collected here with their scope, conditions and corresponding sections. Independent expert review and live-environment validation have not been performed.
Scope and conditionsSections 3.3.1.1/3.3.1.2: direct and gateway delivery for IPv4. The example supplies routes; no historical address-discovery procedure or universal current-OS implementation is claimed.
Used in this lessonIdentify the links, interfaces and supplied routes Deliver directly to B on the same link Read destination fields separately on the two links to C
Scope and conditionsSection 5.2.1.2 and the introduction to 5.2.4 plus 5.2.4.1/2: next hop, outgoing interface and link-layer delivery. Routes are supplied; not a complete route-selection, policy or device validation.
Used in this lessonIdentify the links, interfaces and supplied routes Read destination fields separately on the two links to C
Scope and conditionsPacket Generation: selected next hop, Ethernet address resolution and cache; no routing algorithm or OS procedure.
Used in this lessonDeliver directly to B on the same link Read destination fields separately on the two links to C Separate next-hop selection from address resolution
Scope and conditionsSection 5.2: conceptual separation of next-hop determination and neighbor information. Update and errata screening is separately scoped; no full message, timer or security validation.
Used in this lessonIdentify the links, interfaces and supplied routes Separate next-hop selection from address resolution
Scope and conditionsSections 4/6: assigning an IPv6 address does not itself establish a corresponding on-link prefix. Device configuration and live IPv6 traffic were not validated.
Used in this lessonSeparate next-hop selection from address resolution
Scope and conditionsSections 3/4: documentation blocks, including 192.0.2.0/24; not live targets or local configuration.
Used in this lessonIdentify the links, interfaces and supplied routes
Scope and conditionsSection 2.1.4: documentation unicast MAC range 00:00:5e:00:53:00–ff, checked in the text that obsoletes RFC7042.
Used in this lessonIdentify the links, interfaces and supplied routes