..and one FOG-VM to rule them all.
-
@lof said in ..and one FOG-VM to rule them all.:
where are the undionly.kpxe and ipxe.efi files supposed to reside
After you install fog, they are located on the server in
/tftpboot -
@lof Wayne is right, both are in /tftpboot. That is where you need to create the symbolic link between undionly.kpxe and undionly.0 (note the name change from before) as well as ipxe.efi and ipxe.0. Then in your config file for dnsmasq you only include the base names of undionly and ipxe not with the extension. Its a quirk with version 2.75 and older that you have to accept.
Also note the i386 directory is for 32bit efi images. Those systems are not very common any more. Many of the early Apple systems were 32 bit only uefi requiring special boot kernels.
-
@george1421 Thanks for the info, so forgive my rustiness at the CLI but when I try ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0 I keep getting “ln: failed to create symbolic link ‘undionly.0’: File exists” What am I doing wrong?
-
@lof Does undionly.0 already exist?
I can tell you no matter which way I type in the ln command I always get the parameters backwards. So I’m not the best at first time right. The ln command should be
ln -s /path/to/sourcefile /path/to/symlinkso your example looks right. You might have to usesudofor your OS to create sym links if the destination sym link doesn’t already exist. -
@george1421 Yeah so I was looking here https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server …and saw where it shows how to make the symbolic links toward the bottom. undionly.0 already existed so I used cp undionly.kpxe undionly.0 ipxe.0 didn’t exist so ln -s ipxe.efi ipxe.0 worked. After doing that I tried pxe-booting a laptop and it failed saying no tftp file found so I realized I hadn’t modified my /etc/dnsmasq.d/ltsp.conf file. Here’s what I currently have in that file:
#port=0
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe,fog_server_ip,fog_server_ip
dhcp-option=17,/images
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt=“Press F8 for boot menu”,60
pxe-service-X86PC,“Boot from network”,undionly
pxe-server=X86PC,“Boot from local hard disk”,0
dhcp-range=fog_server_ip,proxyAfter I modified that file, removing the .kpxe at the end of the 3rd line up from the bottom, I issued sudo service dsnmasq restart That got me further but now I get “Connection timed out” when trying to get to http://fog_server_ip/default.ipxe
Any ideas?
-
@lof said in ..and one FOG-VM to rule them all.:
That got me further but now I get “Connection timed out” when trying to get to http://fog_server_ip/default.ipxe
Possibly firewall, possibly SELinux. Look at the CentOS 7 pre-config here:
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#Continue_pre-config -
@wayne-workman Thanks Wayne, so I don’t think that’s the problem. sudo ufw status shows inactive so it’s not the firewall. I decided to test at a different office location today and just discovered that tftp is trying to serve up from the IP from the LAN I was on yesterday via http://xxx.xxx.xxx.xxx/default.ipxe even though /etc/dnsmasq.d/ltsp.conf is showing the correct IP for my current DHCP lease for the LAN I’m on now. Where could it be getting that old address from? I logged into the FOG console and checked the settings and didn’t see it in there.
-
@lof I spent a little time searching the forums and I checked every configuration file my searches referenced. I checked /tftpboot/default.ipxe and it’s got the right IP. I also checked /opt/fog/.fogsettings and it had the correct IP but wrong router/dns addresses I changed those to reflect my current environment and restarted my FOG server VM but it still tries serving up default.ipxe from the wrong IP. I’m at a loss where it’s getting that from. On the bright side, I’m getting a really good CLI/Vi refresher.
-
@lof Can you get a clear video of what its doing wrong?
What IP address do you see? Is it something from this server’s past?
FWIW, the .fogsettings file is only updated when the fog installer is used.
Ah, I found it.
https://github.com/FOGProject/fogproject/blob/master/src/ipxe/src/ipxescriptthe iPXE kernel has a script built in, the last line of the above link is the answer.
chain tftp://${next-server}/default.ipxeSo the dhcp server (or dnsmasq) is telling the iPXE kernel where to go next. So check your ltsp.conf file to see if there is an old address in there.
-
@lof said in ..and one FOG-VM to rule them all.:
I’m at a loss where it’s getting that from.
If the DHCP server in that broadcast domain has options 66 & 67 configured, machines may decide to use that rather than the proxy DHCP options provided by dnsmasq. Each machine’s firmware is different - there’s really no consistency here (yes, shame on you manufacturers Dell, HP, IBM).
So, check the DHCP server settings. Try removing options 66/67 and see what happens.
-
Thanks George/Wayne, so the DHCP server at the office I was at yesterday didn’t have options 66/67 set so it’s not that and the ltsp.conf showed the correct IP addresses. I thinking now I may have been shooting myself in the foot because I previously mentioned that I changed the network configuration for my vm in VMware Workstation from Bridged over to NAT’d in order to test. I think that’s somehow related because I did that yesterday shortly before leaving and noticed default.ipxe was getting served from a new address, …from the NAT’d LAN address my vm was assigned when I switched over to a NAT’d connection. A NAT’d network configuration won’t work because clients I try to PXE-boot can’t see the FOG server, even when connected to the same switch. The only network configuration under VMware Workstation I’ve ever been able to get FOG working correctly with is a Bridged connection. At this point I’m probably just going to burn things down and start over, i.e., re-run the FOG install and also the dnsmasq installer. But this time I’ll leave it on the Bridged connection and won’t switch it. I’ll let you know how it goes after that.
-
@lof said in ..and one FOG-VM to rule them all.:
I changed the network configuration for my vm in VMware Workstation from Bridged over to NAT’d in order to test
Yeah that would be why. Broadcast messages do not traverse to different broadcast domains by default - because that would create network storms (yes, that’s a real technical term). You need the VM to be in bridged mode so it can hear DHCP requests.
You do not need to ‘burn things down’. Just switch it to bridged. The MakeFogMobile scripts will reconfigure everything for you when a new IP is received.
