• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Use of different ipx files between different hardware

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    2
    3
    234
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • EazisE
      Eazis
      last edited by

      I have already a long time a problem with my DHCP on all clients (EEETop ASUS ASUSPRO A41GAR) .

      My DHCP config is this:

      class "UEFI-64-1" {
          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
         #filename "ipxe.efi";
         filename "snponly.efi";
      }
      

      The system EEETop ASUS ASUSPRO A41GART needs to use snponly.efi and the system EEETop ASUS E1600WK needs to use ipxe.efi.
      All the other system can also use ipxe.efi.

      I have also tried other efi files but there is not any file which works for all the system.

      When this happens my collegue ask me to change the dhcp settings and restarting the dhcp service, but when i’m a day off they have problem to image such system who needs snponly.efi

      How can i solve this problem?

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @Eazis
        last edited by

        @Eazis the Arch value is probably not unique enough for your needs. arch 7 defines one of the uefi flavors. The likelihood that both of your systems being the same uefi type is pretty high.

        There is something else that might be a bit more hardware specific. That value is the uuid field. I can tell you that for Dell computers the uuid is model specific. Actually the first 4 characters of the uuid is Dell spelled backwards in ascii.

        So how can you tell the system’s uuid? Use wireshark on a witness computer connected to the same subnet. Start wireshark and use a capture filter of port 67 or port 68 or use a display filter of bootp With wireshark running pxe boot the target computer. You should see 4 or more packets. Look at the DISCOVER packet, this is the target computer saying “hey I’m this come configure me” In the discover packet is the uuid field. Compare these uuid fields between the two different hardware in question as well as 2 of the same model of computers. With that info you can create a custom dhcp class filter to send the appropriate boot file for the unique uuid system.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 1
        • EazisE
          Eazis
          last edited by

          @george1421 Ok thanks for your reply. In the past i already did some research and found the arch 7 flags.

          I will check out the uuid and come back with results. Thanks.

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          148

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project