@george1421 Right. I won’t mess with it since we have it set up and working.

Vamos la, o IP esta 192.168.0.100, não estou usando roteador, as port 66 r 67 ja esta configuradas .

A versão que esta sendo usado e 1.5.9.

Estou usando direto em um cabo de rede, porem não inicia o pxe.

@sebastian-roth said in Image menu not showing recently created images:

@Jim-Holcomb How many images do you have? I am not aware of a limit of images that can be seen in the menu but I can’t tell you for sure.

So would you be able to delete an older one and see if one of the new one pops up in the menu?

Hello Sebastian - I tried that - deleting older images. No joy. You know that the image menu just keeps going to the next number in order. I am currently at 160, but of course I do not have anywhere near that many images. Then menu goes to 158 then ends. Yet if I go to “List all Images” of course the image resides there with all of it’s available information, size, date, etc…

I am stumped here.

@londonfog You only get this screen when you do a deploy image from the iPXE menu? Where a traditional unicast (by registering the target computer and then picking deploy) works correctly?

OK lets see if we can get the target computer into debug mode another way. FOG WebUI->FOG Configuration->FOG Sertings Hit the expand all button, then search for KERNEL DEBUG and enable the check box and hit save. Now pxe boot the computer and go through deploy image. Does that put you to the linux command prompt?

If not go back into the same area and uncheck that option and then search for KERNEL ARGS and paste in isdebug=yes and try it again.

Hopefully one of the methods will get us into debug mode.

@george1421 said in Host status is unknow 2:

@eliaspereira So does it work now that you fixed name resolution on the FOG server?

At first, yes.

Thanks again for the great help!!!

Nice, working!
Thanks a lot for the tutorial and all the work!

@londonfog This is just a guess but the api token should be in the WebUI -> FOG Configuration -> FOG Settings page. Just hit the expand all button then search the page for API. This is where I might expect to find FOG (itself) related settings.

@george1421 Thanks work like i want !

@eliaspereira said in wake on lan not working:

fogserver is in a different vlan from the vlans

This is going to be your first problem. The wol magic packet is not a proper IP packet so it typically can’t traverse a router. There is a way to send WOL packet but you need to send as a directed broadcasts. On most routers this “feature” is disabled because it could be used to abuse your networks.

Are you using (or wanting to use) WOL to wake up computers for imaging or just to wake up computers at a specific time?

Understand this subnet issue is a limitation of the WOL protocol and not FOG.

@elogan Ok that was the link I was going to give you. You can not connect through the fog server, but you can setup a synolgy nas as a “fake” fog storage node.

@cwentwo Ok great on the single subnet.

I have a tutorial here on using the FOG server to capture the pxe boot information. On this system that fails to pxe boot follow this tutorial on how to setup the packet capture. Upload the captured file to a file share site with public read with the link and then either post the link here or DM me the link using FOG chat. I’ll take a look at the pcap to see what the client isn’t being told correctly.

https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

The filter used will specifically only collect the pxe booting process and nothing else. The total packet count of a healthy PXE boot is about 8 packets captured.

@florent 0.13.3.1 is the version I already tested previously.

@sebastian-roth Thanks for your answer. I wait then 🙂

@sebastian-roth said in How to disable "password viewing" in the web UI:

Would be interesting to hear what others think about this.

Couple thoughts…

You can create an Active Directory service account with pretty limited permissions, only allowing it to join systems to the domain, and use this for FOG. This is something everyone can begin doing right now. This reduces the blast-radius should the credentials that FOG uses became exposed or compromised.

In the great majority of enterprise I.T. systems I work in, you can retrieve a credential “ID” (like username or access key) but cannot retrieve the credential “secret” (like a password or secret key). FOG is unique in this area, because the FOG Client needs the complete credential. Though, users should be entirely prevented from retrieving this credential… more on this in points below.

Merely concealing the password with the UI, someone who already has access to the FOG server could still potentially use the API to get the password. So, concealing via the UI is just obfuscation and not real security. Concealing via the UI is likely fairly easy to do and would result in less bugs to work out, but this isn’t real security.

Best solution in my view is to store the password within the database using reversible encryption. The encryption key should be generated by the FOG Installer, and put into /opt/fog/.fogsettings. The API / web components would then use one of several ways to handle encrypting and decrypting using this key. A quick internet search reveals lots of options:

https://stackoverflow.com/questions/9262109/simplest-two-way-encryption-using-php https://www.educba.com/php-encryption/ https://www.tonymarston.net/php-mysql/encryption.html

After implementing, the ability to retrieve the password in any form/nature should be secured… which leads into point 5 below.

The transport layer between the FOG Client and FOG Server is already encrypted, but should someone call the server endpoint to get the credentials, we don’t want the password to appear plain-text within the server response. I’ve not looked into how this currently works so I’m unsure in this area. But, I’d think the FOG Client would first prove it’s identity with client-based authentication, and after this the FOG Server would provide the password to the FOG Client. Maybe it already works this way? No idea. I’m remembering @Joe-Schmitt talking about this, and how he worked with @Tom-Elliott to solve it… This was a long long time ago though, and my memory of it is super fuzzy.

@cwentwo You are amazing! That did it! Thank you!

@dima1002
use Debian 10 instead of debian 11
it’s php-gettext for Debian 10 , but it’s php-php-gettext for Debian 11

@myles said in Issues with one time PXE Boot on HP Workstations:

The time it takes for PXE boot to fail might be something we can get away with, but for them to watch an undesired PXE boot to happen will almost certainly trigger complaints,

This process of pxe boot into FOG and then fog menu timeout (default of 5 seconds) should take no longer than 15 seconds to start booting windows. If it taking minutes then something is wrong. As I mentioned I don’t have the client computer boot through the ipxe menu, but the IT tech select pxe boot when imaging is needed. This way the users computer boots normal 99% of the time, without delay.

Also I mentioned that changing the boot order isn’t what FOG does, but I also said a FOG Postinstall script is all you need. Changing the boot order is simply one line script. The (kind of) instructions for the uefi boot manager is here: https://www.linuxbabe.com/command-line/how-to-use-linux-efibootmgr-examples

If you want to do a little debugging using the efibootmgr program you can easily with FOG. Just schedule another capture deploy (doesn’t matter) but before you press the schedule task button, tick the debug checkbox. Now schedule the task. PXE boot the target computer. After several screens of text you need to clear with the enter key you will be dropped to the FOS Linux command prompt. From there look at/follow section 2 from the link I provided. That will give you an idea of what command parameters you need. Once you find the parameters you need to give you the boot order you desire then…

On the FOG server, in /images/postdownloadscripts/ directory there is a file called fog.postdownload Just add that efibootmgr command to the end of that file. Save it and test to see if it gives you the desired results.

Now you might need to make that call to the efibootmgr a bit more intelligent in that lets say you have two different sets of hardware that have different uefi boot orders. You might need to have different efibootmgr commands for different models or manufactures of computers. We can deal with that later if in general the basis work as you need.

Finally you will need to kill that debug task you scheduled at the beginning of this debugging because that job will stay active until imaging is complete in debug mode.

ref: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

@sebastian-roth said in Fog quick image password not working:

If you mess with the code it will break PXE booting for any client.

@Strahd if you get into a situation where the file doesn’t get updated correctly and its messed up, simply rerun the FOG installer script and it will fix (return it back to the standard programming code) things for you.

@sebastian-roth

Updated and he has confirmed it worked. Captured from the same host twice just to make sure.

Thank you so much for looking into this!