@Tom-Elliott ok how do I set it to 192.168.11.1?

@ksrvpvl Ok, I think I’m getting what you’re saying. I misunderstood earlier.

Is your custom menu option to boot to winPE working? Or are you asking for help with that part too? There is some very basic guidelines on creating a winpe boot option here https://docs.fogproject.org/en/latest/ipxe

The plugin system needs to be enabled in the fog settings, then you should see a plugin menu where you can activate and then install the tasktypeedit plugin. Some basic plugin system info is here https://docs.fogproject.org/en/latest/plugins but it looks like you got past that bit now.

I also found this post https://forums.fogproject.org/topic/10274/creating-task-with-tasktypemanagement?lang=en-US&page=1 where someone was doing the same thing. Perhaps it may offer some help.

@JJ-Fullmer I captured an image from the surface go 4 with the new kernel that has UFS support and I was able to deploy that image with its 4k block based partition table without issue.
Of course that image can now not be deployed on 512e block based disks.

If I ever get the time, I may try testing manipulation of the parition blocks and using an efi tool in a fog post install script to make it so an image can be deployed to either but its probably unlikely to be possible.

For reference, here’s what the 4k block based partitions look like

d1.partitions label: gpt label-id: DEECB42F-8F01-49B9-85BE-8398A932E4E5 device: /dev/sda unit: sectors first-lba: 6 last-lba: 31246330 sector-size: 4096 /dev/sda1 : start= 256, size= 76800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FE5BA595-3498-4D4A-B741-9EB5D84C1EA5, name="EFI system partition", attrs="GUID:63" /dev/sda2 : start= 77056, size= 4096, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=752C5B50-96B7-4130-9789-9A02B05F8A75, name="Microsoft reserved partition", attrs="GUID:63" /dev/sda3 : start= 81152, size= 31024716, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C088525B-56B9-4D7E-A040-1C8F5A782ADC, name="Basic data partition" /dev/sda4 : start= 31106048, size= 139776, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=E2B6791E-DC55-4039-A658-9007B5749FEE, attrs="RequiredPartition GUID:63" d1.minimum.partitions label: gpt label-id: DEECB42F-8F01-49B9-85BE-8398A932E4E5 device: /dev/sda unit: sectors first-lba: 6 last-lba: 31246330 sector-size: 4096 /dev/sda1 : start= 256, size= 76800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FE5BA595-3498-4D4A-B741-9EB5D84C1EA5, name="EFI system partition", attrs="GUID:63" /dev/sda2 : start= 77056, size= 4096, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=752C5B50-96B7-4130-9789-9A02B05F8A75, name="Microsoft reserved partition", attrs="GUID:63" /dev/sda3 : start= 81152, size= 31024716, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C088525B-56B9-4D7E-A040-1C8F5A782ADC, name="Basic data partition" /dev/sda4 : start= 31106048, size= 139776, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=E2B6791E-DC55-4039-A658-9007B5749FEE, attrs="RequiredPartition GUID:63"

Something odd is it doesn’t look like the main OS partition (sda3) shrunk, but it for sure did as it is only 10.56 GB on the server (compressed size) and deploys around 20 GB on the client, same size as the VM based 512e image.

@matthewadams12 Why do you need the Fog Server to be offline?
Maybe there’s a solution where we can isolate just the part you want to isolate. i.e. if you are trying to remove internet access where images are stored you could setup a storage node and keep that offline after initial install. The storage node would also need packages and updates to fog, but you could capture them during updates on the main server and then sneakernet them to the storage node.

Storage nodes are just what I’m using as an example. If it’s not the images stored on the server you’re trying to isolate, then there could still be another solution. You could also firewall the server with your external firewall or the os firewall to only allow access to the fog github page for update downloads and then the repo sites that download the package updates?

Just thought I’d throw out some other possibilities.

@cul3r0 The https redirect is actually only working for me if I go to the fqdn on http, i.e. http://fog-server.domain.tld will redirect to https but http://fog-server will not redirect.
I’m pretty sure it’s possible to adjust the rules to redirect everything to the fqdn on https. You can probably mess with the rules to make it rewrite anything to go the the fqdn on https

@SOSF2 OK I update this exports file with the 2 new location and it’s working ! Thanks. I thinking that this file was not updated with a new ./installfog.sh but it was…

I understand. I thought that with 2 network cards it would be possible to do this.

What I tried was to do the following and change the default.ipx file with the following line:

chain http://192.168.10.1/fog/service/ipxe/boot.php##params || chain http://192.168.0.1/fog/service/ipxe/boot.php##params || goto bootme

WhatsApp Image 2023-12-06 at 09.34.02.jpeg
And I managed to boot on the other network. This way, it is possible to boot from the 2 network cards in different VLANs.

The problem is that, as @george1421 said, Fog doesn’t provide this type of support. (I believe that if the developers created an ID to identify the network and separated the files it would be possible to do this configuration, but I don’t know the feasibility of that.)

As @baovipboy156 suggested, I’ll try to do a forward port to the fogserver in pfSense, and let you know if it works.

Thanks for the help guys.

@Tauric said in Can't deploy/register/debug with parallels:

