@Tom-Elliott
The upgrade to stable version completed successfully.
I’m now on fog 1.5.10.1673
Thanks again

@Tom-Elliott
Sorry :

Thanks for your help.
It seems to works fine now

@Tom-Elliott
After updating from the stable branch, I am still on 1.5.10.

@Tom-Elliott No proxy and no network problem here

@Tom-Elliott
After “git checkout lib/common/functions.sh”
I’m stuck on Downloading kernel, init and fog-client binaries…

curl --silent -kOL https://github.com/FOGProject/fos/releases/latest/download/init.xz

• Could not download init.xz properly

@plegrand In fact i modify this file because of an error during install
1473 lastlog -u $username | tail -n1 | grep “**.***” >/dev/null 2>&1

I replace lastlog by lastlog2

@Tom-Elliott But i didnt modify this file:
lib/common/functions.sh

@Tom-Elliott

I’ve got an error :

git checkout stable
erreur : Vos modifications locales aux fichiers suivants seraient écrasées par l'extraction :
        lib/common/functions.sh
Veuillez valider ou remiser vos modifications avant de basculer de branche.
Abandon

git checkout stable
error: Your local changes to the following files would be overwritten by the checkout:
        lib/common/functions.sh
Please commit or stash your changes before switching branches.
Abandon

git branch
 dev-branch
* master

@Tom-Elliott
What is the procedure for using the stable branch?
Currently, I usually do it this way:

git clone https://github.com/FOGProject/fogproject.git /home/fog-depot
cd /home/fog-depot
git branch
git checkout master or git checkout dev-branch
git init
git pull
cd bin/
./installfog.sh

Thanks for your help

@Tom-Elliott
Hello,
After updating and running a few tests, I noticed an error message in the logs:
fog env[1608]: PHP Warning: Increment on type bool has no effect, this will change in the next major version of PHP in /var/www/html/fog/lib/fog/fogbase.class.php on line 974

What could be the solution to this problem?

Thanks for your help

@Tom-Elliott I just upgraded Debian, im made some change and it seems to work fine

@hillie
That means FOG 1.5.10 works fine with Debian 13 Trixie ?
With the new version of php (8.4)?
Thanks for your anwer
Pascal

Hello,
I am currently using FOG 1.5.10 on Debian 12 (BookWorm).
I am considering updating Debian to version 13 (Trixie).
Has anyone already performed this update?
Are there any issues to be aware of?

Thanks for your help.
Pascal

I have just upgraded from Debian 11 to Debian 12.
No problems except this error in the apache logs:
[proxy:error] [pid 2033] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (127.0.0.1:9000) failed
and unable to access Fog.
I re-run “installfog.sh” and everything seems to be working correctly.
I don’t use LDAp so I don’t have any problems there.
Thanks

@Sebastian-Roth
Hello, I’ll get back to you to know if, today, it’s possible to consider migrating our fog server from debian 11 bullseye to debian 12 bookworm (FOG 1.5.10).
Thank you in advance for your help.

@george1421
None of our switches are configured with dhcp snooping and everything works fine.
The only problem is this room with these network cards.

@george1421
Hello george1421 and thanks for your answer

• Our dhcp server is a separate server not running on the fog server
• It’s the only dhcp server on the network.
• It works very fine and we have no problem for all computers of our network.
• We use this switch for other computers without problem
• dhcp snooping is for multicast no ?
  The only problem is for these computers with these kind of NIC

Thanks again

For information, this is our dhcp configuration:
…/…
option client-architecture code 93 = unsigned integer 16;
…/…

…/…
next-server 192.168.39.243; #FOG
if exists client-architecture {
if option client-architecture = 00:00 { #LEGACY
filename “ipxe.pxe”;
} elsif option client-architecture = 00:02 { #UEFI-32bits
filename “i386-efi/ipxe.efi”;
} elsif option client-architecture = 00:06 { #UEFI-32bits
filename “i386-efi/ipxe.efi”;
} elsif option client-architecture = 00:07 { #UEFI-64bits
filename “ipxe.efi”;
} elsif option client-architecture = 00:08 { #UEFI-64bits
filename “ipxe.efi”;
} elsif option client-architecture = 00:09 { #UEFI-64bits
filename “ipxe.efi”;
}
}
}
…/…

Hello,
We are experiencing major problems on about fifteen workstations equipped with the following network card: Intel I219-V.
We use FOG in many rooms without any problems, but this one is causing us a lot of trouble.
Debian Stable
FOG 1.5.10

The workstations boot PXE with difficulty, and the boot time increases as more workstations are connected.
Subsequently, the deployment happens with a calamitous throughput
The only things I can see are in our DHCP server logs, where dhcp requests from these workstations occur every 2-3 seconds.
The curious thing is that these requests only appear via the switch’s mac address.
…/…
oct. 27 13:52:30 tamtam dhcpd[26231]: DHCPDISCOVER from 2c:fa:a2:1a:eb:b0 via enp2s0
oct. 27 13:52:31 tamtam dhcpd[26231]: DHCPOFFER on 192.168.39.156 to 2c:fa:a2:1a:eb:b0 (vxTarget) via enp2s0
oct. 27 13:52:31 tamtam dhcpd[26231]: DHCPREQUEST for 192.168.39.156 (192.168.39.247) from 2c:fa:a2:1a:eb:b0 (vxTarget) via enp2s0
oct. 27 13:52:31 tamtam dhcpd[26231]: DHCPACK on 192.168.39.156 to 2c:fa:a2:1a:eb:b0 (vxTarget) via enp2s0
…/…
The switch is working properly, as it has already been used in other rooms without any problems.
I could see on the net that this card could cause this kind of problem without really finding a solution.
Have you got any idea about this problem ?

Hello,
I’m coming back to you regarding my initial request.
Has anyone of you tried to upgrade from Debian 11 (bullseye) to Debian 12 (bookworm) with FOG 1.5.10?