YES, It’s works !!! Such a simple misteake, thx for patience and everything
I was looking for this file, it wasn’t there, I reinstalled FOG and magic happend ;]
Now I will be testing multicast !!! Keep your fingers crossed, i will let you know
YES, It’s works !!! Such a simple misteake, thx for patience and everything
I was looking for this file, it wasn’t there, I reinstalled FOG and magic happend ;]
Now I will be testing multicast !!! Keep your fingers crossed, i will let you know
Thank you for your response. I don’t know why but I thought all the time that FOG should be installed on the server / router behind NAT. It didn’t occur to me that it could be a normal host on the network. I don’t need Fog working as a router and image server. Now I see that it makes no sense. So I’ll try to install it on a separate host computer and see what happens.
My switch is TP-LINK TL-SF1024. So it’s not an advanced device. But if I can run FOG on it, I’ll talk to my boss about something better.
Thanks to everyone for the answers, I will let you know if it works.
I had a problem when capturing an image when the computer was in legacy mode, when it was in UEFI mode everything worked. Then I reinstalled FOG on PROXMOX and I didn’t check Legacy mode anymore, but now I just tested imaging in legacy mode and everything works. That’s why I thought it was somehow dependent on whether fog was installed in UEFI/Legacy mode. Topic to close then.
Hi, I’m moving FOG to Proxmox. I currently have FOG installed on a physical computer on Ubuntu Server in Legacy mode, and I’m restoring systems in legacy mode. On the second computer I put Proxmox and there I created a VM with Ubuntu using the default SeaBIOS. Both FOG servers use dnsmasq with the same config (only different FOG server IP addresses). However, during registration and later restoring images from FOG on Proxmox, FOG uses booting after UEFI, not BIOS. Can someone explain to me why this is happening? Is it related to SeaBIOS? Or is it because Proxmox is based on UEFI?
I would like to be able to restore systems on Proxmox in both Legacy and UEFI mode, how to set legacy mode on VM in Proxmox?
Hello everyone, I have Fog installed on Ubuntu 24.04.1 on a virtual machine on proxmox. I get this error on the client:
“https://192.168.25.11/fog/service/ipxe/boot.php… Error 0x420c6001 (https://ipxe.org/420c6001)
Could not boot: Error 0x420c6001 (https://ipxe.org/420c6001)”
what could this mean?
edit:
It looks like I messed something up during the installation. I suspect it’s the DNS. I didn’t notice, but it detected the DNS as localhost by default. When I changed it, FOG started on the client.
thank you george, the current switch is unmanaged, it’s a simple switch. There is not much in the specification of the switch, so I bet that switch is the problem.
All PCs are the same and support WOL and on the old switch they all turn on, but I will check it, maybe one of the students has changed something in the BIOS
Multicast is working, but …
First I used my old switch TP-LINK TL-SF1024 and it’s faild. Two PCs restored at a rate of 150MB/min,
Second time I used LinkSys LGS308, 8 x 1Gb ports. I start to restore 2 other PC and only one turn on from network, second i turn on by my self but the multicast session starting, and both PC restore at rate of 10GB/mmin. Then I connect third PC to the switch and strat multisession once again one PC turn on but second and third i have to turn on. Again multicast worked very well (10GB/min at each PC)
Do you have an idea why only one PC wake on LAN?
Whether the old switch may not support multicast?
YES, It’s works !!! Such a simple misteake, thx for patience and everything
I was looking for this file, it wasn’t there, I reinstalled FOG and magic happend ;]
Now I will be testing multicast !!! Keep your fingers crossed, i will let you know
There is no / tftpboot directory.
I install everything again, I have no idea what happened to this catalog. I could have sworn that this catalog was yesterday.
@george1421
your suggestion did not work. I looked for TFTP troubleshoting like @Sebastian-Roth says and used the command:
tftp -v x.x.x.x -m binary -c get undionly.kpxe
and i have got nothing.
I searched the system a bit and found something like this:
this is my tftp-hpa configuration file
# /etc/default/tftpd-hpa
TFTP_USERNAME="tftp"
TFTP_DIRECTORY="/var/lib/tftpboot"
TFTP_ADDRESS=":69"
TFTP_OPTIONS="--secure"
there are no files in this directory, so where is the undionly.kpxe?
This is from Ubuntu server 18.1 and dnsmasq 2.9 verssion:
# Don't function as a DNS server:
port=0
# Log lots of extra information about DHCP transactions.
log-dhcp
# Set the root directory for files available via FTP.
tftp-root=/tftpboot
# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,192.168.25.117
# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override
# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,192.168.25.117
dhcp-boot=net:UEFI,ipxe.efi,,192.168.25.117
dhcp-boot=net:UEFI64,ipxe.efi,,192.168.25.117
# PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1
# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi
dhcp-range=192.168.25.117,proxy
And this one is from Ubuntu 16.04, dnsmasq 2.5 :
# Don't function as a DNS server:
port=0
# Log lots of extra information about DHCP transactions.
log-dhcp
# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp
# Set the root directory for files available via FTP.
tftp-root=/tftpboot
# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,192.168.25.137
# rootpath option, for NFS
#dhcp-option=17,/images
# kill multicast
#dhcp-option=vendor:PXEClient,6,2b
# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override
# PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3
# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from network", undionly
# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
#pxe-service=X86PC, "Boot from local hard disk", 0
# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1
# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses. Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.25.137,proxy
# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h
# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite```
Hi again.
Now I have one network interface - the FOG server plugged in the switch. Switch is plugged into hardware dhcp so I used dnsmasq from here and then soluion from here
in both cases I get something like this: