• 🌘 Umbra Temporis 🌒@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    78
    ·
    7 months ago
    • Easier to setup
    • More control
    • Easier to maintain
    • Dirt cheap
    • Low power
    • Space efficient
    • Zero downtme

    Need I go on? This is clearly the future. Friendship ENDED with Network Hardware now PEG is my best friend.

    • Toribor@corndog.social
      link
      fedilink
      English
      arrow-up
      25
      ·
      7 months ago

      I want to criticize this but I have multiple production environments with no DHCP and the process for provisioning new servers is basically “Guess an ipv4 address and if you pick one that’s already in use the build will fail and you can guess again.”

      This is arguably better which is a little embarrassing.

      • ms264556@beehaw.org
        link
        fedilink
        arrow-up
        8
        ·
        7 months ago

        Totally OK way of doing it. You basically manually implemented the protocol APIPA uses to allocate 169.254 addresses.

      • exu@feditown.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        7 months ago

        Have you never just run an nmap of the whole network and made a list of ip addresses that are occupied?

      • KillingTimeItself@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        ah yes the good old “gonna use manual addressing because lmao” and then the good old “man i wonder which IP sets i have used already”

        my beloved.

    • MystikIncarnate@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      My only argument is in the idea of finding which device has a particular IP address.

      Guess you’re running laps around the campus staring at pegs for a while to figure out which one it is.