Read a sample: 1. Reading a Network Service Configuration
A router configuration is more than a list of commands. It is a description of how a device is expected to participate in a network: which interfaces connect to which segments, what addresses those interfaces use, and which services or forwarding rules apply.
The challenge is that the configuration usually does not tell the whole story in one place. A command under an interface may depend on a device-wide setting. An address in a service configuration may belong to a server shown only in a topology. A correct-looking setting may be attached to the wrong interface.
This chapter establishes a reading method you can use throughout the book. You will connect a text-based topology to an address table, match configuration commands to devices and interfaces, and trace a packet across a small routed network. The goal is not to memorize every command. It is to learn to ask, “Where does this setting belong, and what does it tell me about the path?”
Consider a small office network with one client, one router, and one server.
text
PC1 R1 Server1
192.168.10.10/24 G0/0 G0/1 192.168.20.20/24
| 192.168.10.1 192.168.20.1 |
+---- LAN 10 ------+ +---- LAN 20 ----+
Read the diagram from left to right, but do not assume that every future packet must travel in that direction. The diagram shows connections, not a required traffic flow.
PC1 is on LAN 10. Its address is 192.168.10.10/24. Router R1 connects to that LAN through interface G0/0, which has address 192.168.10.1/24.
R1 also connects to LAN 20 through G0/1, which has address 192.168.20.1/24. Server1 is on LAN 20 at 192.168.20.20/24.
The /24 prefix indicates that the first 24 bits identify the network portion of each address. In this example, LAN 10 uses network 192.168.10.0/24, and LAN 20 uses network 192.168.20.0/24. They are different IP subnets, even though both connect to the same router.
The labels G0/0 and G0/1 are shortened interface names. A configuration might spell them out as GigabitEthernet0/0 and GigabitEthernet0/1. Interface naming varies by platform, so treat the labels in each example as the authoritative names for that example.
A line in a text diagram represents a connection or network segment. It does not necessarily show every physical component. LAN 10 and LAN 20 might each include a switch, but the switches are omitted here because they are not needed to follow the IP path.
A topology makes relationships visible. An address table makes individual details easier to check.
For a host, the default gateway is the router address used when the host needs to send traffic outside its own subnet. PC1 uses R1’s LAN 10 address, 192.168.10.1. Server1 uses R1’s LAN 20 address, 192.168.20.1.
The router rows say “Not applicable” in the default-gateway column because this table records the hosts’ default gateways, not the router’s complete forwarding information. Routers make forwarding decisions using their routing tables. In this particular topology, both displayed networks are directly connected to R1.
When reading an address table, check three relationships:
1. Host to subnet: Does the host address belong to the subnet shown for its LAN?
2. Host to gateway: Is the host’s gateway on the same subnet as the host?
3. Gateway to interface: Does that gateway address actually appear on the router interface connected to the host’s LAN?
For PC1, the answers are yes: 192.168.10.10 and 192.168.10.1 are in 192.168.10.0/24, and 192.168.10.1 belongs to R1’s G0/0, the interface facing PC1.
The last check matters. An address can be in the correct subnet on paper but still be assigned to the wrong device or interface in a faulty scenario.
Now compare the topology and table with this configuration excerpt from R1:
text
hostname R1
!
interface GigabitEthernet0/0
description LAN 10 - client network
ip address 192.168.10.1 255.255.255.0
no shutdown
!
interface GigabitEthernet0/1
description LAN 20 - server network
ip address 192.168.20.1 255.255.255.0
no shutdown
The first line identifies the device as R1. The two interface lines introduce interface configuration sections. The indented commands following each interface line apply to that interface until the configuration moves to another section.
For GigabitEthernet0/0:
- description provides a human-readable label. It helps a technician understand the intended connection; it does not assign an address or establish connectivity.
- ip address assigns 192.168.10.1 with mask 255.255.255.0, equivalent to /24.
- no shutdown enables the interface administratively. The interface must still have the necessary physical and protocol conditions to operate.
The same pattern applies to GigabitEthernet0/1, using the LAN 20 address.
The exclamation marks are visual separators in this display. They help divide sections; they are not interface names or packet-processing steps.
The most useful habit here is to identify scope before interpreting a command. The line ip address 192.168.10.1 255.255.255.0 is not merely a router address. In this excerpt, it is the address configured on R1’s GigabitEthernet0/0. That interface is the connection to LAN 10.
Likewise, a command shown elsewhere in a configuration may apply to the router as a whole, to a named service pool, or to a particular interface. Its location is part of its meaning.
Suppose PC1 sends an IP packet to Server1. For this first trace, assume both hosts have the addresses and gateways in the table, R1’s interfaces are operational, and no filtering prevents the traffic.
PC1 compares the destination, 192.168.20.20, with its own subnet, 192.168.10.0/24. The destination is outside that subnet, so PC1 sends the packet toward its default gateway, 192.168.10.1.
The packet’s IP…