How to set Option 67

  1. 5 months ago

    First time new poster. Found clone-deploy and I am evaluating the tool for manufacturing boards with a custom image. I am booting into EFI and the NBP file downloads correctly. YEAH! However it does not boot. I suspect that it needs information in option 67 bootfile name (path) so the target machine can find it. In looking at the wireshark transaction (sorry I can paste the log in here, test network) I see option 60 but not 67 is being set. The target does request that information? How do I set option 67? Following is the cut and paste from the target computer.

    >>Start PXE over IPv4.
    Station IP address is 192.168.1.20

    Server IP address is 192.168.1.10
    NBP filename is pxeboot.0
    NBP filesize is 409001 Bytes

    >>Checking Media Presence......
    >>Media Present......
    Downloading NBP file...

    Succeed to download NBP file.
    EFI Shell version 2.31 [5.9]
    Current running mode 1.1.2
    Device mapping table

  2. clonedeploy

    May 1 Administrator

    Since it's processing pxeboot.0, that means all dhcp options are set correctly. Are you using clonedeploy proxy dhcp? What are your pxe modes set to?

  3. I have tried regular PXE boot and proxy DHCP. Our target is 32 bit atom. Here is the list I have tried.
    Pxelinux
    Ipxe
    Syslinux_efi
    Ipxe_efi32
    Winpebios_32
    Winpe_efi32

    I appreciate the quick response.

  4. clonedeploy

    May 1 Administrator

    It is odd that none of those worked and it's going to be difficult to say where it's going wrong without the packet capture. It is possible that this machine does in fact not work with any of these bootloaders. I would like to verify the architecture being sent from the client. If you run proxy dhcp in debug mode, can you post the output of a pxe boot?

  5. Interesting I switched to
    3.18.1 kernel
    debug.xz
    Rebooted my target, the file downloaded but never executed. I suspect the file loads properly but never executes. So I never got any debug output. This is on a small board using the ATOM processor.

    I found this on an other forum
    When using UEFI, Option 67 must be set to wdsmgfw.efi (No BIOS support)!

    Here is a more complete log from the serial port.

    >>Checking Media Presence......
    >>Media Present......
    >>Start PXE over IPv4.
    Station IP address is 192.168.1.20

    Server IP address is 192.168.1.10
    NBP filename is pxeboot.0
    NBP filesize is 409001 Bytes

    >>Checking Media Presence......
    >>Media Present......
    Downloading NBP file...

    Succeed to download NBP file.
    EFI Shell version 2.31 [5.9]
    Current running mode 1.1.2
    Device mapping table
    blk0 :HardDisk - Alias (null)
    PciRoot(0x0)/Pci(0x17,0x0)/HD(1,MBR,0x424D4550,0x800,0xA64800)
    blk1 :HardDisk - Alias (null)
    PciRoot(0x0)/Pci(0x17,0x0)/HD(2,MBR,0x424D4550,0xA657FE,0x3CA002)
    blk2 :HardDisk - Alias (null)
    PciRoot(0x0)/Pci(0x17,0x0)/HD(2,MBR,0x424D4550,0xA657FE,0x3CA002)/HD(1,MBR,0x00000000,0xA65800,0x3CA000)
    blk3 :BlockDevice - Alias (null)
    PciRoot(0x0)/Pci(0x17,0x0)

  6. I am going to bring in an old laptop and make sure I can get the image from it correctly. Will do that tomorrow. However I still suspect there is something not quite right about my target.

  7. Edited 5 months ago by xintersecty

    Here are the results in testing the old Thinkpad T43. It uses
    Broadcom UNDI PXE-2.1 V7.7.5
    Broadcome Base Code PCE-2.1 v1.0.1

    It gets the IP address from the DHCP server (clonedeploy). I have the server setup as Proxy DHCP and I went through pxelinux and ipxe modes using the debug kernel using the 3.18.1, 4.4.3, and 4.5 versions of the kernel versions under the BIOS-ipxe setting.

    It downloads the file correctly but does not execute the NBP. So I am leaning towards the setup in clonedeploy. I suspect I have a subtle error in configuration.

    So what logs/setup can I attach to help you?

  8. clonedeploy

    May 2 Administrator

    I would start by removing the proxy dhcp server for now. Just one less thing to troubleshoot. It looks like you are using the included dhcp server on a private network? Setup that using the client boot method documentation. In CloneDeploy set using proxy dhcp to no and set the pxe mode to pxelinux. Let's start there.

  9. Well then to my pleasant surprise that combo worked. However I don't remember my root password on this machine when I tried to upload the image. Like it has been years since i have used it. So my atom test board is using EFI version 2.31 [5.9]. And it's not executing the NBP. That means there is a configuration issue in the EFI and it's not mounting the memory space the NBP was stored. i have written to the manufacture and to see if they have any instructions on the UEFI and BIOS boot.

  10. Well darn it. The username and password was the clonedeploy system (old laptop). I was thinking it was the password to root on my harddrive. It failed to mount the SMB on first boot, second boot, it could not update the task status.

  11. I am working through the SMB troubleshooting guide as listed one of postings.

  12. Edited 5 months ago by xintersecty

    OK, one of the things I found was that the SMB share was not created properly on my test system. My company requires password be some magical combination of numbers, one uppercase letter and more letters.
    For example I used blahz
    In making my share I had to use 1234Blahz

    Found the section on changing the password in distribution points. And now it's creating an image.

  13. I was successful at getting Clone Deploy to suck down an image from a laptop. So that means my installation is good. Now back to my Atom machine

  14. I have attached the wireshark capture of the initial conversation between clonedeploy and the target. Looking at the definitions of the options and the and the usage of the options, I would say clonedeploy is providing enough information.

    No. Time Source Destination Protocol Length Info
    10 4.943875 192.168.1.10 255.255.255.255 DHCP 336 DHCP ACK - Transaction ID 0x316ae200

    Frame 10: 336 bytes on wire (2688 bits), 336 bytes captured (2688 bits) on interface 0
    Ethernet II, Src: Dell_dc:3e:dc (00:26:b9:dc:3e:dc), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
    Internet Protocol Version 4, Src: 192.168.1.10, Dst: 255.255.255.255
    User Datagram Protocol, Src Port: 67, Dst Port: 68
    Bootstrap Protocol (ACK)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x316ae200
    Seconds elapsed: 0
    Bootp flags: 0x8000, Broadcast flag (Broadcast)
    Client IP address: 192.168.1.20
    Your (client) IP address: 192.168.1.20
    Next server IP address: 192.168.1.10
    Relay agent IP address: 0.0.0.0
    Client MAC address: AdlinkTe_18:d5:a7 (00:30:64:18:d5:a7)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name: pxeboot.0
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (ACK)
    Option: (54) DHCP Server Identifier
    Option: (1) Subnet Mask
    Option: (3) Router
    Option: (6) Domain Name Server
    Option: (44) NetBIOS over TCP/IP Name Server
    Option: (51) IP Address Lease Time
    Option: (58) Renewal Time Value
    Option: (59) Rebinding Time Value
    Option: (255) End
    Padding: 0000

  15. clonedeploy

    May 2 Administrator

    It would be helpful to know the value of option 93 from this capture.

    Frame 8: 401 bytes on wire (3208 bits), 401 bytes captured (3208 bits) on interface 0
    Ethernet II, Src: AdlinkTe_18:d5:a7 (00:30:64:18:d5:a7), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
    Internet Protocol Version 4, Src: 0.0.0.0, Dst: 255.255.255.255
    User Datagram Protocol, Src Port: 68, Dst Port: 67
    Bootstrap Protocol (Request)
    Message type: Boot Request (1)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x316ae200
    Seconds elapsed: 0
    Bootp flags: 0x8000, Broadcast flag (Broadcast)
    Client IP address: 0.0.0.0
    Your (client) IP address: 0.0.0.0
    Next server IP address: 0.0.0.0
    Relay agent IP address: 0.0.0.0
    Client MAC address: AdlinkTe_18:d5:a7 (00:30:64:18:d5:a7)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Request)
    Option: (54) DHCP Server Identifier
    Option: (50) Requested IP Address
    Option: (57) Maximum DHCP Message Size
    Option: (55) Parameter Request List
    Option: (97) UUID/GUID-based Client Identifier
    Option: (94) Client Network Device Interface
    Option: (93) Client System Architecture
    Option: (60) Vendor class identifier
    Option: (255) End

  16. Good Question, ran another trace and pulled out that option

    Option: (97) UUID/GUID-based Client Identifier
    Length: 17
    Client Identifier (UUID): 03000200-0400-0500-0006-000700080009
    Option: (94) Client Network Device Interface
    Length: 3
    Major Version: 3
    Minor Version: 16
    Option: (93) Client System Architecture
    Length: 2
    Client System Architecture: EFI BC (7)
    Option: (60) Vendor class identifier
    Length: 32
    Vendor class identifier: PXEClient:Arch:00007:UNDI:003016

  17. clonedeploy

    May 2 Administrator

    Seems like it should be working. For your pxe mode I would try all of the efi modes to see if one works. If you are using a 32 bit efi you must also select the 32 bit kernel. The same goes for 64bit.

  18. understood. Your help on solving and setting up clonedeploy has been immensely helpful. Currently I am working with the manufacture to resolve this problem. Once I have resolution I will add it back into the thread.

 

or Sign Up to reply!