Sunday, 18 January 2026

Network Story

 Let me tell you a story.


When junior network engineers come to an interview and I ask a question about RIP, many reply:

“Why RIP? It’s not used anymore. Ask me something about OSPF or BGP.”

Okay. Fair enough.

So I ask a very simple follow-up:
How does BGP prevent routing loops?

Silence. Or I hear:
“Uhh… timers?”
“Because it’s Layer 3?”
“Because it’s advanced?”

None of those answers are correct.

Here’s the reality.
RIP teaches you why loops happen.
BGP expects you to already understand that.

BGP prevents loops using AS-PATH:

- Every AS appends its ASN to the path
- If a router sees its own ASN in the AS-PATH
- The route is discarded

Simple. Elegant. Fundamental.

No AS-PATH, BGP collapses.

Why I still ask about RIP?

Because RIP forces you to learn:

- Count-to-infinity
- Split horizon
- Route poisoning
- Hold-down timers

These are not “old ideas”. They are foundations.

If you skip foundations and jump straight to “advanced protocols”, you don’t become advanced. You become fragile.

Final thought:
Wanting to learn BGP before RIP is like wanting to fly a jet before learning how lift works.

Technology changes.
Network behavior doesn’t.

No comments:

Post a Comment

Why do many Palo Alto engineers open a TAC case immediately… without checking anything first?

A production issue happens. Application team says “network issue.” Users say “firewall problem.” And within minutes someone says: “Let’s ope...