Firewalls & Frustration: A Work-In-Progress
*A week of learning, unlearning, and letting it be messy.*
Every week I sit down and blog through whatever I’m learning in school, sometimes to teach it, sometimes to translate it.
This week it’s firewalls.
And if I’m being real? This one’s not clicking yet. But I’m still here, still showing up, still trying to sort the signal from the static.
---
What’s A Firewall, Anyway?
A firewall is a form of protection. It’s a barrier between trusted systems (like your home network or an internal company system) and everything else out there on the internet.
It's like a filter or a checkpoint. It looks at the traffic trying to come in (or out) and says:
- Come on in!
or
- Nope, not today!
Firewalls use rules to make those decisions. Those rules might be based on IP addresses, ports, protocols, or other criteria and they apply in both directions:
- Inbound rules control traffic coming in
- Outbound rules control traffic going out
(easy enough, right?)
That part makes sense to me. It’s the deeper stuff… the stuff beneath the rules… that starts to feel like static.
---
What’s Still Fuzzy
I can explain firewalls at a higher level, but the moment we zoom in- when the conversation shifts to data encapsulation, TCP vs. UDP, or how packets are inspected and filtered on different layers- that’s when I start to lose the thread.
Like:
- What exactly is being *inspected* in a packet?
- How does a firewall know how to treat TCP differently from UDP?
- How exactly is a packet fragmented?
- What does “deep packet inspection” actually mean?
I understand these pieces are part of the bigger picture, but they feel abstract. It’s like learning a new language and realizing you don’t know the grammar, just a few words.
---
The Analogy That’s Helping Me (Sort Of)
Right now, I’m thinking of firewalls as security guards.
Like a bouncer at a club, but one that’s reading a list, checking for hidden weapons, listening to how loudly you’re talking, watching where you go after you’re inside, and also monitoring who leaves and whether they’re carrying sensitive data with them.
And doing that for every request, all the time.
No wonder firewalls are complex- they’re not just barriers, they’re intelligent filters. Which means whoever sets the rules better know exactly what they’re doing.
It also means I’ll need to understand more of what those rules are built on.
---
Letting Myself Not Get It (Yet)
This week’s lesson for me isn’t just firewalls.
It’s patience.
It’s letting myself learn in layers.
It’s okay to not understand everything the first time. Or the second. Or the fifth.
Sometimes learning tech is less about memorizing terms and more about showing up over and over, even when it’s frustrating. Even when you feel behind. Even when your brain is tired and your notebook is full of question marks.
---
Final Thought
Firewalls are there to protect systems.
But learning something new? That needs protection too.
So this week, I’m treating my confusion with a little more grace.
I’m keeping the door open to learning and building my own rules, one layer at a time.
---
If you’ve ever struggled with firewalls (or any tech concept that didn’t click right away), I’d love to hear what helped you through it. Send a cipher or just share what you’re learning too. We’re all decoding something.
