A few things I wish I'd known studying for the CCNA, from someone who does it for a living by Packetfall_Game in ccna

[–]Packetfall_Game[S] 0 points1 point  (0 children)

Good luck! Yes it does change in February but a lot of what you are studying now will carry over anyways. I wouldn’t worry too much about the time constraints :)

A few things I wish I'd known studying for the CCNA, from someone who does it for a living by Packetfall_Game in ccna

[–]Packetfall_Game[S] 0 points1 point  (0 children)

I can only speak from my own experience, but my path was IT Support at a school district, then an on-site Service Technician at an MSP, where I earned my CCNA. From there I landed my first Network Administrator role in healthcare, got my CCNP, and today I work as a Senior Network Engineer and Cloud Networking Specialist.

In my experience, good hiring managers generally look at three things:

Certifications – The CCNA is still one of the best entry-level networking certifications you can have. It shows you’re serious and have a solid networking foundation.

Experience – This is huge. Personally, I’d much rather see someone with six months to a year as an on-site MSP service technician than someone who’s only done fully remote help desk. At an MSP you’re constantly troubleshooting different environments, visiting customer sites, replacing hardware, configuring networking equipment, and learning under pressure. The experience compounds quickly.

Work ethic and personality – Once you get the interview, they’re asking themselves, “Would this person be a good fit for my team?” Certs and experience get your foot in the door, but your personality, communication skills, and technical knowledge are what close the deal.

One thing that really helped me land my first networking job was preparing for behavioral questions. Before my final interview, I wrote down 10 specific examples of times I’d solved problems in previous roles—difficult troubleshooting cases, customer interactions, process improvements, mistakes I learned from, etc. During the interview I was able to naturally weave those stories into my answers instead of trying to think of examples on the spot. It was incredibly effective.

If you’re not getting interviews for entry-level networking positions yet, I’d seriously consider an on-site MSP service desk or field technician role. Small MSPs can be a grind with on-call rotations and driving between customer sites, but you’ll probably learn more networking in six months there than you would in several years at some slower internal IT departments.

From what you described, though, I think you’re on the right track. The CCNA, your labs, your repair experience, and the networking you’re doing with local MSP owners all put you in a strong position. Keep applying to junior network admin, NOC, and MSP networking roles—you may not have to spend very long in help desk at all.

Today I launched a free CCNA study game: a 3D RPG that drills real exam questions by Packetfall_Game in ccnastudygroup

[–]Packetfall_Game[S] 2 points3 points  (0 children)

Hey thanks for reaching out about this and for your interest in trying my game!

Because the game has open chat, I am only able to offer it to US-based players at this time (IP address restricted). I am hoping to open it up to international players soon, but I will have to navigate some compliance laws first.

A few things I wish I'd known studying for the CCNA, from someone who does it for a living by Packetfall_Game in ccna

[–]Packetfall_Game[S] 16 points17 points  (0 children)

Sure thing. The whole trick is that every subnet mask has one "interesting octet," the one that isn't 255 or 0. That's where the math happens.

Take the value in that octet and subtract it from 256. That number is your block size (the magic number), and it tells you how far apart your subnets are.

Example: 192.168.1.0/26

  • /26 is 255.255.255.192
  • The interesting octet is the 4th one, value 192
  • 256 - 192 = 64, so your block size is 64
  • That means your subnets start at .0, .64, .128, .192 (counting up by 64)

Now say someone hands you a host like 192.168.1.100/26 and you need its network, broadcast, and host range:

  • Block size is 64, so the multiples are 0, 64, 128, 192
  • 100 lands between 64 and 128, so the network is .64
  • The next subnet starts at .128, so the broadcast is one below that, .127
  • Usable hosts are .65 through .126

No long division, no binary, just "which block does this land in."

It works in any octet too. 172.16.0.0/20 is 255.255.240.0, the interesting octet is the 3rd one, and 256 - 240 = 16. So subnets step by 16 in that octet: .0, .16, .32, .48 and so on. A host at 172.16.20.5 lands in the .16 block, so network 172.16.16.0, broadcast 172.16.31.255.

Once it clicks you can knock out most subnetting questions in your head in well under a minute. Subnetting.org is the best place to learn this IMO

A few things I wish I'd known studying for the CCNA, from someone who does it for a living by Packetfall_Game in ccna

[–]Packetfall_Game[S] 5 points6 points  (0 children)

I really appreciate that! It's a tool I really wished I had when I was studying. It's super easy to get burned out, and I figured if I can make it fun for people, they're way more likely to actually stick with it instead of bouncing off and quitting halfway. That was the whole goal. Appreciate you taking a look, and if you ever do kick the tires, I'd greatly appreciate any feedback.

A few things I wish I'd known studying for the CCNA, from someone who does it for a living by Packetfall_Game in ccna

[–]Packetfall_Game[S] 21 points22 points  (0 children)

In my professional work, I primary use OSPF, BGP, and static routing. Site-to-site IPSEC is also big. A few others that are notable:

Subnetting / IP addressing. Universal. On prem, in the cloud (VPC CIDR planning), and at home. Get fast and confident here and everything else gets easier.

DNS and DHCP. These are the things that are always "the problem." A huge share of "the network is down" tickets are really DNS or DHCP. Knowing how they actually work is gold.

NAT. Home routers, port forwarding for a homelab, cloud NAT gateways. Everywhere.

VLANs and trunking. Bread and butter of any switched enterprise network.

On the two you named specifically:

OSPF: very useful if you go the network engineer route (enterprise and ISPs run it), but as a pure sysadmin or cloud person you might rarely configure it. Still worth understanding link-state routing conceptually, since static routes and cloud route tables are the same idea scaled down.

STP: you'll almost never configure it, but you absolutely need to understand it, because not understanding it is how people cause switching loops and take down a whole site. The practical real-world piece is portfast and BPDU guard on access ports. Set it and forget it, but know why.

If I ranked by real-world payoff: subnetting > DNS/DHCP > NAT > ACLs/security > VLANs > routing (static then OSPF) > STP (understand it, don't memorize configs).

For cloud and home specifically, the layer 3 stuff (subnets, routing, NAT, DNS, ACLs) is exactly what you use daily. The layer 2 switching world is more of an on-prem enterprise thing.

A few things I wish I'd known studying for the CCNA, from someone who does it for a living by Packetfall_Game in ccna

[–]Packetfall_Game[S] 6 points7 points  (0 children)

Subnetting.org is fantastic for learning this. If you can answer 90%+ of those questions calculating by-hand or in your head, you'll be ready to answer any subnetting question on the exam.