Comment on Going nuts with networking of VMs on Proxmox (SOLVED)

• trilobite@lemmy.ml ⁨6⁩ ⁨days⁩ ago

  Maybe I’m misunderstanding but what I mean is that I assign static IP via DHCP based on the MAC. I’m not setting static IPs at client level. i.e MAC address on VM1 is XX:XX:XX:XX so I set this MAC address in DHCP to correspond to IP 192.168.20:XX so that the machine gets a unique IP all the time. Is this what you meant?

  source
• Eggymatrix@sh.itjust.works ⁨6⁩ ⁨days⁩ ago

  Dhcp and ensuring it works is someting I don’t care about. I tell the kernel wich packets it should be interested in and how to sign itself and that will be it thank you very much.

  I configure static routes and have all my machines and network segments neatly arranged in my database. I setup a new machine I know exactly what address it should have,it goes up and until it has a problem it will keep the address it was installed with.

  Its 2026 I work like that, you can have your opinions I have mine. The difference is that I depend on one less thing that I don’t care about, so I have more profit margin.

  source

  • tiptoes@sh.itjust.works ⁨6⁩ ⁨days⁩ ago

    Very old school; yes you can certainly do all of that and track all of that yourself. We all used to do it that way……But it’s 2026….just as you’d use a real editor rather than edlin, or password managers rather than text files, the new ways ARE better, easier and more consistent. Making sure dhcp works is one of the modern (honestly not that modern) basics that make sure your network is set up properly and isn’t hiding some misconfiguration gremlins that only work because of some static ip and route workaround you implemented years ago and worked “until now”.

    source

    • Eggymatrix@sh.itjust.works ⁨5⁩ ⁨days⁩ ago

      You can have some weird workaround creep up yesrs later also with dhcp and dns ,😉

      source

      • tiptoes@sh.itjust.works ⁨3⁩ ⁨days⁩ ago

        Heh true enough. And you can run into issues with package updates breaking something. But hopefully that breaks things for others too so there’s some shared misery there rather than just having to curse your past self for decisions you no longer remember? 🤣

        source
• warmaster@lemmy.world ⁨6⁩ ⁨days⁩ ago

  I don’t know what I’m doing, please explain.

  source

  • tiptoes@sh.itjust.works ⁨6⁩ ⁨days⁩ ago

    DHCP can be set to specifically assign the same IP to specific devices, reserving them and ensuring that no other systems will use the same IP accidentally. So your servers will consistently get that same IP address assigned to them every time, no worry about the ip address changing unexpectedly.

    source

    • warmaster@lemmy.world ⁨5⁩ ⁨days⁩ ago

      Oh ok, it’s what I did. I set the client’s IP as fixed on my router.

      source
    • trilobite@lemmy.ml ⁨6⁩ ⁨days⁩ ago

      Can I just check with @tiptoes@sh.itjust.works and @Eggymatrix@sh.itjust.works that what I’m doing is what you are saying.

      I’m not setting static IPs at client level. Would be a nightmare. What I do is assign IPs on the DHCP server i.e MAC address on VM1 is XX:XX:XX:XX so I set this MAC address in DHCP to correspond to IP 192.168.20:XX so that the machine gets a unique IP all the time. Is this what you meant? I thought everyone would be doing this nowadays as it so easy to manage, except when something goes wrong like in this case.

      source

      • Eggymatrix@sh.itjust.works ⁨5⁩ ⁨days⁩ ago

        No what I meant is I don’t use dhcp at all, but apparently I am an old gremlin and all these youngsters do it some variation of your way. If you want ro do it like that I leave you with them.

        No worries, I just don’t want to get you confused

        source