show_ip_int_brief retweeted
TODAY, I PASSED MY CCNA 200-301! 😭🎉 The late nights, countless labs, subnetting struggles, self doubt, and resilience. It all paid off! ❤️From joining @thenetclan Cohort 3 to receiving a CCNA voucher, I’m incredibly grateful to @AbbyJefia for making this dream possible.
#CCNA
show_ip_int_brief retweeted
Lining up some giveaways from @certtap for the holidays. Will be giving away exam vouchers for the following:
- Security+
- Network+
- CCNA
Will also be giving away much more.
If anyone or organizations want to contribute and give back to the community, just reach out.
show_ip_int_brief retweeted
I PASSED MY CCNA! 🎉🥹
I'm grateful to @thenetclan founders, @AbbyJefia and @OnijeC, my instructors, my mentors, and my sisters @BlessingDe73515, @Nne__Nna and @leey_mah.
Thank you for the support, lessons and encouragement. We did it! 💜
show_ip_int_brief retweeted
Day 53/100 of learning Web3 Security.
Today was mentally exhausting and I felt completely drained, but I forced myself to stay on track. Let this be a reminder: never give up, no matter how tired you are. Consistency and grit trump fatigue every single time.
I tackled a deep security report on owner-signed HCA intents lacking execution equivalence checks on both the client frontend and on-chain level. If a backend orchestrator server gets compromised, it can secretly alter intent payloads to grant unauthorized administrative control, while smart contracts execute them blindly without checking if the payload matches the user's original request.
Despite feeling completely worn out, I sat down, took the evaluation, and scored a massive 10/10! 🚀
Showing up when you want to quit is how real breakthroughs happen. Never give up on your marathon, no matter how tired you feel.
ANOTHER MILESTONE UNLOCKED! 🔥🌐
Officially completed Cisco Networking Academy’s Networking Basics course! 🏆🎓
Networking foundation: BUILT. 🔐
#Cybersecurity
#CiscoNetworking #NetworkingBasics @THE_CYBRARIANS @CiscoNetAcad
show_ip_int_brief retweeted
🔐 #OverTheWire Bandit | Levels 10–20
My CTF learning journey continues!
These levels took me beyond basic Linux commands into data decoding, file analysis, network protocols, authentication, and Linux access control.
Here are some of the key concepts I worked through👇:
show_ip_int_brief retweeted
HOW TO BECOME A NOC ENGINEER
A Network Operations Center (NOC) Engineer monitors networks, troubleshoots issues, and keeps systems running smoothly.
Here’s how to get started:
1. Learn Networking - Understand IP addressing, subnetting, DNS, DHCP, TCP/IP, and the OSI model.
Master Network Devices — Learn how routers, switches, firewalls, and access points work.
2. Learn Linux Basics - Practice commands, log analysis, and basic troubleshooting.
3. Understand Monitoring - Explore tools like Zabbix, PRTG, Nagios, and SolarWinds.
4. Practice Troubleshooting - Learn to use ping, traceroute, nslookup, and Wireshark.
5. Build a Home Lab - Practice network configurations and troubleshooting using Cisco Packet Tracer.
6. Learn Ticketing & Documentation - Understand incident reporting, escalation, and documenting network issues.
7. Get Certified (if you can afford to) - Start with CompTIA Network+ or Cisco CCNA.
8. Apply for Entry-Level Roles - - Look for NOC Technician, NOC Analyst, or Junior Network Engineer positions.
9. Keep Learning - Build hands-on experience and develop your networking skills.
You don’t need to know everything to start. Learn the fundamentals, practice consistently, and apply!
Goodluck.
show_ip_int_brief retweeted
For someone participating in their first CTF, what advice do you have? (Note: I’m learning as I go!)
What are the main things I should know before getting started?
#Cybersecurity #EthicalHacking
show_ip_int_brief retweeted
I’m not even done yet 😂😂 I’m still cooking and adding more in batches.
Drop a star if you find it helpful
I took some time off to build something for people learning networking and preparing for their first roles in tech.
Introducing Broken NetLabs
A collection of broken network labs for aspiring Junior Network Engineers, Data Centre Network Engineers, NOC Engineers, and anyone looking to build real-world troubleshooting skills.
Download a lab, find the faults, fix them, and document your solutions in public. You'll also sharpen your technical documentation skills along the way.
🔗 github.com/akintunero/broken…
Happy troubleshooting! Feel free to share this with someone in your network who could benefit from it.
show_ip_int_brief retweeted
I designed a multi-site enterprise network connecting a Head Office, Branch Office and simulated ISP.
I implemented VLANs, inter-VLAN routing, DHCP, OSPF, eBGP, route redistribution and NAT/PAT.
I documented the configurations and testing. Take a look👇
github.com/IgbojionuLinda/En…
Day 125 of my #EthicalHacking journey. 🔐
Yesterday, I practically spent the whole day exploring #Wireshark. 😅
Here's what I covered:
- Wireshark dissectors (Frame, Ethernet, IPv4, TCP, etc.).
- What happens when a standard port is assigned to a different application.
- How to manually adjust port assignments.
- How Wireshark handles non-standard ports.
- Heuristic dissectors and how to adjust protocol dissection.
One thing I'm beginning to appreciate about Wireshark is that capturing packets is just the beginning. Understanding how Wireshark identifies and interprets those packets is another level entirely.
Still exploring, still learning 🔥
Day 124 of my #EthicalHacking journey. 🦈🔐
Yesterday, I kind of lost myself in #Wireshark. 😂
While exploring packets, a question crossed my mind: How do I find the router on my network? 🤔
I started with the MAC address, which was pretty easy to spot in an HTTP request packet and as the destination MAC. But finding the router's IP took me a little longer, until I checked a DHCP ACK packet and spotted it. 😂
Sometimes, the answer is right there in front of you!
I also explored broadcast packets, including DHCP requests and ARP traffic.
At one point, I noticed an unfamiliar IP address, so I investigated its traffic. Turns out, it was only involved in DNS traffic, so I suspected it was the DNS server.
But here's what got me thinking: Why was my DNS server using a local IP instead of an external one like Google's "8.8.8.8"? 🤔
Another rabbit hole to explore! 😂
show_ip_int_brief retweeted
Day 60/100✅
One tiny quote mark stopped my whole script today.
unterminated string literal
I read the message, found line 1, deleted the extra ", and it ran.
Learning to read errors might be the most useful skill I pick up this week.
#Python #100DaysOfCyber @malik_cybersec
Day 59/100
Finished Cisco Endpoint Security yesterday. Today I picked what to learn next, and it wasn’t another course.
Python. Every log parser, scanner and automation script in security starts there.
Starting Automate the Boring Stuff. #100DaysOfCyber @malik_cybersec
show_ip_int_brief retweeted
I took some time off to build something for people learning networking and preparing for their first roles in tech.
Introducing Broken NetLabs
A collection of broken network labs for aspiring Junior Network Engineers, Data Centre Network Engineers, NOC Engineers, and anyone looking to build real-world troubleshooting skills.
Download a lab, find the faults, fix them, and document your solutions in public. You'll also sharpen your technical documentation skills along the way.
🔗 github.com/akintunero/broken…
Happy troubleshooting! Feel free to share this with someone in your network who could benefit from it.











































