I have an air gapped instance of fog 1.5.8. I have some new devices with unsupported storage devices.

I want to try some of the other boot images to see if they have the correct drivers. They used to be searchable, but i cannot find them of late.

@Sebastian-Roth the installer will not run without internet connectivity. It hangs on the line adding repository, I think. I’ve left it for 30 minutes with no change.

This behavior is new, because I’ve always deleted the .fogsettings file and rerun the installer to change the ip.

Outside the settings in the web ui I had to manually change the ip set in the tftpboot folder.

@george1421 that was it.

I have a new instance of 1.5.7 which is air gapped. Typically we build outside and sneaker net it in, delete /opt/fog/.fogsettings and rerun the installer with the correct ip information.

The installer now checks for internet and hangs indefinitely. Is there a way to bypass the check? I manually changed the interfaces and ips in settings, but I still have a reference to the old ip during the pxe boot.

Http://<old ip>/fog/service/ipxe/boot.php

So I have an issue with MS Surfaces. I only have a handful of usb/ethernet adapters. Ratio is about 100:1.

This causes enormous problems for my cloning guys who are as sharp as a bowling ball.

So I had a hair brained idea. What if I lie to fog? If I boot a custom ipxe image via USB and change the mac in the ipxe bios via “set net0/mac aa:bb:cc:dd:ee:ff”. This does work and my dhcp is non the wiser, but if I chain to the ipxe.efi on the fog server it reverts the mac back to the hardware default and performs another dhcp request.

Soooo what if I go straight from my custom ipxe to fog by calling the script directly from the fog server and cut out the fog default ipxe.efi?

What does the default ipxe.efi script call to start the fog boot process so I can call it directly from my custom ipxe.efi USB image?

I add the wifi mac into the host, but it sees the device as unregistered when it pxe boots.

Any magic I’m overlooking?

Currently fog tracks assets by mac address. Unfortunately, this is causing issues correlating to devices that have removable pxe interfaces, eg surface pro devices.

I currently have multitudes of these devices, and only a handful of USB network interfaces. The mac address travels with the adapter and not the device. Would it be possible to change the key value from the mac address to something like the serial or some unique value that stays with the device.

My environment does no allow to sneaker net in VMs, so I have to build the system onsite without internet connectivity.

I have local copies of the Centos OS, EPEL, and Remi repositories. When using those the installer gets to the page to import the database and, the management page is blank.

I can create a webpage and it does display. Phpinfo shows correctly an is v5.4.

When I run the installer on my laptop from home it works fine, so I know it is a package issue. I am having difficulty determining what packages are winning out during the yum selection process.