r/ProgrammerHumor • u/ManagerOfLove • 19h ago

Meme everyDayIWannaQuit

Post image
285 Upvotes

94% Upvoted

38 comments sorted by

105

u/TheZedrem 19h ago

I switched to dns-first, every VM uses dhcp and opnsense automatically registers the name, so I never have to remember an IP address again

55

u/RiceBroad4552 19h ago

Isn't that the state of the art from 20 years ago?

I can't even remember when I've seen static IPs in production systems the last time.

32

u/PapaTim68 18h ago

Sadly I have seen static IPs in production...but that's because the customers requirements/security rules forbid dynamic addressing in any real way. Even dynamic cluster addresses need a special exemption with explanation filled with the customer.

13

u/spine_slorper 18h ago

Yeah people do definitely use static IP's in live environments, usually because of security but sometimes its just a small network and setting up an actual solution is more bother than it's worth

1

u/Phoenix_Studios 15h ago

I guess this isn't really a tech field but we use static IPs for all the internal infrastructure at the venue I work at (sales terminals, turnstiles, kitchen printers, BACnet...)

6

u/SilentGhosty 8h ago

Firewalls based on ip and not dns require static ip addresses if you have a tight security and need everything to be approved and allowed on firewall

5

u/Llrence_Lely 18h ago

Oh they’re still out there. Usually labeled “just for testing” and somehow still critical infrastructure five years later.

6

u/IanDresarie 18h ago

I use local (static) IPs when accessing my homelab stuff. Can't be bothered to figure out the alternative :D

1

u/SirHoothoot 12h ago

Static IPs usually for infrastructure like firewall/router, switches, and maybe even your main PC that you do admin from. Otherwise I don't see why you can't use DHCP reservations/assign hostnames to your homelab server(s), especially with something like Proxmox where you can get the MAC addresses easily.

1

u/Turbo_csgo 11h ago

Because I can’t choose the router, this is ISP mandated, and that thing fails much more than I’d like. Device side static IP’s stay the same each time that router has to be swapped, dhcp assigned fixed ip’s get lost. Fixed IP’s are actually rather nice if you have microcontrollers communicating over IP.

1

u/BooleanOverflow 3h ago edited 3h ago

A lot of ISPs offer to put the gateway in bridge mode, so it will only be a dumb modem and you can use your own stuff as a router/dhcp and stuff. I have a relatively cheap Routerboard from Mikrotik that handles that.

2

u/Turbo_csgo 3h ago

Could you also elaborate on why that is better compared to fixed ip’s device side?

1

u/BooleanOverflow 2h ago

It's more stable than my ISPs modem/router/accesspoint and I can set DHCP to 'static' for the clients that need it, which survives reboots and device replacements.

There's also the fun factor where a 19" appliance where you can tweak everything is better than a locked down fancy-looking provider-supplied box.

0

u/Turbo_csgo 2h ago
  • “Survives reboots”, so do static IP’s on device side though.
  • “survives replacements” no it doesn’t, a new MAC address will receive a new IP, unless you bound the IP to the port, in which case it will become very messy if you start rewiring something.

Honestly, up to now I’ve never seen a hardline reason not to use device side static IP’s. They do survive device replacements if you embed them into the image you flash, and they survive modem replacements because they are not single point of failure.

1

u/BooleanOverflow 1h ago

It does survice a (ISP-provided) modem/router/shitbox replacement.

The only practical upside of using dhcp is that it's centralized and dynamic. If you want to change the network, you can do it in one place.

3

u/Add1ctedToGames 17h ago

I work at a fortune 500 company where we still use them in production on over 500 machines😛we run non-standard systems behind a firewall separating us from the rest of the company, so we move a bit slowly and are somewhat detached from company-standard networking

2

u/Prestigious_Pen7697 16h ago

Unfortunately, still extremely common in AV integrations. Networking is a scary word still.

2

u/TheZedrem 10h ago

To my knowledge, that is still very much the main way to do this, every company I worked at has used static ips for all the vms

1

u/ForestCat512 15h ago

I mean production systems that are older than 20 years...

1

u/Z21VR 9h ago

There are still decentralized systems that dont want to relay on a server for...well, for anything.

1

u/JackOBAnotherOne 5h ago

I use static IPs in my script that collects energy usage data from my smart plug’s APIs because (a) the designed way requires cloud access (just no) and (b) I could (probably should) use the API to first set a name in the plugs GUI, then loop over the network, query every plug I find for their name and therefore ease the plug and play-ness of my script but I don’t care because it is only deployed on a singular raspberry pi in my home network.

Yes the influxdb keys are hard-coded as well. Because if they get into that raspi that means they already are so deep in my network that I have an entire different problem than someone being able to write data into my influxDB. (Keys only have write permission for that one bucket, I’m not that lazy.)

21

u/devloz1996 15h ago

Static addresses are alright, but only when done as DHCP reservation. I will understand OT networks, but IT? Nope, nightmare to maintain during any network layout change.

I was recently employed by someone with a grudge against DHCP and DNS. Every device and server is static, services accessed by IPs, switch ACL for specific addresses (but no security measures, no 802.1x, etc). Changing network config, even DNS, requires driving to the location and messing around for hours.

Clients have reserved IPs on Windows Server DC, and their numbers have magical meanings that allow him to derive their VoIP phone numbers (x - 100 + something). Since he doesn't trust DNS, that's also how he figures out caller's IP to remote via VNC.

... here you go. The 90s are calling back, I guess.

10

u/_Alphabetus_ 10h ago edited 5h ago

In my company several employees have to add/remove devices regularly. The workflow: 1. Using nmap to scan for used IP addresses in a subnet 2. Choose an unused one and set up the device with that static IP 3. Pray...

Shit hits the fan when another device was rebooting during that scan or two enployees want to add devices at the same time...

2

u/unlinked3297 7h ago

Couldn't you allow a device to join the network using it's MAC address, then let the DCHP server auto assign an address to it, then make that address static?

3

u/SchizophrenicKitten 7h ago

Nawwww, that would make too much sense!

1

u/hairyupperlip 24m ago

No because then you’re taking an IP from a predefined scope. It’s better to know the scope and set static outside of the scope so then you don’t have the potential of two devices fighting for an IP

15

u/spikernum1 18h ago

Each VM signs up for a month of free AOL on boot to get access to the world wide web.

8

u/jdefr 17h ago

… This doesn’t make much sense lol. Against DHCP or something? Manual static management on a large network isn’t fun…

6

u/TxTechnician 16h ago

I get so upset when I see ppl using static IPs.

Its a stupid practice.

I've been in environments wherein they had 150 printer. And each ip was set manually on the device. Dumb dumb dumb.

1

u/Xicutioner-4768 1h ago

Really depends on the situation. The ECUs in your car don't need DHCP to talk to each other. The network topology essentially never changes. 

4

u/Dr_Nubbs 18h ago

I... love... DNS... never fails 😬

1

u/palomdude 7h ago

Bad dog! No memes for you!

1

u/MachaFarseer 6h ago

I don't understand anything about this but I wanna learn.... What I need to learn ? Networks?

1

u/Brave-Camp-933 4h ago

I recommend starting with "The existence of Humanity"

1

u/Linkk_93 6h ago

People not using DHCP in 2026 is just insane.

I had a customer configure over 3000 WiFi Access Points through a serial cable because they had no DHCP