- 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.
Low tech DHCP
Submitted 8 months ago by ElCanut@jlai.lu to technology@beehaw.org
https://jlai.lu/pictrs/image/96db2db5-7942-4e90-aa53-6e6c07b8c25a.jpeg
Comments
UmbraTemporis@lemmy.dbzer0.com 8 months ago
Toribor@corndog.social 8 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 8 months ago
Totally OK way of doing it. You basically manually implemented the protocol APIPA uses to allocate 169.254 addresses.
exu@feditown.com 8 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 8 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.
Kissaki@beehaw.org 8 months ago
Zero downtme
If the paper falls down it’s literal downtime though!
UmbraTemporis@lemmy.dbzer0.com 8 months ago
But the server is still operational, it’s just moved.
- Resilient
- Durable
- Secure
MystikIncarnate@lemmy.ca 8 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.
nxdefiant@startrek.website 8 months ago
Distributed Honor-system Clothes Peg Server
Blooper@lemmynsfw.com 8 months ago
Lol honor system omg I’m dying
JoMiran@lemmy.ml 8 months ago
I did something like this some 22 years ago or so. I can’t remember the exact reason why but essentially DHCP was not reliable enough or it caused some issue with the proprietary network hardware my company built and sold. So I built a little “kiosk” (old laptop with an HTML interface to an database) that would give you an IP and a “return by” timer of 12 hours. Before displaying it would ping to make sure the IP wasn’t active. Looking at this post I know realize that I could have just bought a pack of clothes pins and saved myself some trouble.
t3rmit3@beehaw.org 8 months ago
The RFC is actually real, though it it basically a joke: www.rfc-editor.org/rfc/rfc2322
Management of IP numbers by peg-dhcp
Introduction This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don’t necessarily have a clear organisational body.
History of the protocol.
The practice of using pegs for assigning IP-numbers was first used at the HIP event (www.hip97.nl). HIP stands for Hacking In Progress, a large three-day event where more then a thousand hackers from all over the world gathered. This event needed to have a TCP/IP lan with an Internet connection. Visitors and participants of the HIP could bring along computers and hook them up to the HIP network.
During preparations for the HIP event we ran into the problem of how to assign IP-numbers on such a large scale as was predicted for the event without running into troubles like assigning duplicate numbers or skipping numbers. Due to the variety of expected computers with associated IP stacks a software solution like a Unix DHCP server would probably not function for all cases and create unexpected technical problems.
jarfil@beehaw.org 8 months ago
It’s not a joke if it specifies a procedure to solve a real-world problem.
RFC 2549 is a joke, RFC 1149 is almost a joke (basically a spec for a sneakernet, XKCD What If 31 ), RFC 2324 is mostly a joke but also an example of IoT… and similar thing goes for all of these:
tangentsoft.com/rfcs/humorous.html
Even the ones most intended as a joke, have some grain of usefulness in them.
sobriquet@aussie.zone 8 months ago
The XKCD one is interesting, but seems to be missing the transfer to/from the storage medium sent by FedEx.
If I want to move data from my computer to yours over the internet, the internet bandwidth between our devices/networks is the main consideration. If I’m FedExing SD cards or HDDs, I’ve also gotta take into account the transfer times to get the data ONTO those devices.
I wonder how the analysis would fair when taking into account:
- speed of internet
- TB/kg of storage
- storage medium transfer speeds
sushibowl@feddit.nl 8 months ago
Written on 1 April 1998. definitely a joke, though it does work.
Zworf@beehaw.org 8 months ago
Haha this is literally how we used to deal with this at CampZone, a huge LAN party, back in the mid-2000s.
sunbeam60@lemmy.one 8 months ago
Same as The Party in Aars, Denmark, in the 90s. Every table had a sheet. Cross out the IP you picked.
Zworf@beehaw.org 8 months ago
Oh yeah The Party was another big one. Probably gone by now too?
Inktvip@lemm.ee 8 months ago
Talking about Lan uplinks, in the early 2010’s I had the joy of working with a 20gb uplink at a small university LAN (the sysadmin got a good amount of free pizza and beers for that one). I spent a large amount of my savings on a 10gb NIC only to find out my hard drive couldn’t keep up lol.
Zworf@beehaw.org 8 months ago
Wow…
I remember in 1993 my uni had no uplink. It was UUCP only (so just polled mail). In 1994 we got an uplink which was 256kbit shared between all sites. Luckily it came in to our facility first (the IT/Tech branch) and was cascaded further so we basically used it all 😜
Flax_vert@feddit.uk 8 months ago
Probably the server room in a big company
silentdon@beehaw.org 8 months ago
The admin at my first job did this but with an excel spreadsheet. They were old school and didn’t “trust” DHCP.
Kissaki@beehaw.org 8 months ago
If they were using a spreadsheet I don’t think it qualifies as equal/the same to this.
Zerthax@reddthat.com 8 months ago
I have to use a lot of static IP addresses, and I’d take this over what I normally deal with.
JohnEdwa@sopuli.xyz 8 months ago
This is basically how radio controlled models using FM TX/RX pairs were coordinated back in the day, there would be a board witch each frequency crystal that you would use for your transmitter, and you’d plop the matching one into your model. Reason being that if someone was already flying something and you turned your radio on to the same frequency, they would immediately crash.
Frederic@beehaw.org 8 months ago
Superb, really!
Barometer3689@feddit.nl 8 months ago
Lol I know that place. Funny finding it on here.
uninvitedguest@lemmy.ca 8 months ago
RFC = Really Fuckin’ Cheap?
Mountaineer@aussie.zone 8 months ago
Can’t tell if you’re joking, but a Request For Comments is effectively a proposal for how a process should be performed.
Some of them are eventually ratified as internet standards by the IETF.
Plenty of them remain useful as defacto standards even without formal acknowledgement.uninvitedguest@lemmy.ca 8 months ago
Thanks! Genuinely had no idea. Thought it was being described as a really fuckin’ cheap DHCP server.
tunetardis@lemmy.ca 8 months ago
1st reaction: lmao 2nd reaction: hey wait, this is pure genius!
Fubarberry@sopuli.xyz 8 months ago
Yeah, the older I get the more I appreciate solutions like this.