this post was submitted on 04 Apr 2024
724 points (100.0% liked)

Technology

37712 readers
337 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] UmbraTemporis@lemmy.dbzer0.com 78 points 7 months ago (8 children)
  • 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 25 points 7 months ago (4 children)

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 8 points 7 months ago

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

load more comments (3 replies)
load more comments (6 replies)