#neteng — Public Fediverse posts

Well, huh. Retrofitting a @mikrotik based PPPoE WISP for #IPv6 and labbing out the design. Turns out the PD for the clients can be handled entirely through RADIUS and the PPPoE server. CE side still needs a separate PPPoE and DHCP-PD client configuration, but everything on the PE side is simple. Liking this. #NetEng

Today I learned that SVG is XML-based, which means I can script variants of my network icons with sed. This makes me smile. #NetEng

Kirk Byers’ highly recommended and free Learning Python for Network Engineers course starts again today, Tuesday, June 16th. For more details and to sign-up see: https://buff.ly/LZq140c #NetEng

I'm getting more than a little frustrated with wasting my time on circular troubleshooting with the questionably-useful chatbot that has replaced frontline support at #Cisco #TAC. #NetEng

Danke an @9er für den genialen Talk, besser als so manches bei DENOG und RIPE.

https://cfp.gulas.ch/gpn24/talk/YZQXRH/

Ich empfehle unbedingt die Aufzeichnung anzugucken, sobald sie verfügbar ist, featuring 2-3 Fragen/Anmerkungen von meiner Wenigkeit.

Update: https://media.ccc.de/v/gpn24-605-wir-bauen-uns-ein-forschungsnetz-belwu-2026

#gpn24 #neteng

Cisco’s integration of AI into their general certification tracks. https://www.linkedin.com/posts/john-capobianco-644a1515_cisco-just-settled-the-argument-ccna-v20-share-7463223964203655168-4M_x

AI in networking is a logical extension of large-scale analysis and orchestration. I get that. This has the same foundational thinking as the “every networking practitioner must be a developer” mantra from 10 years ago… and it holds a similar level of truth. This is why it belongs in the automation tracks and not the ever increasingly broad general tracks. #NetEng #AI #Cisco #CCNA #CCIE

Wow. Fifteen years since I became a founding member of the #FNS. Great experiences, great people, dubious networking. https://flatnetworksociety.com/ #NetEng

Auditor: Can you send a screenshot of the access VPN timeouts so we can demonstrate policy compliance?
Me: (Sends relevant portions of the configuration.)
Them: This is a text file. We need a screenshot.
Me: (Sends screenshot of my terminal session showing the relevant portions of the configuration.)
#InfoSec #NetEng #MaliciousCompliance

We have dozens of relatively simple methods to secure Internet traffic, but we’re often reduced to “just open access through your firewalls from this huge list of source addresses” because too many folks can’t be arsed to do any of those. Keeping it simple is •not• about moving the complexity into the customer’s realm of responsibility. #NetEng #InfoSec

I think I’ve been in this industry for too long. I searched for a synopsis this morning and accidentally typed “synoptics” instead. Last week I was teaching the NATO phonetic alphabet and taught “unicorn” instead of “uniform.” #NetEng #SiliconValley

"SD-WAN" (over MPLS no less!) with IPSec tunnels (not transports!), hard static routes for link monitoring, and floating static routes for tunnel failover... because that's less complicated than using a routing protocol. #NetEng #BangHeadHere

Listened to a presentation today from someone with an accent that made every instance of “configuration” sound like “conflagration” instead. Thinking about this further, sometimes there’s little difference between the two. #NetEng

At TORNOG 1 in a Nokia automation workshop. They're talking about gRIBI and I'm suddenly craving a steak. #NetEng

Taking a break from the day to day for an awesome event in Toronto. #NetEng https://tornog.ca/events/tornog-1/

Hm. RADIUS bandwidth profile was defined as 1024/8192 B/s instead of 1024/8192 KB/s. I now have an explanation for the angry tickets from a few customers. Easily corrected. I also know that my traffic restrictions are working correctly… if not as intended. #Oops #NetEng

I heard IPv4 referred to as telnet-era IP yesterday. Made me smile. #NetEng #IPv6

I’m wondering if @mikrotik has thought of adding “access point” on the back of these? Maybe taking the joke a little too far? https://merch.mikrotik.com/products/groove-boxer-briefs #WiFi #NetEng #Merch

For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. https://github.com/ghostinthenet/l2vpnLab #MTPC #NetEng

I just spent an hour #Labbing an #L2TPv3 pseudowire native fragmentation (#PWE3) problem. Turns out the platform doesn’t •do• native fragmentation, but it took forever for me to figure this out because my oversized #IPv6 pings were making it across the wire. This shouldn’t happen without native fragmentation.

Two coffees later it dawned on me that I was pinging from the device that was anchoring the pseudowire, so IPv6 was fragmenting at the source. A packet capture showed the fragmentation headers •and• the missing MRRU attribute in the L2TPv3 pseudowire setup. I should have started there.

#NetEng #ThereAreDays

Word of the day: Assiduity n. great care and attention to detail. A required quality of networking practitioners engaged in labbing. If we don't know all of the details of how a thing works, we don't •really• know how it works at all. #NetEng

The trace is consistent: ✅ 1492B Payload = PASS ❌ 1493B Payload = DROP

Because it returns zero "Packet Too Big" errors, clients loop forever (RFC4890 violation).

I'm thinking of forcing RA MTU to 1280 to stop local fragmentation entirely. Thoughts? #IPv6 #NetEng

@jschauma #Yoinked #NetEng

Just recorded an episode of Heavy Networking with Ethan Banks , the founder of Packet Pushers, here at #NANOG96 . It was my third time on the packet pushers network but my first time having a 1:1 with Ethan.

We were discussing the task of defining a network service. It's harder than you think!

Thanks Ethan & the packet pushers team for having me on. Thanks for also allowing me to advocate for #TORNOG1 , happening this April!

#CanadaNeedsNOGs #NANOG #Podcast #NetEng #TORNOG