@george1421 said in Securing FOG Boot Options?:

@jra Now that I’ve had my second cup of coffee this morning I can explain it a bit more.

What the advanced menu and advanced.php does is insert a menu you create when advanced.php is called. You have to hand code the advanced menu and insert the text into a field in FOG Configuration->FOG Settings PXE Advanced Menu field. That field is then inserted after the #ipxe you saw when you called advanced.php directly (like I had you do).

I don’t have the skills to do this, but it would be great if you could construct the advanced menu like you do the standard iPXE menus by just changing the Menu Show with field, to “Show on Advanced menu”. Then you could move standard menu item behind the advanced menu right from the gui. That sounds like a logical feature to have, but right now the FOG Project doesn’t have the developer time to add that feature.

Right right - ok I’m with you. Have the workaround though and for now even the non-splash menu is functional, in the sense that curious students here can’t amuse themselves doing goofy imaging.

I am appreciative of the help so thanks much there. 🙂

I know that this is an old thread but please can a moderator link this to?

https://forums.fogproject.org/topic/12838/change-the-default-images-location

I found the former by Google and this fixed my installation.

Please feel free to delete my comment. I wont be offended!

Thanks.

@fgutvar multicasting is very much dependent on your infrastructure. Multicast packets are normally blocked crossing your vlan routers this is by design. For multicasting across subnets there is typically a multicast router in place. This can be the same or different than your vlan router. The processing of unicast and multicast routing are different. Some standard IP routers have an igmp proxy service that will run. It functions much like a dhcp-relay or dhcp-helper service does, but the igmp proxy listens for multicast traffic and not dhcp traffic.

@george1421 : Thank you very much.

In fact i’m used to regular pxe server and we use fog mostly for the cloning feature for windows Workstations.

To deal with Ubuntu workstations i like to do iso booting + pxe , this way i can mix/test configurations (preseed.cfg) of installation process quickly/easily directly from our gitea.

By the way i use fog as the main pxe server even for servers with debian based installations.

After this part of deployment ansible is the king of the hill to do all basics/complex tasks.

Can i modify the topic’s title with SOLVED ? Can i edit my posts to remove the domain’s informations ?

Regards.

@noobfogger said in Backgroundchange dont work -> black:

can anyone send me an custom background .png that i can test it?

http://boot.ipxe.org/texture.png
https://ipxe.org/_media/logos/ipxe-large.png

Both are used for testing by the iPXE team and should work. Though I have to say I have not tested those myself lately.

In ubuntu server 21.10 i had to change something in ~/fogproject-master/lib/ubuntu/config.sh -> “php-gettext” to “php-php-gettext” -> is maybe that the reason?

No, definitely not.

@psicodelico FOG was not made to support setups with more than s single network interface. While you can manually fiddle with things to make some scenarios work I am not sure this is true in your case. You probably need to explain in more detail what your setup looks like. Especially why your FOG server had 10 interfaces. You seem to want to combine FOG server and router in one system from what we know so far. Not a great thing to do I reckon.

Thank you sir

@Pilar Somehow lost track of this. You still run into this issue?

The output you posted seems file so far. What about exportfs -v (please post output here as well)?

Is 111.111.111.111 your FOG server IP?

Is there a firewall on the FOG server or somewhere along the route between host machine and FOG server?

if I change the path of the image in the node it does NOT create a new exports with the current

I am still not sure I understand what you meant here.

@sebastian-roth Thank you. I have not exchanged .efi for .*pxe, it’s what’s in the configuration by default. I’ve only added the “authoritative;” line and changed the UEFI 64 files to intel.efi instead of ipxe.efi. Also, I’ve also used snponly.efi which returns the same result with intel.efi. I decided to use snponly.efi for the meantime while on testing stage.

@handso said in Dell 5090 MFF restores during the capture process. HELP!:

The Linux Kernel is 5.10.71 Tom Elliott arm64.

I am just wondering about the arm64 part. Probably just what you copy & pasted when grabbing the version but I still want to bring this to attention.

So I did the capture through the debug method. Unfortunately no error message outputted on the screen during the capture. It happens around 8% of disk 3 being cloned. It just exited directly and restarted.

As George already said this is hardly ever the case with FOG. So we don’t have a simple step by step guide to debug this issue yet. There is a slight chance that updating to dev-branch can help because we updated the FOS inits to a newer buildroot version just recently. Though the Linux kernel version has not changed much (5.10.86) and I don’t think that’s gonna make the difference. But it’s still worth a try.

