@Jeremy said in FOG Project Image Capture on Raspberry Pi 4 (ARM64) via U-Boot:
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.