Gutenberg Articles

Appearance

Excerpt ​

Excerpt from Hitchhiker's Guide to the Internet, by Ed Krol

  The ROUTED program, which does RIP for 4.2BSD systems,<br />
  has many options. One of the most frequently used is:<br />
  "routed -q" (quiet mode) which means listen to RIP infor-<br />
  mation but never broadcast it.  This would be used by a<br />
  machine on a network with multiple RIP speaking gate-<br />
  ways.  It allows the host to determine which gateway is<br />
  best (hopwise) to use to reach a distant network.  (Of<br />
  course you might want to have a default gateway to<br />
  prevent having to pass all the addresses known to the<br />
  Internet around with RIP).

  There are two ways to insert static routes into "routed",<br />
  the "/etc/gateways" file and the "route add" command.<br />
  Static routes are useful if you know how to reach a<br />
  distant network, but you are not receiving that route<br />
  using RIP.  For the most part the "route add" command is<br />
  preferable to use.  The reason for this is that the<br />
  command adds the route to that machine's routing table<br />
  but does not export it through RIP.  The "/etc/gateways"<br />
  file takes precedence over any routing information<br />
  received through a RIP update.  It is also broadcast as<br />
  fact in RIP updates produced by the host without question,<br />
  so if a mistake is made in the "/etc/gateways" file,<br />
  that mistake will soon permeate the RIP space and<br />
  may bring the network to its knees.

  One of the problems with "routed" is that you have very<br />
  little control over what gets broadcast and what<br />
  doesn't.  Many times in larger networks where various<br />
  parts of the network are under different administrative<br />
  controls, you would like to pass on through RIP only nets<br />
  which you receive from RIP and you know are reasonable.<br />
  This prevents people from adding IP addresses to<br />
  the network which may be illegal and you being<br />
  responsible for passing them on to the Internet.  This

Explanation ​

This excerpt from The Hitchhiker’s Guide to the Internet (1987) by Ed Krol is a technical yet accessible explanation of how the ROUTED program (a Unix daemon implementing the Routing Information Protocol, or RIP) functions in 4.2BSD (Berkeley Software Distribution) systems. The text blends practical networking advice with subtle critiques of RIP’s limitations, reflecting the early Internet’s decentralized, experimental nature. Below is a detailed breakdown of the passage, focusing on its content, themes, literary style, and significance—with an emphasis on the text itself.

1. Context & Source ​

  • Book Context: The Hitchhiker’s Guide to the Internet (a play on The Hitchhiker’s Guide to the Galaxy) was one of the first user-friendly introductions to the Internet, written for a non-expert audience. Krol’s guide demystified TCP/IP, email, and routing at a time when the Internet was transitioning from academic/military use to broader adoption.
  • Technical Context: The excerpt discusses RIP (Routing Information Protocol), an early distance-vector routing protocol used to dynamically exchange routing tables between gateways (routers). RIP was simple but flawed—prone to slow convergence, routing loops, and misinformation propagation (issues hinted at in the text).

2. Themes & Key Ideas ​

A. Control vs. Automation in Networking ​

The passage explores the tension between automated routing (RIP) and manual control (static routes):

  • RIP’s "Chattiness": By default, routed broadcasts and listens to RIP updates, which can flood networks with redundant or incorrect data. The -q ("quiet") flag lets a host passively listen without contributing to the noise—a nod to the need for selective participation in distributed systems.
  • Static Routes as Safeguards: The text warns that while RIP automates routing, it lacks granular control. Static routes (/etc/gateways or route add) allow administrators to override dynamic updates, but with risks:
    • /etc/gateways is authoritative and propagates unconditionally, meaning errors can "bring the network to its knees" (a vivid metaphor for cascading failure).
    • route add is local and silent, avoiding RIP’s broadcast storms.

B. Trust and Responsibility in Decentralized Networks ​

