Make CloneDeploy mobile

  1. 2 months ago

    Hi. i was a Fog project user, but i decide move to CloneDeploy since I'm not skilled on Linux. On FOG I'm using a script that automatically change the FOG IP every time i connect on a new network, so i can PXE Boot any computer in this network.
    My scenario is: Use CloneDeploy in a Laptop (on cable), on randoms networks that i cannot access the DHCP server, need to be able to take a laptop around to different clients and use it over their DHCP network.

    Running Windows 10 pro,
    CloneDeploy V 1.3.5
    Capture and deploy images trough PXE Boot
    Cannot access the DHCP main server

    I hope i get myself clear, sorry about my English.

  2. clonedeploy

    Oct 8 Administrator

    If you don't have access to the dhcp server and want to pxe boot, CloneDeploy Proxy DHCP is your only option.

  3. I'm reading the documentation clonedeploy.org/docs/clonedeploy-proxy-dhcp , where says "It does not need to be installed on your CloneDeploy Server, but it can if you want to" What benefits or loses on do that?

  4. clonedeploy

    Oct 8 Administrator

    There aren't any, it doesn't matter where it's installed.

  5. Ty for the fast answer, I'm on this steps now
    In the CloneDeploy Web Inteface, select Admin->PXE->Using Proxy DHCP->Yes
    Create the default global boot files when prompted.

    I see alot of options there, there is a best options to selectg for clone Windows 10 UEFI systems only?

  6. clonedeploy

    Oct 9 Administrator

    Any of the ipxe options are usually the best bet.

  7. @clonedeploy If you don't have access to the dhcp server and want to pxe boot, CloneDeploy Proxy DHCP is your only option.

    I have to differ with this....DNSmasq is working great and since its more standard on linux I think it should be the prefered option if installing clone deploy on Linux

  8. clonedeploy

    Oct 9 Administrator

    @hrumph2 yes you are correct there are other options out there. I was talking more about CloneDeploy options not 3rd party. Also this user mentioned they installed on Windows, so I was assuming the user wanted a Windows option. Finally, CloneDeploy proxy offers some advantages over DNSmasq since it can talk directly to the CloneDeploy api. Thanks for your input though, in the end, it's whatever works for you.

  9. @clonedeploy Can you take a look on my configs, i was able to run the proxy dhcp server debug mode and see the request but the boot screen not pop up on the remote computer.

    10.47.0.79 => Local laptop clonedeploy server
    10.47.0.5 => Firewall DHCP Server
    10.47.0.107 => Remote computer need to upload a image

    More info attached.....

    ;Config File For CloneDeploy Proxy DHCP Server
    
    [settings]
    
    ; LISTEN-DHCP sets the server to listen for pxe boot dhcp offers and apple netboot dhcp informs on port 67
    ; Must be true in order for Apple NetBoot to work
    ; Can be false if not using Apple NetBoot and the CloneDeploy Proxy DHCP is installed on the same server as your DHCP Server and option 60 is set to PXEClient on that DHCP Server
    ; Valid values: true | false
     
    listen-dhcp=true
    
    ; LISTEN-PROXY sets the server to listen for pxe boot proxy dhcp requests on port 4011
    ; Must be true for PXE booting
    ; Apple NetBoot does not use this port
    ; Valid values: true | false
    
    listen-proxy=true
    
    ; LISTEN-APPLE-BSDP sets the server to listen for Apple NetBoot Inform Requests
    ; Must be true to use with Apple NetBoot
    ; listen-dhcp must also be true when this is true
    ; Valid values: true | false
    
    listen-apple-bsdp=true
    
    ; INTERFACE sets the nic you want to listen on.
    ; Any interface can be specified with 0.0.0.0
    ; If running on Linux with Mono, you must use 0.0.0.0
    ; When binding to the interface, it is possible to reuse the port if there is already an existing DHCP Server on the same machine, with some limitations
    ; -- This lets you use the CloneDeploy Proxy DHCP on an isolated network with only a single machine for both DHCP services and Proxy DHCP services, but ideally should be on it's own machine with an ip helper pointing to it
    ; -- Not all DHCP servers support this, if CloneDeploy Proxy DHCP cannot bind, it will let you know
    ; -- Requests that are fowarded by a relay or ip helper, will not work when CloneDeploy Proxy DHCP is bound to the same interface that a DHCP Server is already using
    ; ----- It will only respond to requests in the same subnet / vlan
    ; Valid values: A single IPv4 address | 0.0.0.0
    
    interface=10.47.0.79
    
    ; NEXT-SERVER sets the IPv4 address of the tftp server
    ; Value is required for both PXE and Apple NetBoot
    ; Valid values: A single IPv4 address
    
    next-server=10.47.0.5
    
    ; CLONEDEPLOY-BASE-URL sets the optional url used for CloneDeploy API Calls
    ; Valid Value: Your CloneDeploy Base Url from CloneDeploy Web Interface ->Admin->Server
    
    clonedeploy-base-url=http://192.168.56.100/clonedeploy/
    
    ; CHECK-WEB-RESERVATIONS check the CloneDeploy server for static computer boot reservations
    ; Valid values true | false
    
    check-web-reservations=true
    
    ; CHECK-TFTP-CLUSTER check the CloneDeploy server for tftp cluster groups
    ; Valid values true | false
    
    check-tftp-cluster=true
    
    ; TFTP-POLLING-INTERVAL when using clustered tftp server, how often to check to see if they are up
    ; Valid values number (in seconds)
    
    tftp-polling-interval=30
    
    
    ; ALLOW-ALL-MAC sets the server to respond to all pxe boot or netboot requests or limit to only those set in the allow file
    ; Valid values true | false
    
    allow-all-mac=true
    
    ; BIOS-BOOTFILE sets the file that is loaded for legacy bios clients, both x86 and x64
    ; Path is relative to your tftp base folder
    ; If using with CloneDeploy, it should always be proxy/bios/pxeboot.0
    
    bios-bootfile=proxy/bios/pxeboot.0
    
    ; EFI32-BOOTFILE sets the file that is loaded for efi x86 clients
    ; Path is relative to your tftp base folder
    ; If using with CloneDeploy, it should always be proxy/efi32/pxeboot.0
    
    efi32-bootfile=proxy/efi32/pxeboot.0
    
    ; EFI64-BOOTFILE sets the file that is loaded for efi x64 clients
    ; Path is relative to your tftp base folder
    ; If using with CloneDeploy, it should always be proxy/efi64/pxeboot.0
    
    efi64-bootfile=proxy/efi64/pxeboot.0
    
    ; APPLE-EFI-BOOT-FILE sets the boot file on Apple NetBoot when not using a macOS NBI. Ex: The CloneDeploy Linux Imaging Environment
    ; This file is only loaded if an nbi is selected with an id of 3913 or 39131
    ; This feature enables NetBooting to both an Apple NBI and the Linux Environment while using only a single CloneDeploy Proxy DHCP Server
    ; If using with CloneDeploy, it should always be proxy/efi64/ipxe.efi
    
    apple-efi-boot-file=proxy/efi64/ipxe.efi
    
    ; APPLE-BOOT-FILE sets the boot file on Apple NetBoot when a macOS NBI is selected.
    ; Path is relative to your tftp base folder
    ; [nbi-id] is a placeholder for the selected NBI from the Apple Boot Menu
    ; If using with CloneDeploy, it should always be [nbi_id]/i386/booter
    
    apple-boot-file=[nbi_id]/i386/booter
    
    ; APPLE-ROOT-PATH sets the location of the NBI .dmg folder for Apple NetBoot - Only supports serving over http - No NFS
    ; [nbi-id] is a placeholder for the selected NBI from the Apple Boot Menu
    ; If using with CloneDeploy, it should always be http://clonedeploy-server-ip/clonedeploy/public/macos_nbis/[nbi_id]/NetBoot.dmg
    
    apple-root-path=http://192.168.56.1/clonedeploy/public/macos_nbis/[nbi_id]/NetBoot.dmg
    
    ; APPLE-VENDOR-SPECIFIC-INFORMATION sets the NBI list boot menu for Apple NetBoot
    ; If using with CloneDeploy, it should be generated from the CloneDeploy Web Interface->Admin->BootMenu->Apple NetBoot
    ; If not using with CloneDeploy, you can generate it by filling in the vendor-specific-info-generator section below and running with the --generate argument
    
    apple-vendor-specific-information=
    
    ; SERVER-IDENTIFIER-OVERRIDE sets the Server Identifier
    ; By default this value is set to the inteface value when empty, except in cases where it cannot be, such as an interface set to 0.0.0.0
    ; Valid values: A single IPv4 address
    
    server-identifier-override=
    
    ; The Following section is used to generate the apple-vendor-specific-information string for use with Apple NetBooting when CloneDeploy Proxy DHCP is ran with the --generate argument
    ; This Should Only be filled in if using without CloneDeploy
    ; It supports adding up to 5 boot options to the Apple NetBoot Menu
    ; NETBOOT-SERVER-IP sets the CloneDeploy Proxy DHCP that should be targeted when a boot Menu selection is selected
    ; NETBOOT-SERVER-IP should match either the interface value or the apple-target-ip-override value
    ; Id Values for a single CloneDeploy Proxy DHCP Server must be unique
    ; Id Values for an NBI being served from a single server must be b/w 1-4095 
    ; Id Values for an NBI being served from multiple servers for load balancing must be b/w 4096-65535
    ; An id with the a value of 3913 or 39131 will load the apple-efi-boot-file, any other value will load the apple-boot-file
    ; Name values can be any name you want to display on the Apple NetBoot Boot Menu
    ; Name values should not contain spaces or special characters
    [vendor-specific-info-generator]
    
    netboot-server-ip=
    
    apple_nbi_id_1=
    apple_nbi_name_1=
    
    apple_nbi_id_2=
    apple_nbi_name_2=
    
    apple_nbi_id_3=
    apple_nbi_name_3=
    
    apple_nbi_id_4=
    apple_nbi_name_4=
    
    apple_nbi_id_5=
    apple_nbi_name_5=
  10. clonedeploy

    Oct 10 Administrator

    Your next-server is wrong, it should be the CloneDeploy server ip.

  11. @clonedeploy and interface=10.47.0.5?

  12. C:\Program Files (x86)\clonedeploy\cd_proxyd>cd_proxyd.exe --debug
    CloneDeploy ServiceURL Is Populated. Testing API ... FAILED
    ... Web Reservations Will Not Be Processed
    ... Clustered Tftp Servers Will Not Be Processed

    Could Not Bind 10.47.0.5:67
    Ensure The Interface Is Correct And The Ports Are Not In Use

    Press [Enter] to Exit.

  13. Following this steps

    PC PXE Operation When Installed On Same Server as DHCP
    
    This method does not require any additional IP Helpers because there should already be one pointing to the DHCP server.
    
    If installing on an existing DHCP server, port 67 is already in use and the proxy cannot bind to respond to discover requests. You must set listen-dhcp to false in CloneDeploy Proxy DHCP and set option 60 to PXEClient on the DHCP server.
    
    In this mode, CloneDeploy Proxy DHCP only listens on port 4011.
    
    Apple Netboot cannot be used this way

    Din't find where set option 60 to PXEClient on the DHCP server

  14. clonedeploy

    Oct 11 Administrator

    You don't need to set option 60 in your case. Just set the interface and next-server to your CloneDeploy server ip

  15. @clonedeploy got this message

    C:\Program Files (x86)\clonedeploy\cd_proxyd>cd_proxyd.exe --debug
    CloneDeploy ServiceURL Is Populated. Testing API ... FAILED
    ... Web Reservations Will Not Be Processed
    ... Clustered Tftp Servers Will Not Be Processed

    Could Not Bind 10.47.0.5:67
    Ensure The Interface Is Correct And The Ports Are Not In Use

    Press [Enter] to Exit.

  16. clonedeploy

    Oct 11 Administrator

    According to what you posted earlier:

    10.47.0.79 => Local laptop clonedeploy server
    10.47.0.5 => Firewall DHCP Server
    10.47.0.107 => Remote computer need to upload a image

    So your next-server and interface should both be 10.47.0.79

  17. Almost there! Any way to by pass the secure boot, without turn it off ?

  18. clonedeploy

    Oct 11 Administrator

    Not with PXE boot. USB should work with secure boot.

 

or Sign Up to reply!