mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

8.3K
active users

#neteng

2 posts2 participants0 posts today
Jody Lemoine 🇨🇦<p>I was just having a discussion on one of Orhan Ergun’s posts on LinkedIn about “no dns lookup” vs “transport preferred none” in a <a href="https://hachyderm.io/tags/Cisco" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cisco</span></a> <a href="https://hachyderm.io/tags/IOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IOS</span></a> configuration. I thought it deserved a wider distribution, so here I am.</p><p>Lots of folks disable name lookups on Cisco IOS boxen to prevent the device from attempting to resolve mistyped commands as host names. Unfortunately, this disables name lookup for •all• functions on the device, which can break a few important things.</p><p>Rather than disabling name lookups entirely, I recommend turning off the device’s default behaviour for mistyped commands, which is to treat them as host names and to connect to them via telnet or rlogin, which can include a name lookup.</p><p>Configuring “transport preferred none” on the con and vty lines will give the device no transport protocol to use for such connections and it won’t bother to try, eliminating the name lookup problem with mistyped commands while preserving lookups for other functions.</p><p><a href="https://hachyderm.io/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a></p>
Jody Lemoine 🇨🇦<p>A first principle in network security is to minimize or eliminate the attack surface. I refer to this as the Miyagi Rule, quoting the iconic sensei from “The Karate Kid” in the 1980s: “Best way to avoid punch... no be there!” <a href="https://hachyderm.io/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a> <a href="https://hachyderm.io/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a></p>
Jody Lemoine 🇨🇦<p>The more experience I have with networking vendors, the more I become convinced that their prevailing definition of “enterprise” only includes the top 1% to 2% of the enterprise market. <a href="https://hachyderm.io/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a></p>
Amy Renee<p>Me: I'm going quietly mad.</p><p>Husband: weren't you just yelling at that router?</p><p>Me: do you want to be next?? </p><p><a href="https://infosec.exchange/tags/neteng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>neteng</span></a><br><a href="https://infosec.exchange/tags/backAwaySlowly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>backAwaySlowly</span></a> <br>😂</p>
Jody Lemoine 🇨🇦<p>Booked for MTCSWE training and certification at the end of July. <a href="https://hachyderm.io/tags/MikroTik" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MikroTik</span></a> <a href="https://hachyderm.io/tags/MTCSWE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MTCSWE</span></a> <a href="https://hachyderm.io/tags/Certification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Certification</span></a> <a href="https://hachyderm.io/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a> <a href="https://hachyderm.io/tags/Pok%C3%A9mon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pokémon</span></a></p>
Wireshark<p>SharkFest'25 US is almost here!<br>June 14–19 • Richmond, Virginia</p><p>Whether you're a packet analysis pro or just getting started, SharkFest is the place to sharpen your <a href="https://ioc.exchange/tags/Wireshark" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wireshark</span></a> &amp; <a href="https://ioc.exchange/tags/Stratoshark" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Stratoshark</span></a> skills, learn from world-class instructor &amp; connect with the community.</p><p>- Hands-on workshops<br>- Expert-led sessions<br>- Keynote from Vint Cerf<br>- Pre-conference classes with top analysts</p><p>Register now &amp; be part of the packet party: <a href="https://sharkfest.wireshark.org/sfus/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">sharkfest.wireshark.org/sfus/</span><span class="invisible"></span></a></p><p><a href="https://ioc.exchange/tags/SharkFest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SharkFest</span></a> <a href="https://ioc.exchange/tags/PacketAnalysis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PacketAnalysis</span></a> <a href="https://ioc.exchange/tags/NetworkSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetworkSecurity</span></a> <a href="https://ioc.exchange/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a> <a href="https://ioc.exchange/tags/sf25us" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sf25us</span></a></p>
Aaron C<p>Jon Howe showing us…pain? Good timing on the pic. LOL</p><p><a href="https://masto.ai/tags/chinog12" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chinog12</span></a> <a href="https://masto.ai/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a></p>
Aaron C<p>Network operations is great, but what about your career? We’re getting some insights into how to route your own career.</p><p><a href="https://masto.ai/tags/chinog12" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chinog12</span></a> <a href="https://masto.ai/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a></p>
Aaron C<p>The shirt!</p><p><a href="https://masto.ai/tags/chinog12" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chinog12</span></a> <a href="https://masto.ai/tags/NetEng" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetEng</span></a></p>

🎶 please, oooh please, just tell me no.. 🎶

It's 2am and I just want one thing
a strong, handsome, sexy pair of SFP+
in a 10G ethernet switch, RISC-V cores
mod'able, jtag'able, RTOS'able, oooh yes

... so... in all seriousness, there have been lustful hardware-acquisition eyes on this pretty little design since its pre-release marketing materials hit the English speaking OSS internet, and have been watching from afar as its reviews came through, patiently.

I'm not one to say that tonight is the right time to buy a pair, but it's not NOT the right time to buy a pair of Milk-V Vega switches.

Main:
- milkv.io/vega

Detailed Community Review:
- Getting an overview of Vega Basics
- community.milkv.io/t/getting-a

*note: I am particularly aware of its limitations, do not expect a production grade switch, mostly want more risc-v hardware to develop with, and general messing around

When troubleshooting, asking what changed since everything last worked is an important step. It’s also important to not fixate on this step because we don’t always •know• what changed. If it’s obvious, great. If it’s not, stay focused on what’s happening now rather than going down the rabbit hole of what might have happened. #NetEng #Troubleshooting

“Switches switch and routers route.” That’s a statement that isn’t as true as it used to be… or at least not without carefully defining context.

It’s time to go old school and stop using the word “switch” in this context. The first switches were hardware-accelerated bridges and have since evolved past bridging. If we switch to “bridges bridge and routers route” we’ll be more correct in our thinking, but we have to think of bridging and routing as functions rather than devices.

These days, most switches can accelerate both bridging and routing (L2 and L3) on their backplanes. Most routers have similar functions and are built on switching chips too. The whole line between switches and routers is becoming a very grey and fuzzy one.

Bridges bridge and routers route, and switches do either or both •very• quickly. Most of the other considerations are about product placement.