Re: How to set up dhcpd.conf to serve different UEFI files per OS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/4/23 16:25, Barry wrote:
I have always seen this done by having tooling that read a database of hardware mac addresses mapped to config.

With that setup you “just” edit the database to switch the os you want and rebuild
your dhcpd/tftpd config.
Unfortunately, the vast majority of my systems are virtual machines, so the MAC addresses are dynamically generated. And even with the physical servers, I go back and forth between RHEL and Fedora on a pretty regular basis. So that MAC address mapping doesn't necessarily stay the same.

I think the easiest thing in my little environment is to write a little shell script that copies the RHEL or Fedora shim.efi to /var/lib/tftpboot before I kickstart a machine. I suspect that it will take a little bit before I do it out of habit, but I install machines so frequently for different projects that it will become a habit pretty quickly.

I really wish that there was something in the OS that would identify itself when it sends a DHCP broadcast. I've read up https://kb.isc.org/docs/isc-dhcp-44-manual-pages-dhcp-options and it suggested that I add:

set vendor-string = option vendor-class-identifier;

to my dhcpd.conf, and I tried it. But all that I see in the logs when I get a dhcp request is:

lease 172.31.100.165 {
  starts 0 2023/06/04 21:55:20;
  ends 0 2023/06/04 22:55:20;
  cltt 0 2023/06/04 21:55:20;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet 30:e1:71:51:24:18;
  uid "\0010\341qQ$\030";
  set vendor-string = "anaconda-Linux";
  set vendor-class-identifier = "anaconda-Linux";
}

I feel like there's more info in the dhcp requests than I know how to find. Still digging.
--
Thomas
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux