Group Details Private


  • RE: Fog on Existing DHCP server

    pfsense is a good option, but not the only one.

    If you are using a soho (home router) that doesn’t support dhcp booting options, you can use / install a service on the FOG server called dnsmasq. This is a dhcp proxy service that will supply the boot information only to the pxe booting client.

    Just install dnsmasq from your linux distro’s repository. Then edit / create a file called ltsp.conf in the /etc/dnsmasq.d directory. In that ltsp.conf file put in the following :

    # Don't function as a DNS server:
    # Log lots of extra information about DHCP transactions.
    # Set the root directory for files available via FTP.
    # The boot filename, Server name, Server Ip Address
    # Disable re-use of the DHCP servername and filename fields as extra
    # option space. That's to avoid confusing some old or broken DHCP clients.
    # inspect the vendor class string and match the text to set the tag
    # Set the boot file name based on the matching tag from the vendor class (above)
    # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
    pxe-prompt="Booting FOG Client", 1
    # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
    # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
    # This option is first and will be the default if there is no input from the user.
    pxe-service=X86PC, "Boot to FOG", undionly.kpxe
    pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
    pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

    Don’t forget to replace <fog_server_ip> in the above text with the IP address of your fog server. The tag appears many times.

    If your distro has a config file in that directory, remove it and only place one config file (ltsp.conf) in that directory path.

    One other point to check, make sure the version of dnsmasq installed is 2.76 or later. You can find out by using the following command: dnsmasq -v

    posted in FOG Problems
  • RE: pxe boot/fog menu

    Interesting, I have not seen that with any Dells we have. For the FOG iPXE menu to “disappear” that would mean the iPXE kernel would either have crashed or you have already register the target computer and scheduled a task for it.

    Lets start out with some basics.

    1. What you do have configured for dhcp options 66 and 67. Also be sure you don’t have dhcp option 60 set.
    2. What model of dell computer is this?
    3. Is this computer in uefi or bois mode?
    4. Is the target computer and the fog server on the same subnet?
    posted in FOG Problems
  • RE: Issues with Fog 1.5.2

    @k-hays Not for the worker threads. We are finding (so far) 256MB per php-fpm worker is working well. Run with these setting and for sure provide feedback. Once we get these number working stable on all that are having issues we will include them in the fog 1.5.5 update.

    posted in FOG Problems
  • RE: Issues with Fog 1.5.2

    @k-hays Please, only change MAX server AND make sure you added the memory line for 256M. The rest of the values are ok at 6.

    posted in FOG Problems
  • RE: Issues with Fog 1.5.2

    @k-hays said in Issues with Fog 1.5.2:

    max_spare_servers = 6

    Set that value to 40 and make sure you have the memory allocated to 256M and you should be good to go. Understand this fix will only address imaging and not your initial post of html in the FOS screen.

    posted in FOG Problems
  • RE: Issues with Fog 1.5.2

    @k-hays Max should be 40 as I posted below.

    php_admin_value[memory_limit] = 256M
    pm.max_requests = 2000
    pm.max_children = 40
    pm.min_spare_servers = 6
    pm.start_servers = 5
    posted in FOG Problems
  • RE: rEFInd PXE booting issue

    @jj-fullmer Very nice and quick reply from the rEFInd Developer (they are almost as fast as the FOG Developers to respond).

    Do you have the time to work with the refind developer to figure out the root of the issue, since you have the hardware? The results will help both FOSS projects.

    posted in Hardware Compatibility
  • RE: rEFInd PXE booting issue

    @Developers Please be aware of JJ Fullmer’s post on issues with refind 0.11.1 and 0.11.2. Reverting back to 0.11.0 appears to have addressed his issue with HP.

    @JJ-Fullmer Great find!!, please let us know what the rEFIn’d developers respond with.

    posted in Hardware Compatibility
  • RE: FOG 1.5.4 Windows 7 UEFI Image Capture posted in FOG Problems
  • RE: FOG 1.5.4 Windows 7 UEFI Image Capture

    @ty900000 Server OS and Version? FOG version?

    posted in FOG Problems