@sebastian-roth yes, right… and just FYI, I got it working once I followed the instructions on the link you’ve sent me, thanks man!

@ngriffith29 With FOG you usually register hosts (at least you need to if you want FOG to rename them) and there you define the hostname it will use after deployment. So it’s just up to you to name the hosts accordingly.

@londonfog said in Use http instead of tftp for fetching kernel and initrd:

and as long as directory above is in /var/www (ubuntu server here) it will work?

Yes. Your actual files will need to be in /var/www/os/ubuntu/20.04/casper/ If all you are doing is changing the protocol.

I agree that tftp over to a remote site will be painfully slow.

If your remote site has a web server available, it may be faster to host this iso locally at the remote site:
url=http://{fog-ip}/os/20.04/ubuntu-20.04.1-live-server-amd64.iso so you don’t have to copy that iso across your WAN link.

@sebastian-roth
Wow, so is my only known option for external storage making the NAS behave as a storage node? It has a flaky proprietary OS/GUI that has warning everywhere. “You will brick me if…”

@george1421 I think that may work, it might be just as easy to implement a feature as well for the web interface, just brainstorming here. But my assumption was that after registering a host, I would be able to log into the fog web interface and assign which menu entry would be default for a host.

I will experiment with both the method you describe, and perhaps a feature as described above in the web interface and see if I can’t get it to work.

Oddly enough I found the solution soon after my last post.I was looking at the wrong file all along.
I completely forgot that I un-commented the line 4 of my dnsmasq.conf file while running some tests last week . I just had to re-comment that line and voila it’s finally working.

@NubCake69 Are all the rooms on the same subnet? On the same VLAN?

From what we know so far I would think you are right, the switches need to relay the DHCP packets. No way to solve this unless you have access to the switch settings.

Update:
Finally had some time to sit and putz with it. Seems it was a carry over issue between what the password was in /opt/fog/.fogsettings for "fogproject’ versus what the UI had for the TFTP settings for the ftp user account, and for the storage node. Interesting that it was able to Image, and pull images though.

For those that may be interested, or have the same issue:
FTP to the FOG server from another box, and test FTP user and password that is shown in the storage management UI. This password should ALSO match what is in the FOG Settings in the UI for TFTP server. In my case… the password in the GUI would not allow me to connect to the FTP. Started searching for the proper way to change the FTP password for FOG… but ended up finding that the password was different in the .fogsettings file. I tried the password in the settings file and it worked to connect to the ftp.

At this point, I took the password shown for fogproject in /opt/fog/.fogsettings and placed it in the UI for the Storage, and TFTP server settings. Attempted to delete from the UI… and bingo, all good.

A good ref that helped to figure this out:
Troubleshoot_FTP

@abulhol Should be back up and running.

Thanks for letting us know.

@nik That appears to be a vmware workstation interface, but TBH I’ve never seen that interface before at least on windows.

The error is a bit strange too. The vmnetX devices are basically like vSwitches are to vSphere ESXi. To reach outside of that vmnetX vSwitch that vmnetX needs to be connected to a physical network adapter. If your fog server doesn’t need to reach outside of the VM Host server then you don’t need to bridge to a physical adapter. If you want two on vm host vms to communicate all you need to do is to connect the VMs to the same vmnetX device.

@jcyrus_rti You are welcome!

Sorry if my answer sounded harsh. Didn’t mean to.

So much for me. I didn’t see that the computer was in raid mode and not in AHCI.
The subject is irrelevant.
Sorry for the inconvenience

Solved topic

@george1421 it is a racktop production filesystem,
the server “heads” are from racktop
I don’t know what filesystem is under that.

The senior sysadmin is looking into creating the share on that system.

I will let you know once I can continue working on this.

Thank again

@sebastian-roth to fix-it, i have changed owner, changrp and chmod.
Thanks for you help 🙂

@george1421
Merci cela à fonctionner avec bzImage553 👍
Bonne continuation
JCH

@mstabrin Ok that is the answer I just came up with. For every foreign subnet you will need to add in a new dhcp-range value.

Well done finding the solution. I also learned something new today too about adding multiple ranges.

@amirbfc said in Lenovo M75s-1 boot on uefi:

“Could not select: Exec format error (http://ipxe.org/2e008081)”

Is secure boot disabled in the UEFI settings?

@dominique said in Database engine MyISAM - upgrade FOG?:

Any idea when 1.6.0 will be general available?

There is no timeline for this yet. Many people use FOG but very few help working on it. So things are going very slow at the moment. We’ll bring out a last 1.5.x release (1.5.10) to finish up that line and then the next will be a first 1.6 release (months down the road).

If you are keen to get InnoDB earlier you can follow the topic Goerge posted. From my point of view this should be possible in 1.5.x setups as well. But we won’t officially support this and don’t want to push out for a major change in the 1.5.x branch anymore.

@huecuva said in Fog on Proxmox ?:

I’m just having issues booting my HTPC from ipxe for some reason I can’t figure out.

Please start a new thread so we can discuss

@alesser Not really unfortunately.

The token you see on the screen is stored in the fogserver in a different mechanism. What you see is an encrypted string compared to what is actually stored in the FOG Server.

If you have the original “plain text” value, it should work (even if you don’t see the same key) as it’s still referencing the same “plain text” value.