USB Boot static IP

  • Hi again and congratulations to the new release 1.1.0!

    I would have the need for beeing able to configure the usb boot image to use a fixed static ip, subnetmask, gateway, dns.
    Would be cool if one could configure all this in the WebGUI and then create the USB image.
    Or is there a simple way already I missed?

    Problem is that we have many very small subnets /29 and no free IPs left for an additional DHCP server.

    Additional the gateway would be a Cisco ASA, but is not able to provide boot options (I don't get it why the hell they offer mostly everything but strip that ...). And the ASA already acts in some subnets as simple DHCP-Server so can't be configured to be a relay.

  • I'll try and get this in when I can. What options would you want to set in the WebGUI. If we set all ip info there, then we can only use 1 usb boot at a time.

  • Thanks for the quick reply!


    For now it would be totally sufficient to have [b]one fixed IP[/b] for the boot image to be able to boot one at a time. This still would make it possible to create multiple different USB-Boot images with different IPs as long as it is only a small number of bootimages that one needs. So that should be way easier as the following.


    If it would be possible to have something like a complete list / mac to IP mapping on the bootimage, one would need to create that list.

    [h][b]How to assign IP while boot?[/b][/h]
    Using a created udev-script or systemd-networkd.
    I was thinking of using systemd-networkd and create the config files for each mac:

    .link files for physical devices = name deviced from mac-address
    .network files = match name = the one created from mac-address












    [h]Where to store the information for the list?[/h]
    In the central computer imformation, where we already have stored the mac address.
    There could be additional fields that allows to store a fixed IP address (+ gateway, Subnetmask ...) if one wants to create a bootimage with fixed IP addresses.
    Then one could mark every computer that he wants to create a single bootimage for or simplier make a bootimage and create a list from all computers that have this information stored.

  • So the simple solution would be easy, the complex one not so much. First issue is that systemd is not used, it is busybox, but I think some basic scripting could accomplish the same thing. The biggest issue is how to get the list into the boot image. It is not accessible directly from the client iso, it needs to be mounted in linux.

  • Getting the file into the bootimage:
    As the current process already involves to manual copy the contents from "clonedeploy\web\private\client_iso\output" to the USB-Drive, there could also be the generated list?

    Then it would be already on the USB-Stick / CD-ISO. And a script could check if the file exists and contains the MAC-Address of the current booted machine, it would use those information?

  • I was thinking about static IP addressing as well, but I had the thought of escape button during DHCP lookup and allow the user to manually enter addressing. Probably would only need IP address / gateway / and dns.

  • Some progress has been made here. static ip's can now be passed in as kernel args. Also if dhcp times out you will be prompted for static info. In 1.2.0.

    The complex method is something I may revisit at a later time.

  • Thank you for the hard work you put into this software. I currently have Clonedeploy working fine on a Windows 2012 server but am on a static network (No DHCP). Could you give an example of how the kernel argument would look like for entering a static IP before creating the ISO/USB boot disk?

  • [code]cd_net_ip= cd_net_netmask= cd_net_gateway=[/code]