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

Configure iVentoy as netboot-Option in boot menu

Scheduled Pinned Locked Moved
Tutorials
3
5
5.4k
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.
  • Y
    youzersef
    last edited by youzersef Apr 25, 2024, 11:50 AM Apr 25, 2024, 5:36 PM

    firsteval i will thank @baovipboy156 and @george1421 for helping me to make this configuration.

    iVentoy is the next generation of Ventoy. It is a new netboot solution which could be used to run iso files directly from the PXE-Boot. Just put the ISO-Files in the right folder then you can see it as new boot option on iVentoy. It is very useful you do not have to set every OS on PXE boot menu of Fog-Server.

    Attention: It is free to use till 20 devices and you are not allowed to use it for commercial purposes. For more information https://www.iventoy.com/en/doc_edition.html

    in my example:
    my dhcp Server: 192.168.111.1
    my Fog Server: 192.168.111.125
    my iVentoy Server: 192.168.111.122

    Remember this is the basic configurations “same vlan”. that is why i will use the following configuration on iVentoy Server:

    76ffcab1-1b08-4796-801e-15288dbe2bdb-grafik.png

    after save start the tftp boot service from “Boot Information”.

    Then we have to add new boot option on Fog Server:

    Menu Item       iVentoy
    Description     iVentoy
    Parameters      set newserver:ipv4 192.168.111.122 # ip adresse of iVentoy
                    set newbootfile iventoy_loader_16000
                    set net0/next-server ${newserver}
                    set net0/filename ${newbootfile}
                    chain tftp://${newserver}/iventoy_loader_16000
    Menu Show       with  All Hosts                
    

    in the dhcpd.conf file Server edit the classes:

        class "UEFI-32-1" {
            match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
            if exists user-class and option user-class = "iVentoy" {
                filename "iventoy_loader_16000_uefi";
                next-server 192.168.111.122; # IP Address of iVentoy
            } else {
                filename "i386-efi/ipxe.efi";
            }
        }
     
        class "UEFI-32-2" {
            match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
            if exists user-class and option user-class = "iVentoy" {
                filename "iventoy_loader_16000_uefi";
                next-server 192.168.111.122; # IP Address of iVentoy
            } else {
                filename "i386-efi/ipxe.efi";
            }
        }
     
        class "UEFI-64-1" {
            match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
            if exists user-class and option user-class = "iVentoy" {
                filename "iventoy_loader_16000_uefi";
                next-server 192.168.111.122; # IP Address of iVentoy
            } else {
                filename "ipxe.efi";
            }
        }
     
        class "UEFI-64-2" {
            match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
            if exists user-class and option user-class = "iVentoy" {
                filename "iventoy_loader_16000_uefi";
                next-server 192.168.111.122; # IP Address of iVentoy
            } else {
                filename "ipxe.efi";
            }
        }
     
        class "UEFI-64-3" {
            match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
            if exists user-class and option user-class = "iVentoy" {
                filename "iventoy_loader_16000_uefi";
                next-server 192.168.111.122; # IP Address of iVentoy
            } else {
                filename "ipxe.efi";
            }
        }
     
        class "Legacy" {
            match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
            if exists user-class and option user-class = "iVentoy" {
                filename "iventoy_loader_16000_bios";
                next-server 192.168.111.122; # IP Address of iVentoy
            } else {
                filename "undionly.kkpxe";
            }
        }
    }
    

    restart your DHCP-Server and test your configuration on fog Client.

    b9b1a6af-a1f0-4d29-b637-b9943ecaadd4-grafik.png

    76d43d8e-c752-4956-818e-b39dafc9cfe1-grafik.png

    and after i boot with debian 🙂
    796dc767-3ab1-459f-92a2-d1b99e70c365-grafik.png

    Windows 11

    003891ec-1a32-4d4b-acf4-96e9a439e298-grafik.png

    have a nice day 🙂

    1 Reply Last reply Reply Quote 1
    • Y
      youzersef
      last edited by Apr 25, 2024, 5:43 PM

      Bonus: you could make auto install Scripts “unatended.xml, preseed.cfg, etc…”
      for more information: https://www.iventoy.com/en/doc_autoinstall.html

      1 Reply Last reply Reply Quote 0
      • L
        llino
        last edited by May 1, 2024, 10:52 PM

        My home configuration network I have a pfSense box and a hypervisor with a fog server on a VM i’m thinking of adding another virtual Network to the to my fog server so I can run iventoy on another IP how do I configure the DHCP server on my PFsense box. The PFsense has only Next Server ip configurations

        G Y 2 Replies Last reply May 2, 2024, 12:08 AM Reply Quote 0
        • G
          george1421 Moderator @llino
          last edited by May 2, 2024, 12:08 AM

          @llino said in Configure iVentoy as netboot-Option in boot menu:

          i’m thinking of adding another virtual Network to the to my fog server so I can run iventoy

          Just be aware that FOG was not designed to have 2 imaging network interfaces. So it will be difficult to have fog respond to both subnets independently.

          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 0
          • Y
            youzersef @llino
            last edited by May 2, 2024, 6:07 PM

            @llino

            i do not know how could you do it on web gui, but i can tell you how clould you deactive the web gui configuration file and instead use the CLI to edit the dhcpf.conf file directry then i will work. But remember after that any changes on webgui will not be effected that is mean you have put your new changes over CLI.

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

            298

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project