IP Routing

What this topic solves

RIB, FIB, next-hop resolution, route preference, metrics, ECMP and forwarding decisions.

Follow state and packet path

Start with next-hop reachability, RIB/FIB and route source. Then validate protocol state, policy, metrics, attributes and convergence.

Input → classification/state → decision → table → next-hop/output → counters

Design before configuration

• Define the failure domain and expected convergence behavior.
• Document addressing, identifiers, timers, MTU and policy boundaries.
• Prefer explicit, observable state over assumptions.
• Plan rollback and out-of-band access before risky changes.

Commands and verification

Command syntax varies by platform and software release. The examples below come from the existing portal content and must be validated against the target platform documentation before production use.

# Cisco — exemplos conceituais
ip route 0.0.0.0 0.0.0.0 192.0.2.1
ip route 10.20.0.0 255.255.0.0 192.0.2.2
ip route 10.20.0.0 255.255.0.0 192.0.2.3 250

# MikroTik
/ip/route/add dst-address=0.0.0.0/0 gateway=192.0.2.1
/ip/route/print detail

# Linux
ip route
ip route get 10.20.30.40

Evidence-driven workflow

1. Define source, destination, time window and exact symptom.
2. Establish the expected healthy state and compare it with the observed state.
3. Inspect counters, tables, logs and packet captures before resets.
4. Test one hypothesis at a time and prefer reversible changes.
5. Repeat the original test after correction and check side effects.

Standards and RFCs applicable to the technology

Use the current standard/RFC and the documentation for the exact software release being operated. Vendor syntax is an implementation detail; protocol behavior should be understood independently.

Prove the behavior in a controlled topology

Build the smallest topology that reproduces the mechanism, capture control and data traffic, introduce one deliberate failure and diagnose it before applying the fix.

Related network topics