Krol highlights a social-technical problem:

  • RIP assumes trust in routing updates, but in "larger networks under different administrative controls," this is dangerous. A misconfigured or malicious gateway could inject illegal IP addresses, and RIP would blindly propagate them.
  • The text implies that RIP lacks accountability mechanisms—a critique of early Internet protocols that prioritized simplicity over security. This foreshadows later developments like BGP (Border Gateway Protocol), which includes policies to filter routes.

C. Practicality vs. Idealism ​

The parenthetical remark—"(Of course you might want to have a default gateway..."—reveals a pragmatic workaround for RIP’s inefficiency. Instead of broadcasting every known route (scaling poorly), administrators could use a default gateway (a "catch-all" route), sacrificing precision for simplicity. This reflects the ad-hoc nature of early Internet engineering.

3. Literary Devices & Style ​

Krol’s writing is technical yet conversational, using:

  • Analogies/Metaphors:
    • "Bring the network to its knees" → Evokes collapse under misinformation, emphasizing RIP’s fragility.
    • "Passing on... nets which you know are reasonable" → Frames routing as a social contract, not just a technical process.
  • Parenthetical Asides:
    • "(Of course you might want to have a default gateway...)" → Mimics an oral explanation, as if Krol is speaking directly to a sysadmin. This mirrors the book’s tutorial tone.
  • Understatement:
    • "One of the problems with 'routed' is that you have very little control..." → Downplays a critical flaw, letting the reader infer the severity.
  • Imperative Mood:
    • "You would like to pass on through RIP only nets which you receive from RIP..." → Directs the reader’s attention to a desired but unavailable feature, subtly critiquing RIP’s design.

4. Significance of the Passage ​

A. Historical snapshot of Internet growth ​

  • The text captures the transition from small, trusted networks (e.g., ARPANET) to larger, heterogeneous ones. RIP worked fine in academic labs but struggled with scale and untrusted actors—a microcosm of the Internet’s growing pains.
  • The warning about "illegal IP addresses" hints at early concerns about security and governance, presaging modern issues like BGP hijacking.

B. Pedagogical Value ​

Krol’s explanation is accessible without oversimplifying. He:

  1. Describes how RIP works (-q flag, static routes).
  2. Critiques its limitations (lack of control, trust assumptions).
  3. Offers workarounds (default gateways, route add). This structure mirrors the problem-solution pattern common in technical writing.

C. Foreshadowing Modern Networking ​

  • The problems Krol identifies (misinformation propagation, lack of route filtering) led to:
    • BGP’s policy-based routing (1990s).
    • Firewalls and access control lists (to block illegal routes).
    • Zero-trust networking (assuming no implicit trust).

5. Line-by-Line Analysis of Key Sections ​

Section 1: routed -q (Quiet Mode) ​

"listen to RIP information but never broadcast it... allows the host to determine which gateway is best (hopwise)"

  • Purpose: Avoids contributing to routing table bloat (a common RIP issue).
  • Implication: Even in 1987, passive observation was a tool for debugging or conserving bandwidth.
  • "Hopwise": Refers to RIP’s metric (number of hops to a destination), a simple but flawed way to measure route quality.

Section 2: Static Routes (/etc/gateways vs. route add) ​

"The '/etc/gateways' file... is also broadcast as fact in RIP updates produced by the host without question"

  • Key Idea: /etc/gateways is dogmatic—it overrides RIP and propagates unconditionally.
  • Risk: A typo could corrupt routing tables across the network, showing how centralized configuration files can become single points of failure.
  • Contrast: route add is local and silent, reflecting a defensive programming mindset.

Section 3: Administrative Boundaries ​

"larger networks where various parts... are under different administrative controls"

  • Problem: RIP has no authentication or validation. If one admin misconfigures a route, others inherit the problem.
  • Modern Parallel: Similar to how DNS cache poisoning or BGP leaks can have global effects today.

6. Why This Matters Today ​

