1. Home
  2. Technical Help

Subcategories

  • Technical help directly related to FOG.
    9k Topics
    86k Posts
    SimonGuentherS

    @Tom-Elliott

    @Jeremy said in FOG Project Image Capture on Raspberry Pi 4 (ARM64) via U-Boot:

    @Tom-Elliott

    Regarding OPNsense, there isn’t anyone on the infrastructure team available to look into it right now; I can probably check on that Monday morning.

    To be transparent with you, I’ve been retraining for a new career since February 2026 and only just got my IT diploma in July. I’m still building experience, but one thing I know about myself is that I stick with projects and usually find a way to get them finished. I’ll get back to you once I have the information regarding OPNsense. Tropical Casino https://tropical-casino.com/ gives me a similar mindset with game rules and account settings: if something isn’t clear, I’d rather work through it properly than pretend I already know the answer. I’d rather be accurate than fast.

    c7c21587-422e-4b8f-9e41-a83d1b13068a-image.png

    bb057c4c-aaeb-418a-8680-53868b66c841-image.png

    Thanks for bearing with me on this. While I wait to get someone from the infrastructure side to look at the OPNsense box, is there anything specific you’d want me to check on it so I can come to Monday with the right information?

    My assumption is that once the kernel brings the NIC up and pulls a DHCP lease, the init scripts then need to reach the FOG server over HTTP (the web= address) and NFS for the image storage. If the Pi and the FOG server are sitting on different subnets or VLANs, I’m wondering whether OPNsense could be dropping that traffic at exactly the point where it hangs, right after “Link is Up” and before fog.checkin ever runs.

    If that’s a plausible direction, I can have them check the firewall rules and live logs for anything blocked between the Pi’s subnet and the server on the relevant ports. If you think it’s more likely something else entirely, let me know what you’d prioritise and I’ll chase that instead. Either way I’ll report back once I’ve been able to get onto the OPNsense side.

  • Problems with specific computer models.
    713 Topics
    8k Posts
    R

    @Tom-Elliott

    Thanks so much for your help with this. Happy to feed back any info I can so please do let me know if there’s anything else you need me to test. Will be on annual leave for a couple of weeks after this and have no access to the systems but I think this confirms your suspicion. Please see results below from a Dell OptiPlex 3070:

    Addresses on this machine:

    NIC: 01:00.0 (Realtek RTL8168h)
    Root port: 00:1c.0

    UEFI mode:

    setpci -s 01:00.0 CAP_EXP+10.w = 0142 (last digit 2 = L1 enabled)
    setpci -s 00:1c.0 CAP_EXP+10.w = 0c42 (last digit 2 = L1 enabled)

    Legacy/CSM mode:

    setpci -s 01:00.0 CAP_EXP+10.w = 0040 (last digit 0 = ASPM off)
    setpci -s 00:1c.0 CAP_EXP+10.w = 0c40 (last digit 0 = ASPM off)

    Dell’s UEFI firmware enables L1 on both the NIC and root port. The Legacy/CSM path leaves both off. The only difference between the two readings is those two ASPM bits. Everything else in the register is identical.

    Thanks for the nudge to run these. Anything else needs testing please do let me know. We love using FOG and it’s invaluable in our set of schools that we work in at least so please do keep up the great work!

  • Technical help related to a Windows Problem.
    1k Topics
    8k Posts
    V

    What version of FOG are you running?

  • Technical help related to a Linux Problem.

    730 Topics
    6k Posts
    Mr_____TM

    @JasonNaughton

    Hi, I noticed that this was unresolved after so long. Wonder if you have solved it?
    I recently stumbled across the man page for dhcpcd.conf. In there is a denyinterfaces (pattern) should solve the issue for you. It tells dhcpd to ignore the nic interfaces listed in pattern. Just was wondering if you found the fix otherwise hope this helps.

  • Technical help related to a Mac Problem.

    81 Topics
    943 Posts
    Bristow 0B

    Hello everyone,

    As I work at a secondary school, I was able to get hold of some Catalina iMacs (iMac 14.3).
    I already use FOG to deploy Windows and Linux images on PCs.

    I would like to deploy a LinuxMint image on these iMacs.

    However, I am unable to boot into PXE on them with FOG, and I do not know what is wrong.

    I modified my DHCP server as follows:

    ## FOG class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { #BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; # filename "i386-efi/ipxe.efi"; filename "snp.efi"; } } } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } ### END FOG

    I tested ipxe.efi in 64-bit and 32-bit, as well as snp.efi, but it still doesn’t work. I get some kind of spinning planet when I try to boot.

    I admit I don’t fully understand the documentation page: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

    Thanks in advance!

  • General Developer questions relating to FOG.
    688 Topics
    5k Posts
    A

    FOG version 1.6.0-beta.5136, https enabled
    PXE works great with Wyse 5070 thin clients and Dell Optiplex 3000 thin clients.

    Tried my first 5060 today.

    Wyse 5060, BIOS 1.0J (2018-11-06), UEFI boot, Secure Boot disabled. PXE acquires DHCP, downloads EFI binary and autoexec.ipxe. Even an autoexec.ipxe containing only:

    #!ipxe
    echo HELLO
    sleep 30

    causes an immediate reboot. No requests for default.ipxe, boot.php, bzImage, or init.xz ever reach the FOG server. Same FOG server works perfectly with Wyse 5070 and Dell OptiPlex systems.

    I’ve tried handing out all the different *.efi devices in my /tftpboot dir, all do the same thing. I know this is a really old system, it’s just weird that it’s just rebooting so early in the ipxe process.

    Has anyone seen this before? THanks

52

Online

12.8k

Users

17.6k

Topics

157.0k

Posts