[quote=“SKasai, post: 44747, member: 29107”]Well, looking at /opt/fog/service/common/lib…

We had to hack the MulticastTask.class.php for some reason… This is what we have:[/quote]
Not sure from which version this file is coming (maybe Tom knows better) but it seems kinda old as the class MulticastTask does not extend FOGBase. Not sure if this plays a role but I definitely wonder if your installation is a bit mixed up with code from different versions and patched files on top of that. Wouldn’t wonder if things go wrong with this.

Do you have a spare machine (e.g. just a desktop machine) to setup a new FOG server (version 1.2.0 or current SVN if you like) to see if your multicast issues go away.

It’s very hard to guess what’s going wrong when you use a different set of code than we’d guess you have when talking about version 1.2.0.

As this would cause extra load on the system I wonder if it’d be wiser to try and gather bandwidth data from the transfers that occour while uploads and downloads happen anyway…

/etc/dhcp/dhcpd.conf
[CODE]…
filename “undionly.kpxe”;
…[/CODE]
and restart the service afer changing the config file:

[CODE]service isc-dhcp-server restart[/CODE]

At first I thought access rights seem ok. But luckily I didn’t trust my eyes and starting setting rights on my system just to make sure I didn’t miss something. And there it is…
[CODE]sudo ls -al /var/www/fog/service/ipxe
total 34188
drwx------ 2 fog www-data 4096 2015-03-26 11:54 .
…[/CODE]
The directory itself is not accessible by the webserver. AFAIK all those files and the directory should be owned by www-data and execution rights are not needed:
[CODE]sudo chown -R www-data /var/www/fog/service/ipxe
sudo chmod 755 /var/www/fog/service/ipxe
sudo chmod 644 /var/www/fog/service/ipxe/*[/CODE]
Boot up the client and see if things work!

Please don’t reinstall yet. We better find out what’s wrong and then you can still decide. Better to learn and know what was wrong than having a clean new install working but no idea about why (well, at least that’s how I see things).

From what I can see in the error.log I am pretty sure it’s access rights on that file. Not sure how that could happen… Please post the output of the following command run on the FOG server:
[CODE]sudo ls -alZ /var/www/fog/service/ipxe[/CODE]

[quote=“raymondub, post: 44705, member: 28342”]I made 2 things:

• disable wifi in the bios
• creation a new host adding the macaddress in fog[/quote]

Great! My guess is that the wifi adapter is being recognized when the FOG client boots up and it wants to request an IP via DHCP too…

AFAIK this main board still has PS/2 connectors. Hope you still have one of those keyboards handy… give it a try!

Edit: I am not absolutely sure but I read about different revisions ob this mobo either having a BIOS or UEFI… Which revision do you have? BIOS Version? Can you set legacy mode in BIOS/EFI?

Are we talking download multicast or single imaging??

Still wondering why we see two udhcpc on this Latitude E7440…

Talked to Tom about it and he created a custom init.xz for you showing all the interfaces just before sending out DHCP requests… Would you please try this on your Latitude and take a picture of the interface list?

[CODE]cd /var/www/fog/service/ipxe
sudo mv init.xz init.xz.orig
sudo wget http://mastacontrola.com/init.xz
sudo chown www-data:www-data init.xz[/CODE]

Sounds feasable to me when all your clients are in that same VLAN too and everything is configured properly… give it a go and let us know if you need assistence or things go wrong.