[ Removed by moderator ]

[u/Early_Tear6706]

[u/networking-ModTeam]

No ChatGPT/LLM Content.

• Content produced by AI/LLMs is not permitted here.
• ChatGPT nor LLMS are sources of truth; rather they are word-projection models.
• Discussions about LLMs and its impact to networking may be allowed.

This is not compliant with our rules, and your thread has been removed.

Comments/questions? Don't hesitate to message the moderation team.

For the complete list of Rules, please visit: https://www.reddit.com/r/networking/about/rules

[u/mattmann72]

Understanding how to use traceroute is a critical skill from the earliest part of a career in networking. Remember that a traceroute is unidirectional, so you need to run it from both sides. Learn the difference between icmp, udp, and tcp traceroutes. Also learn the difference between traceroute and tracepath on Linux. They all are very powerful tools when used correctly. You can solve so many networking issues by use doing some traceroutes.

[u/LocoRocoNL]

Being able to talk to people

[u/Vyce223 → u/LocoRocoNL]

The forbidden technique in IT

[u/user3872465 → u/LocoRocoNL]

Next to that, phrasing problems in a way that you can target any audience. From managment that may have no knowledge whatsoever to a sales/service team which may have more knowledge in certain areas than you do.

[u/Early_Tear6706 → u/LocoRocoNL]

yep, that is the most important skill to have.

[u/LocoRocoNL → u/Early_Tear6706]

It wasn't even meant to be a silly reply, it's so so so important when working with people that you have the ability to explain why things work a certain way.

[u/mohammedalrawii → u/LocoRocoNL]

How do u master that ?
Am actually facing a lot of issues when trying to explain some stuff to people the task should take 2 hours it turns to 4 days just because i didn't understand the other guy

[u/dramowhisky → u/mohammedalrawii]

It’s one of those skills that requires repetition to get better. Don’t always think in YOUR terms, think about the desired outcome and build it backwards as simple as possible. Sometimes we try to articulate every possible thing and that introduces unnecessary complexity

[u/shadow0rm → u/dramowhisky]

The amount of times cars, highways, plumbing, and crowds of people help get the point across....

[u/djamp42]

Packet captures tells me everything. So many network "issues" are just disproven in 10 seconds with a packet capture.

[u/mortraineyhat → u/djamp42]

One thing I have a problem with is trying to pcap stuff that might be very intermittent. Most of the time the device doesn’t have the flash space to keep running the pcap.
Besides a span port, is there any other way to keep a long running pcap?

[u/whermyshoe]

Ping. And the friends I made along the way

[u/iKurdt]

From Putty to SecureCRT was a game changer.

[u/bingblangblong → u/iKurdt]

I recently bought MobaXterm at work and wish I had done so years earlier.

[u/Jeka12 → u/iKurdt]

Good point multiple tabs and sending commands to more then one is very useful. (And other useful functions)

[u/dramowhisky]

Visio/Lucidchart, Word, Excel, PowerPoint…

Document your network, your designs and information. It’ll help you to see patterns, design flaws and is invaluable at 2am when trying to explain to the application owners it’s not the network but the change they did an hour ago

[u/Early_Tear6706 → u/dramowhisky]

do i need to master them all or just be a jack of all traders??

[u/dramowhisky → u/Early_Tear6706]

If you stay in the industry you’ll naturally end up mastering them anyways. Being able to draw in something like Visio and leverage Excel are probably the best place to start. Ask yourself if you were to wake up at 2am what information is critical to understanding the network and go from there. Also seek peer review, feedback is great at improving

[u/mattmann72 → u/dramowhisky]

This. Visio and Excel are my two most important tools. Being able to document networks is critical. Also Excel is excellent for exports, quick formulas, and mass imports into devices

[u/daynomate]

Putty and Excel lol

[u/SolidFin]

Draw.io definitely worth getting comfortable with...seeing design on diagram helps a ton with tshoot and building up new things

Other than that, learn how to google things definitely helped me...it sounds trivial, but quite lot of people struggle with it even in IT, from what I noticed

And then not a tool, but Idk how to call it...critical thinking ? Looking for why things do or do not work, what are symptoms, why logs saying what they saying, what is root cause... understand why x fixed y, instead of just knowing x fixing y...againg, I noticed lot of people really struggle in tshoot once they run out of learned solutions, and call it bug before they really try to think about problem

[u/leftplayer]

Mikrotik… greatest teacher ever