• ToriborA
    link
    fedilink
    English
    arrow-up
    25
    ·
    9 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
      ·
      9 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
      ·
      9 months ago

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

      • ToriborA
        link
        fedilink
        English
        arrow-up
        4
        ·
        9 months ago

        You could, but that information gets stale pretty quickly and is tricky to do with the ACLs.

    • KillingTimeItself@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 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.