While RIP is now obsolete (replaced by OSPF and BGP), the excerpt’s themes remain relevant:

  • Decentralization vs. Control: Blockchain and federated systems face similar trade-offs.
  • Trust in Automated Systems: AI/ML models propagate biases like RIP propagates bad routes.
  • Workarounds as Innovation: The default gateway hack mirrors how cloud networking uses "0.0.0.0/0" routes today.

7. Conclusion: The Text as a Microcosm ​

Krol’s passage is more than a manual—it’s a case study in early Internet culture:

  • Collaborative yet cautious: Trust is assumed but must be managed.
  • Pragmatic: Workarounds (like default gateways) bridge gaps in technology.
  • Forward-looking: The critiques of RIP anticipate modern networking challenges.

The literary craft—blending dry technical detail with wry asides—makes it engaging while preserving precision. It’s a reminder that even in engineering texts, clarity and context matter as much as correctness.

Final Thought: If The Hitchhiker’s Guide to the Galaxy taught us that the answer to life is "42," Krol’s Hitchhiker’s Guide to the Internet might say the answer to networking is "It depends"—and this excerpt shows why.

Questions ​

Question 1 ​

The passage’s discussion of the /etc/gateways file and the route add command serves primarily to illustrate which of the following tensions in early network administration?

A. The conflict between open-source ideals and proprietary networking solutions
B. The trade-off between centralized control and the risks of unchecked propagation
C. The debate over whether manual configuration is inherently superior to automated routing
D. The ethical dilemma of prioritizing network speed over data integrity
E. The technical limitations of 4.2BSD systems compared to modern Unix distributions

Question 2 ​

The parenthetical remark—"(Of course you might want to have a default gateway..."—functions rhetorically to:

A. Undermine the credibility of RIP as a viable routing protocol
B. Introduce a tangential topic that distracts from the main argument
C. Highlight the author’s personal preference for static over dynamic routing
D. Signal the passage’s shift from technical explanation to normative advice
E. Acknowledge a pragmatic workaround for a systemic limitation

Question 3 ​

Which of the following best describes the implicit critique embedded in the statement, "This prevents people from adding IP addresses to the network which may be illegal and you being responsible for passing them on to the Internet"?

A. A warning about the lack of accountability mechanisms in decentralized protocols
B. An argument for the necessity of government regulation in network administration
C. A defense of RIP’s design as inherently resistant to malicious actors
D. An example of how early Internet culture prioritized innovation over legality
E. A call for the adoption of cryptographic verification in routing updates

Question 4 ​

The metaphor "bring the network to its knees" is most effective in conveying which of the following ideas?

A. The physical infrastructure of early networks was unusually fragile
B. RIP’s design flaws were primarily a result of hardware limitations
C. A single misconfiguration could have cascading, system-wide consequences
D. Network administrators were often overwhelmed by the complexity of routing tables
E. The Internet’s growth was inevitably stymied by the limitations of distance-vector protocols

Question 5 ​

The passage’s structure—moving from a description of routed -q to static routes to the risks of unfiltered RIP updates—is best understood as an example of:

A. Problem-solution reasoning, where each section introduces a flaw and a partial remedy
B. Chronological progression, mirroring the historical development of routing protocols
C. Deductive logic, deriving specific warnings from general principles of network design
D. Comparative analysis, juxtaposing RIP with more advanced protocols like OSPF
E. Persuasive rhetoric, building an argument for the obsolescence of distance-vector routing

Solutions and Explanations ​

1) Correct answer: B ​

Why B is most correct: The passage contrasts the /etc/gateways file (centralized, authoritative, and propagative) with the route add command (local, silent, and non-propagative). This juxtaposition highlights the tension between centralized control and the risks of unchecked propagation: while /etc/gateways offers administrative power, it also introduces systemic vulnerability ("that mistake will soon permeate the RIP space"). The route add command, meanwhile, sacrifices some control for safety. This aligns with B’s focus on the trade-offs inherent in delegation vs. containment.

