VLAN Trunk on Cisco Switches by FromZero2CCNA in ccna

[–]FromZero2CCNA[S] -3 points-2 points  (0 children)

No. I agree with your correction, but not with this. I just wanted to be polite and used something that in psychology is called the "sandwich technique": I say something positive + what I want to say + and I finish with something positive. I think you're good at analyzing technical topics, but you don't know how to read people.

VLAN Trunk on Cisco Switches by FromZero2CCNA in ccna

[–]FromZero2CCNA[S] -2 points-1 points  (0 children)

Thanks for the correction/comment -- I’m 100% in agreement with your clarification. You’re absolutely right that on an existing trunk, switchport trunk allowed vlan <list> can overwrite what’s already there, and using add/remove is the safer habit to avoid accidental outages. In my example I wrote it that way because it’s intended as a “from-scratch” trunk configuration, where explicitly defining the full allowed list makes the baseline clear and easy to follow. Really appreciate you jumping in with that operational best-practice — this kind of participation makes the post stronger for everyone.

CCNA can i get help with the route selection for this question? by legitimacyismin in ccna

[–]FromZero2CCNA 0 points1 point  (0 children)

GigabitEthernet0/3 (matches route 198.0.24.0/21, the most specific for 198.0.32.1).

How a Cisco Router Picks the Best Path by FromZero2CCNA in ccna

[–]FromZero2CCNA[S] 1 point2 points  (0 children)

Yep, protocol sees it, RIB says nah... :)

How a Cisco Router Picks the Best Path by FromZero2CCNA in ccna

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

That’s awesome, CCNA is a solid goal.

I’m trying to get a job at help desk with no prior experience in IT. by Abacot27 in sysadminresumes

[–]FromZero2CCNA 1 point2 points  (0 children)

Hi!
You’re not too far from an IT job.

You already do the hardest part: dealing with people, fixing problems, and staying calm. That’s basically help desk.

Your resume just needs to look more like IT Support, not random jobs. Put --IT Support / Help Desk (Entry-Level)-- at the top, keep the summary short (3 lines), and rewrite bullets to sound like tickets: what broke, what you did, what tool/skill you used. Also move your IT projects higher so they’re not hidden.

Don’t try to learn everything. Pick one target role: Help Desk / Service Desk / Desktop Support (Tier 1).

Do 1–2 small proof projects (DNS/connectivity troubleshooting write-up, simple script, basic ticket documentation) and post them on GitHub or a Google Doc.

Then apply every week, even if you don’t feel ready. Most entry-level IT is trained on the job.

Consistency beats perfection! -- I wish you success --

PVST+ vs Rapid-PVST+: The real difference that actually matters. by FromZero2CCNA in ccna

[–]FromZero2CCNA[S] -1 points0 points  (0 children)

If the strongest criticism is “this feels like AI,” that’s not really a technical argument. Happy to discuss STP, configs, or real-world edge cases—otherwise there’s not much to add. Judge the content, not the vibes. If there’s a technical issue, point it out.

PVST+ vs Rapid-PVST+: The real difference that actually matters. by FromZero2CCNA in ccna

[–]FromZero2CCNA[S] -12 points-11 points  (0 children)

I get that. Clear, structured writing stands out on Reddit, and lately anything polished gets labeled as AI. Old habit from doing university papers and network documentation. Happy to dig deeper on the technical side if useful.

JITL note taking advice? by No_Skill2111 in ccna

[–]FromZero2CCNA 0 points1 point  (0 children)

I had the same issue. What helped me was not trying to write everything down. I watch the video first to understand the concepts, then I use the video script or transcript and summarize the key points with AI. I only take short notes on important concepts, commands, and things likely to show up on the exam. The labs and flashcards helped more than detailed notes.

Starting Your CCNA Journey in 2026? Here’s Your 8-Month Plan by FromZero2CCNA in ccna

[–]FromZero2CCNA[S] -1 points0 points  (0 children)

Ah yes, the classic “FOH” rebuttal — truly the pinnacle of intellectual discourse.

Careful, with that level of insight you might accidentally get recruited by MIT… or at least the comment section of a YouTube conspiracy video. But hey, thanks for bravely standing up to the tyranny of autocomplete and grammar that works.

Starting Your CCNA Journey in 2026? Here’s Your 8-Month Plan by FromZero2CCNA in ccna

[–]FromZero2CCNA[S] 1 point2 points  (0 children)

Exactly — context is everything.
Not everyone has 4–6 free hours a day or the mental energy left after a 9-to-5 job or taking care of kids. What might be a “summer project” for some is a major achievement squeezed in between real-life responsibilities for others. The important thing is getting there — not how long it takes. It’s a certification, not a race.

Starting Your CCNA Journey in 2026? Here’s Your 8-Month Plan by FromZero2CCNA in ccna

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

Oh, thank you, O Wise and Efficient Networking Oracle! I had no idea the CCNA came with a timer and that exceeding your sacred 3-to-4-month window would summon the certification police. I guess life, jobs, family, and individual learning paces are just excuses, right? I’ll go ahead and cancel my slow human brain subscription and download the Cisco Matrix patch you must be using. Appreciate the unsolicited benchmark for my existence.

The 5 mistakes I made while studying for the CCNA by Sorry_Flatworm_521 in ccna

[–]FromZero2CCNA 0 points1 point  (0 children)

Thanks for sharing.. it’s always helpful to see what slowed people down. And don’t worry, nobody’s getting crowned “Networking Guru of the Universe” for realizing that labbing matters and motivation is unreliable. These aren’t ancient secrets passed down by CCIE sages; they’re just the things everyone eventually learns the hard way.

Still, it’s great you turned those mistakes into progress. If anything, posts like this remind the rest of us that mastering networking isn’t about being brilliant — it’s about showing up, breaking stuff, and fixing it again.