Also for the initrd=init.xz

That is precisely why you should not trust my memory. For a little clarity this is what boot.php file creates for the auto reg function.

kernel bzImage loglevel=7 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.50.23/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.50.23:/images/ storageip=192.168.50.23 nvme_core.default_ps_max_latency_us=0 loglevel=7 mode=autoreg imgfetch init.xz

So the command at the IPXE> prompt would be
initrd init.xz or imgfetch init.xz There is no equals = sign in the command.

And just to tag along with what Tom said, when I first read your post I was confused if your target computers are ARM or Intel? You menitoned Intel iMac, and then a little later ARM. But I took the ARM reference as it should work because its not ARM based.

OK by setting the logging to 7 and you don’t see a bunch of text on the screen then the kernel (bzImage) is not starting up. So at the IPXE prompt I would try kernel bzImage to see if it is really transferring it. The boot command at the IPXE> should try to run the kernel.

@DBCountMan From my memory, yes, that is correct.

@AlleneBrick @alexamore90
Lets clarify further first.

What DHCP server are you using and what is its ip?
What do you want the fog server ip to be?

@Tom-Elliott said in Update to Ubuntu 23.10 arise Kernel Panic on Fog 1.5.10 with Kernel 6.1.22:

@herman This must’ve been changed by someone else at somepoint. Glad you found it and returned here. It seems you were missing the file entirely so that explains the kernel panic.

@Tom-Elliott Thanks man.

@processor Yes you can !

@professorb24 Deploy the image

I believe a reinstall would do the same no ?

@george1421
Thanks for the quick reply, found the cause. I tested running on a vmware virtual computer. There is a constant error there. On the physical computer there are no problems, booting goes as it should.

@JJ-Fullmer Thank you for the info this worked for me.

@baovipboy156

Thanks!

@yonatan FOG doesn’t have the concept of displaying certain ipxe menus based on platform type. You can probably do this with a custom advanced menu but then you have to hand code the menu. iPXE (the bootloader that creates the FOG iPXE menu) can branch in the code based on arch or platform.

While this quote doesn’t speak to your issue, you can see how the iPXE menu item can branch based on the iPXE platform field.
https://forums.fogproject.org/topic/15984/integrate-fog-with-wds-mdt/11?_=1702084351302

You could use that concept to create an advanced ipxe menu. One other tip I can give you is that you can view how the FOG iPXE menu is constructed by pointing your web browser at the following url http:<fog_server_ip>/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00

@Cire3 In general what you ask is possible. It will take a little setup to complete, but possible.

What you need to know

FOG has the ability to create custom FOG iPXE menu items. You will want to create a fog ipxe menu to chain to your netboot.xyz server. So you will want to build this menu first and manually select the netboot server to confirm it works (more on that in a bit) If you want to manually select this menu item then you are done. If you want to default to this menu item instead of booting the local hard drive then go to the next step. You can change in the fog ipxe menu builder what menu item you want to execute if you don’t select a menu item. Just change the default menu item to your netboot.xyz iPXE menu.

I have a tutorial on how to netboot installer disks so the concept of creating IPXE menu items. If you read over it you will see how to netboot alternate operating systems. https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

Look at this post: https://forums.fogproject.org/topic/15984/integrate-fog-with-wds-mdt/11?_=1702084351302 if you need to chain to another boot loader than this will help. Specifically this section of the code.

set next-server 0.0.0.0 # Replace with WDS server IP address ... set net0.dhcp/filename ${wds-bootfile} set proxydhcp/filename ${wds-bootfile} chain ${wds-bootfile} || goto Menu

You see how to populate the dhcp next server and bootfile so that the chained bootloader will think it was pxe booted natively. The other thing this ipxe menu shows you how to dynamically change the bootloader based on bios or uefi.

@cornycopia Hi!
Are you familiar with powershell at all? If not, it’s too hard to learn,
I have made a powershell module to help with managing these things (see my signature for more links)

For example there’s a command to make a new fog host https://fogapi.readthedocs.io/en/latest/commands/New-FogHost/
I would recommend giving that a go.

That said, let’s take a look at why this isn’t working

The first issue I see with your body is the macs need to be an array
You might also have to have the modules param defined in the body.
In my PowerShell function I have a function to get all the modules and I filter it to the default ones so that the behavior is the same as when you add a host in the gui instead of creating a host with nothing in it.
https://fogapi.readthedocs.io/en/latest/commands/Get-FogModules/

Here’s a simplified table of that output, I think the ids are always the same in all installs, but they could be unique to your install

id name -- ---- 1 Directory Cleaner 2 User Cleanup 3 Display Manager 4 Auto Log Out 5 Green FOG 6 Snapins 7 Client Updater 8 Host Registration 9 Hostname Changer 10 Printer Manager 11 Task Reboot 12 User Tracker 13 Power Management

Anyway, here’s an example of a json body for creating a host with the default service modules enabled (these are my defaults, you may have different ones configured)

{ "macs": [ "A4:BF:01:6E:E4:F2" ], "name": "demo", "modules": [ "7", "9", "13", "6", "11", "2", "12" ] }