If that doesn’t help I suggest you take a video of the screen while capturing. Make sure you setup the camera/smartphone (on a pile of books for example) to get a steady recording. Some cameras even allow for 60 fpm videos. This way we might have a chance to see even a very brief error message flashing the screen just before it reboots.

@jshaver @george1421 Well done!

As far as the upgrade: although it seemed to finish with an error concerning updating the PHP components, the node showed the latest version in the console. Not sure what’s up with that, but it looks like the upgrade fixed this issue.

You might want to post the error log here so we see what went wrong and if it’s worth investigating. You find the log in /root/fogproject/bin/error_logs/...

@cparsons The short answer is you have 2 dhcp servers on your network and one of them are not handing out dhcp option 66 to the pxe booting computer.

Is your FOG server on the same subnet as your target computer?
What device is your dhcp server? (mfg and model)

@Rayco Thanks for letting us know. Though I guess we have updated this long ago. See this commit from 2018: https://github.com/FOGProject/fogproject/commit/b629d5ef15ae52f680fb5c7b99c53ee1da91aa5a#diff-6c19cefd5d36153992eb2ff3ad4873a91680a65ef783d8aa86751fea6f90ef29 (We have changed the URL to standards-oui.ieee.org despite Tom’s comment in that commit.)

I never had problems with mac list update, but in my last update FOG cannot open http://standards.ieee.org/regauth/oui/oui.txt because isen’t a valid link now.

You seem to be mixing up a few things here. First we need to know which version exactly you use and if you’ve manually modified the code already. The very latest dev-branch code is already using the URL you ask about. And this is the same if you’d use latest alpha from working-1.6 branch.

@george1421 I found a device that was running a second DHCP … thanks for your help, the capture and deployment works now

@zaboxmaster said in USB to ethernet adapter:

I know this has been covered multiple times, but I have tried various methods, from the API post-deployment to remove the host to the I.M.I option or the I.M.C option. I cannot seem to get it right.

I am afraid we can’t help you without more details. Please start by telling us the FOG version you use. Then let us know in more detail what exactly you’ve tried and what didn’t work (error messages, pictures, …).

There has been discussion about using a different identifier (other than MAC address) which would help in your case. But there is some major work to be done and no one seems to find the time to do it: https://github.com/FOGProject/fogproject/issues/198

@sebastian-roth when George says this

mkdir -p /opt/fog/secureboot/hwkeys
cd /opt/fog/secureboot/

sudo efi-readvar -v PK -o /opt/fog/secureboot/hwkeys/hw_PK.esl
sudo efi-readvar -v KEK -o /opt/fog/secureboot/hwkeys/hw_KEK.esl
sudo efi-readvar -v db -o /opt/fog/secureboot/hwkeys/hw_db.esl
sudo efi-readvar -v dbx -o /opt/fog/secureboot/hwkeys/hw_dbx.esl
sudo chmod 666 /opt/fog/secureboot/hwkeys/*

He says he got the certs above on a debian instance running on a hardware pc,

What about if this a Ubuntu vm?

@chaonatic said in Lenovo x1 Carbon Gen 7, 8 & 9 USB NIC Issues:

Okay, I changed the boot file name and it did do the 10 second delay, but it’s still not PXE booting off of a USB-C NIC or the dock. Any other ideas I could try?

OK then I may ask you to hit the s key on your keyboard when asked to do so. Wait for another 30 seconds and then key in the following commands, take a picture and post here:

ifstat dhcp net0

@inger Well we really need to isolate just the fog server and target computer on the same network switch. Right now we don’t know where the problem is. It sounds like a network issue. I assume both the fog server and target computer nics are in working order, so we need to look at what is in between. So my recommendation is to start small and see if it works. If yes then start expanding the scope of devices.

At this point I don’t think its the fog server at fault, but something in the infrastructure. I’m not trying to point blame some place other than fog, it just seems like an intermittent network issue.

@dawnofsoap Thanks for bringing this up again. I should really push out a new release when I find the time over X-mas.

@cul3r0 said in Fog Server CA Download:

How do you recompile your own client binaries? Is there documentation on that?

You can find information on all the tools and stuff you need in our github project readme though it’s kind of dated (older versions).

I have been quiet because I am looking into re-designing the whole thing to make it a lot easier. Please be patient a little longer.