@Tom-Elliott
Of course, it’s disabled. 😉

Do you think writing this in fog.man.reg after line

[[ $exists != "#!ok" ]] && handleError "Unable to register host: $exists ($0)\n Args Passed: $*"

could do it :

host="" imageid="999" blDoAD="Y" realdoimage=$(echo -n 1 | base64) res="" user64=$(echo "fog" | tr -d '\012' | base64) pass64=$(echo "password" | tr -d '\012' | base64) while [[ $res != "#!ok" ]]; do echo -n " * Enter hostname for this computer: " read host if [[ ${#host} -gt 15 ]]; then host=${host:0:15} echo " | Truncated to 15 characters: $host" usleep 2000000 fi host=$(echo $host | base64) res=$(curl -Lks --data "host=$host" ${web}service/hostnameloop.php 2>/dev/null) [[ $res != "#!ok" ]] && echo "$res" done dots "Attempting to register host" res="" while [[ -z $res ]]; do res=$(curl -Lks --data "sysuuid=${sysuuid}&mac=$mac&advanced=$(echo -n 1 | base64)&host=$host&imageid=$imageid&doimage=$realdoimage&doad=$blDoAD&username=$user64&password=$pass64" ${web}service/auto.register.php 2>/dev/null) echo "$res" usleep 2000000 done . /bin/fog.inventory usleep 2000000

@george1421 I have run all test and first, there were a firewall rule that were blocking TFTP from the FOG server then after running more test, I realised that it’s not link to hardware or sofware on the server.
During test, I just changed the port on the switch next the computer to keep most of the hardware between server and client.
On same vlan I run at 450 Mbits/s (around 50 mo/s) and when I change vlan, I run at 150 Mb/s only.
And under 20 mo/s max with Windows TFTP client so I give up using it to run more tests.
Colleagues says there is not QOS but there is definitly something reducing the speed.

a06abb6b-6197-402f-ba10-c8be4fddc41a-image.png

@george1421 Rebuild to last version didn’t fix the problem.
@Tom-Elliott Exit type to EXIT give a “chainloading failed…”

using snponly.efi fixed the problem.

Thank you for your help.

@Sebastian-Roth
I think to know what is blocking.
I have to change vlan and fog IP adress to make updates but it use IP parameter in the updateDB() function :

wget --no-check-certificate -qO - --post-data="confirm&fogverified" --no-proxy ${httpproto}://${ipaddress}${webroot}management/index.php?node=schema >>$error_log 2>&1

I think -X with help to finish install.

I use WAPT to deploy softwares but i don’t understand your use case.
Why not just deploy WAPT agent and use command like “wapt-get install tis-yourPackage” ?

@jmeyer Having a FOG server with a dual nic is a standard and supported configuration for installing FOG.

There are a few things you need to know/do before installing FOG.

Know the linux kernel names of your network interfaces. You can see this by using the following command ip a s Identify the name of your business network interface and your imaging network interface. Document these names. Make sure your imaging network interface is configured for a static IP address. FOG does not like having the imaging network interface IP address changing once FOG is installed. Make sure your business network interface has a default route defined so that it can get to the internet. Confirm that your fog server has internet access. Make sure your imaging network interface does not have a default route defined.

Now use the git method to download the installer files onto your FOG server.

Install FOG. During the installation process you will be prompted for the linux name of your imaging network interface. Key that in when requested. You will also be prompted to if you want to install a dhcp server. Answer yes to this. The fog installer will only bind the dhcp server to the imaging network interface leaving your business network interface alone during the installation of FOG. There will be no conflicts on the business side since fog will only focus on the interface you said that is your imaging network.

@jmeyer said in Fresh install debian 11:

Yes. I’m an running Debian on a Qnap with Container Station.

Have you ever had FOG running on that before? NFS can be an issue in container virtualization. It definitely is on Proxmox when you use the default settings. I don’t know about Qnap.

@Sebastian-Roth We have find out that bios mode had to set to “Legacy Support” with priority on “UEFI First” and not with bios mode on “UEFI”.
Problem wasn’t coming from FOG.

Sorry and thank you for your help.

@Tom-Elliott Perfect ! Thank you.

@jmeyer Just pushed the fixes to working-1.6 as well.

@jmeyer I am marking this solved as we have not heard back on this. Feel free to update this topic if you are still working on this and need help.

@Tom-Elliott Fast as always. Thank you !

You should be able to use the original refind.efi from 1.6.0 as this is one of the older versions. Whether it works I don’t know, but I do know of at least one person who uses this old version (0.9.4 I believe?) with their HP machines. They also needed to use the 10 second delay files due to NICs being power save ready.

@jmeyer There is no real check. At the moment we install mariadb on fresh installs but stick to mysql on upgrades (which is set in /opt/fog/.fogsettings) because Ubuntu does not properly migrate your database from mysql to mariadb yet (while Debian has long ago).

Thanks.
1.5.7.745 update works fine.