home.social

#neteng — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #neteng, aggregated by home.social.

  1. Cisco’s integration of AI into their general certification tracks. linkedin.com/posts/john-capobi

    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.

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

  3. 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.)

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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.

  11. 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

  12. 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

  13. 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

  14. 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

  15. 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.”

  16. 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

  17. 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

  18. "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

  19. "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

  20. "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.

  21. "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

  22. "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

  23. 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

  24. 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

  25. 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.

  26. 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

  27. 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

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

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

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

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

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

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

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

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

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

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

  38. 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

  39. 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

  40. 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.

  41. 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

  42. 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

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

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

  45. I heard IPv4 referred to as telnet-era IP yesterday. Made me smile.

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

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

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

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

  50. I’m wondering if @mikrotik has thought of adding “access point” on the back of these? Maybe taking the joke a little too far? merch.mikrotik.com/products/gr