Why the distractors are less supported:

  • A: The passage does not address open-source vs. proprietary debates; it focuses on technical trade-offs within a single system (4.2BSD).
  • C: The text does not argue for the inherent superiority of manual configuration; it merely notes the risks of automated propagation and the utility of manual overrides in specific cases.
  • D: The "ethical dilemma" of speed vs. integrity is not the core tension; the passage is more concerned with practical risks (e.g., misconfiguration) than moral trade-offs.
  • E: The comparison is not about 4.2BSD’s limitations relative to modern systems but about the design choices within RIP itself.

2) Correct answer: E ​

Why E is most correct: The parenthetical remark introduces a pragmatic workaround ("default gateway") for RIP’s inefficiency (passing "all the addresses known to the Internet"). This acknowledges that while RIP’s design is flawed, administrators can mitigate its drawbacks with ad-hoc solutions. The tone is concessive and practical, not dismissive or prescriptive, which aligns with E’s framing of a "workaround for a systemic limitation."

Why the distractors are less supported:

  • A: The remark does not undermine RIP’s credibility; it accommodates its flaws.
  • B: The aside is directly relevant to the discussion of RIP’s limitations; it is not tangential.
  • C: The author does not express a personal preference for static routing; the focus is on RIP’s operational challenges.
  • D: The passage does not shift to normative advice; it remains descriptive, offering a practical (not moral) suggestion.

3) Correct answer: A ​

Why A is most correct: The statement warns that RIP’s lack of validation mechanisms could make an administrator unwittingly complicit in propagating "illegal" IP addresses. This critiques the absence of accountability in decentralized protocols like RIP, where no entity verifies the legitimacy of routing updates. The emphasis on "you being responsible" underscores the lack of safeguards in a trust-based system.

Why the distractors are less supported:

  • B: The passage does not argue for government regulation; it highlights a technical vulnerability, not a policy gap.
  • C: The text does not defend RIP’s design; it exposes its risks.
  • D: While early Internet culture did prioritize innovation, the passage focuses on the consequences of this prioritization (e.g., illegal addresses), not the cultural values themselves.
  • E: Cryptographic verification is not mentioned; the critique is about RIP’s lack of filtering, not encryption.

4) Correct answer: C ​

Why C is most correct: The metaphor "bring the network to its knees" conveys the systemic fragility introduced by a single misconfiguration in /etc/gateways. The image of a network "collapsing" under the weight of propagated errors emphasizes the cascading effects of RIP’s unchecked broadcast mechanism. This aligns with C’s focus on system-wide consequences from a localized mistake.

Why the distractors are less supported:

  • A: The fragility is not about physical infrastructure but the logical propagation of errors.
  • B: The passage does not attribute RIP’s flaws to hardware; the issue is protocol design.
  • D: The metaphor does not describe administrators being "overwhelmed"; it describes the network’s failure.
  • E: The text does not claim RIP inevitably stymied Internet growth; it notes a specific, remediable flaw.

5) Correct answer: A ​

Why A is most correct: The passage follows a problem-solution structure:

  1. Problem: routed’s default behavior (broadcasting RIP updates) is noisy and risky (Section 1).
  2. Partial solution: routed -q (quiet mode) lets hosts listen without broadcasting (Section 1).
  3. Problem: Static routes are needed for unreachable networks, but /etc/gateways propagates errors (Section 2).
  4. Partial solution: route add avoids propagation but is local-only (Section 2).
  5. Problem: RIP lacks control over broadcasts, risking illegal addresses (Section 3). This mirrors A’s "problem-solution reasoning," where each section introduces a flaw and a mitigating (but imperfect) remedy.

Why the distractors are less supported:

  • B: The structure is not chronological; it is logical, addressing interrelated technical issues.
  • C: The passage does not derive warnings from general principles; it moves from specific problems to specific workarounds.
  • D: OSPF is not mentioned; the focus is on RIP’s internal trade-offs, not comparisons.
  • E: The text is not persuasive; it is analytical, describing limitations without advocating for RIP’s obsolescence.