@AdrianW There isn’t a -M option in the ipxe menu you posted.

To add a little clarity

1. What were you doing when it threw this -M error? Just booting into the ipxe menu to register or where you trying to image?
2. Do you get the same results when just booting into register or only when imaging?
3. Can you get A computer to fail with the -M error message and then run Tom’s query again but with the mac address of the computer that threw the error like this http://10.0.0.1/fog/service/ipxe/boot.php?mac=00:00:00:00:00 where 00:00:00:00:00 == the mac address of the computer that generate the error.

I have seen sometimes users naming the image name with something like “Win10 -May2020” Might confuse the iPXE boot loader.

I thought of a bit of an easier way to explain the field mapping between the kernel parameters ( cat /proc/cmdline ) and the grub menu. Here is a graphic that explains how to map the values between the two different booting methods.

@Duncan said in Very slow cloning speed on specific model:

vme_core.default_ps_max_latency_us=0 - not a valid identifier

First of all let me say excellent matrix. It looks like the latency of 0 does the trick without having to use the nvme-cli command.

Second thing the above error message is not really an error, its a spurious message because of the way FOG converts kernel parameters into variables. The kernel parameter apparently does its job, but throws that warning which can be ignored.

Again, well done with the truth table matrix. So it looks like you can go back to using the standard fog kernel but just place the kernel argument nvme_core.default_ps_max_latency_us=0 in the global kernel parameters in the FOG Configuration -> FOG Settings menu.

@ty900000 said in FOG/Apache PKI/Certificate Authentication:

Would it be possible to log into FOG using PKI certificates, rather than the local database or LDAP?

Since I worked on the ldap plugin for fog back in the day, I’m going to say no, unless someone creates a custom plugin. The issue is that FOG needs a named user in its local database for authentication. What was done in the ldap plugin is when a successful ldap authentication was created a temporary user was created in the fog user database. Authentication was done by ldap, but internally with FOG there was a named user in the database. Understand the ldap plugin has been improved since I was working with it, but back then this is how we got around a few issues.

It may be possible to use the ldap plugin as a template for the pki certificate authentication, I simply don’t know. But (IMO) it will take a bit more than just making apache happy.

@ziolucione Ok this part has a few steps but is not hard. What you need to do as a test is to take a registered computer and setup a debug deploy of the image you are interested in quick deploying. (it would probably be faster to use a wired connection for this, but what ever works). When you are dropped to the FOS Linux command prompt key in the following cat /proc/cmdline That will print out the kernel parameters used to call that image.

Now when I created the grub menu for that wireless usb boot I created a menu entry 5, that is the template you need to populate with the values collected from the cat cmdline command. You will need image name, image type from your debug deploy image into that option 5 in the grub menu. You can make more grub menu entries by just copy and pasting the section 5 menu entry. The order the menu items are in the grub menu is the order they will be displayed when the system usb boots.

I can give you a hint if you want to edit the grub menu on a windows computer, use notepad++ and not windows notepad. Windows notepad adds in windows specific characters that sometimes confuses linux applications.

@franck25 said in How to boot uefi on ltsp server via ipxe fog:

chain tftp://10.20.11.203/ltsp/amd64/pxelinux.0

While I don’t know ltsp (I’m aware of the project), I can tell you that pxelinux.0 is a bios boot loader. Its akin to undionly.kpxe. For uefi lets assume that ltsp has a uefi boot loader (might end in .efi or something else since they are using syslinux it may end with a .0 too). With fog we use undionly.kpxe for bios and ipxe.efi for uefi systems using the ipxe boot strap program. For syslinux the same rules should apply.

I don’t have a clue, but could figure it out how to setup a dhcp forwarder on the Aruba/Procurve switch. But I would have to say, if you have a single dhcp server today AND you have vlans in place then you should have a dhcp-helper/dhcp-relay service already installed on your vlan/subnet router. The only reason why you would need to change this service is if you are running dnsmasq service on your fog server (something you would intentionally turn on and configure). If you are not using dnsmasq then changing the dhcp-relay service is not needed.

Can you explain a bit more about what issue you are having?

@george1421 I see linux mint on virtual box. Its probably not the Debian 10.2 issue that was just discovered.

Where we usually run into problems with this process is someone will think its a good idea to change the linux user fogproject’s password. That causes the upload to fail during image capture with the ftp error and then can’t update the database error. If you didn’t touch the linux user fogproject then there is something else going on.

Lets have you run through this tutorial just to be sure that everything is in sync. If you have already done this successfully then we will need to dig a bit deeper. https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

What host OS is the FOG server running on? Debian 10.2?

@franck25 said in How to boot on fog with bios legacy and uefi on a computer park ???:

dhcp-range = <10.20.11.201> Proxy
If you have an idea ??

dhcp-range = <10.20.11.201> Proxy is part of the problem. You need to replace the greater than and less than signs because they are part of the label and should not be in the config file. The correct answer is

dhcp-range=10.20.11.201,proxy (also don’t miss the comma after the IP address). Nowhere in your config file should the greater than, less than wrap your IP addresses.

Edit: George1421 == to slow… Sebastian for the win!!