• Big_Boss_77@kbin.social
    link
    fedilink
    arrow-up
    82
    ·
    6 months ago

    Teach him to use it and send him down the path of one of the most frustrating career paths in existence…

    Developer: Hey, I think the network is broken

    Network Engineer: Okay, lemme check 30 seconds later nope, looking good, what’s up?

    Developer: There’s a network issue, I ran this new code and lost everything.

    NE: That’s… not really how the network works…

    Dev: I’m a Developer, I know how the network works.

    NE: Really…? Do you know how servers work?

    Dev: Yes, of course. …

    NE: Then why didn’t you look that your code crashed the VM you were using and you need to restart it…

    Dev: …so it was a network issue?

    NE: …

    Dev: to other Devs Hey guys, don’t worry, it was a network issue, but I got them to do their job for once and fix it.

    NE: resumes recreational liver destruction

    • qjkxbmwvz@lemmy.sdf.org
      link
      fedilink
      arrow-up
      24
      ·
      6 months ago

      After setting up my own network, and trying to (kinda sorta) do it the right way (multiple SSIDs, vlan segregation, restrictive firewalls for iot, VPN to a VPS, etc.) — I have so much respect for network engineers. First month with my new router, felt like I “broke the Internet” every other day.

    • geekworking@lemmy.world
      link
      fedilink
      arrow-up
      10
      ·
      6 months ago

      Or he could go it operations where every day is “a bad day to stop sniffing glue” because you are the only thing keeping the house of cards up while dev and network squabble over who’s foot cannon broke shit this time.

    • Crow@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      6 months ago

      Networking has to be the most confusing and tedious IT work I’ve ever done. I still don’t fully understand all the basics of security. But by far the worst part is that troubleshooting can’t be done like normal programming. Network troubleshooting takes forever, and all you get is a working network. Network work feels so dull even I have a hard time seeing my effort.

      • jubilationtcornpone@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        ·
        6 months ago

        No kidding. There’s no debugger. You can’t just set a breakpoint and see what’s going on under the hood. It’s more like playing Russian roulette and hoping you don’t bring the whole network down.

        It’s messing with the wiring while it’s still hot and there often isn’t a better way to do it.

    • wreckedcarzz@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 months ago

      Those last couple of steps actually involve a shotgun and condolences to the devs family. Take no shit.

  • Lophostemon@aussie.zone
    link
    fedilink
    arrow-up
    51
    arrow-down
    1
    ·
    6 months ago

    My 14 yo would be stoked. He’s right into networking tech. Doesn’t really care about Nintendo.

    • JustUseMint@lemmy.world
      link
      fedilink
      arrow-up
      24
      ·
      6 months ago

      No you can’t use the web GUI you fucking baby you’re going to learn IOS like a REAL man! No not the apple one! Cisco had it first anyway!!!

    • afraid_of_zombies@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      6 months ago

      My field still has a lot of serial. I don’t know at this point how many serial connectors I have made by hand that are out there and I have only a vague idea how any given one works.

  • R0cket_M00se@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    6 months ago

    Alright now hook that shit up to the router, don’t forget to create a LAG or you’ll create a broadcast storm, and I’m in a WoW raid in ten minutes so make it fast.

      • [email protected]@sh.itjust.works
        link
        fedilink
        arrow-up
        6
        ·
        6 months ago

        LAG are aggregated interfaces and they can indeed be used to prevent (some) layer 2 loops. LAG as in Link Aggregation Group)

        Using 2 non-LAG interfaces between the same 2 devices creates a loop.
        In the case of a loop, if you’re running spanning tree, one of these interface will be blocking instead of forwarding, preventing the loop, but also percentile the use of this interface until the topology changes (ie: the current one goes down).
        If you’re not running spanning tree for some reason, then both interface will chug along, oblivious to the fact that there’s a loop and broadcast packets will indeed keep being flooded on one and received on the other, again flooded, etc. creating a broadcast storm and impacting performance of the whole layer 2 domain and possibly even crashing devices.

        A LAG more or less means the interfaces in the group behave as one big (aggregated) interface.
        LAG also means you can push traffic on both interfaces for more bandwidth.

        Source: Network engineer Internet plumber

      • R0cket_M00se@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        6 months ago

        It doesn’t.

        The assumption is that they’re creating a high bandwidth trunk interface to the L3 switch/router, so if they forget to create an aggregate it’ll be two independent interfaces and will down the network (or a port will auto down itself with STP, MSTP, etc. but that’s not as funny)

        • MadhuGururajan@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          6 months ago

          A router of industrial scale which i see at work has its ports to be l3 ports by default. They don’t down the network as the router rejects config where two ports are given the same subnet… at least the ones i operate at work.

          • R0cket_M00se@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            6 months ago

            That’s true, the default for layer 3 switches is to have its port set as routable.

            The original joke really kinda falls flat with modern tech, but it’s still funny to think about handing a switch to someone with zero knowledge and then watch as they accidentally lock up the environment.

  • XTornado@lemmy.ml
    link
    fedilink
    arrow-up
    12
    ·
    6 months ago

    So that’s why Nintendo uploaded that video explaining the Switch after 7 years selling it.

  • MeanEYE@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    6 months ago

    Had I gotten this, I’d be ecstatic. Networking was always a mystery to me and I loved playing with networking services.