IPXE boot to fog cloud server
-
@ipxefoguser This is NOT a normal ipxe boot sequence for FOG. Did you create any custom ipxe boot menus? I don’t even think FOG uses the clear statement.
-
here is one straight from boot just used dhcp and hten loaded the chain command -
I think he’s typing in commands manually.
So, you should set your dhcp service (or dnsmasq) to point to the public ip of the fog server - then you should be done - provided the needed ports are open to the fog server: https://wiki.fogproject.org/wiki/index.php?title=FOG_security
-
@ipxefoguser Can you tell me precisely what you have configured for dhcp option 67?
While that looks like an ipxe boot banner, why is it dropping you to an ipxe command prompt? At this point the fog custom built iPXE kernel should take over. My intuition is telling me something else is going on here than a normal fog ipxe boot.
-
@ipxefoguser What does this have to do with FOG at all?
The iPXE command
chainneeds an URL pointing to something it can actually chainload. What exactly are you trying to chainload? A kernel?chain http://54.162.252.75/bzImageOr just another iPXE script served via HTTP?chain http://54.162.252.75/script.ipxeWhat exactly are you trying to achieve? What on the cloud server do you want to chainload?
-
i havent made any changes from stock at all. I dont know what you mean by dhcp option 67. I made the ipxe usb drive boot from the ipxe site. Maybe there is a different version but i certainly didnt see anything else.
-
@wayne-workman
on the aws server all ports are open. When i used the prebuilt ipxe test environment it works fine. My guess is something is wrong with the fog server but i used the guide that i linked to before and it doesnt provide anymore details -
@ipxefoguser if the fog instance is all default and you’ve opened it to the world for inbound TCP 0.0.0.0/0 on all ports, then there is nothing wrong with the fog server.
You don’t need any pxe usb device to use fog. The problem is you have not configured dhcp options 66 and 67. Please see this:
https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG
Those dhcp options are done on the local network, not the aws dhcp options. -
@wayne-workman said in IPXE boot to fog cloud server:
https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG
actually when i pointed the url to x.x.x.x/fog/service/ipxe/boot.php i got the boot screen but it kept looping. After that it started to time out and now all it does is time out. So im closer but i dont know what else im missing. I can access it fine via a browswer
-
@Moderators @ipxefoguser change the default login credentials for the fog server please - anyone can log in with the defaults.
-
@ipxefoguser said in IPXE boot to fog cloud server:
i got the boot screen but it kept looping
Most likely this problem would go away if you set dhcp to point to the fog instance - which would cause the target system to use the IPXE binaries built & shipped with fog.
-
@wayne-workman
actually it went through fine now. The last issue i have is that it kernel panics once it boots but idk if thats a local hardware issue or part of the server. The key here was to know where to point to the fog php page -
@ipxefoguser I think I start understanding what you are trying to do here. You have FOG installed on a publicly accessible server (cloud server) and want to image clients through this. It’s not what FOG is made for but I think it can be used like this.
You should be able to chainload the FOG iPXE script like this:
chain tftp://54.162.252.75/default.ipxe(but I think the TFTP port is not open on your server as I just tried this and got a timeout) -
@ipxefoguser You might be able to modify this part of FOG by moving the default.ipxe script to the webserver directory.
sudo cp /tftpboot/default.ipxe /var/wwwThen you should be able to access that file via HTTP: http://54.162.252.75/default.ipxe and also chainload to it:
chain http://54.162.252.75/default.ipxe -
@wayne-workman said in IPXE boot to fog cloud server:
https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG
well now my issue again seem to be ipxe since i cant get it to get an ip no matter what i do but thats not FOG. Like I said i wanted to know the directory where files are stored on log and where the scripts are etc because those were not listed anywhere that was part of confusion
-
@sebastian-roth bingo and it has sorta worked but the issue is whatever kernel fog uses to do that system registration is just too old for this brand new machine and it misses the harddisk entirely. This has happened when installing locally as well. So idk what core system y’all use but we need to update it to the most recent
-
@ipxefoguser You can update the kernel in the FOG web UI. Go to FOG Configuration -> Kernel Update
-
Documentation for kernel update:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update -
@wayne-workman
I really appreciate all your help over the thread. Sadly this machine has a lot of issues in booting except for the latest linux. I only managed to get debian 10 pre release and gentoo to run. So FOG is probably gonna take a while. The issue is around it recognizing the internal harddrive otherwise it just skips over it on the boot screen and choses the usb drive. I looked around and it seems to be a linux kernel issue that got resolved only in october or so release -
@ipxefoguser Welcome. When I post stuff, it’s both for the OP (you) and for future readers too, hence all the documentation links.
