@Wallae said:
If you want to get the old naming scheme (eth0, eth1, etc) do the following in terminal
sudo apt-get remove biosdevname
sudo update-initramfs -u
You will need to reboot after.
As for installation guides
https://forums.fogproject.org/uploads/files/1443813159297-imaging-server.pdf
is generally considered one of the best ones even if some things may not apply to your specific situation, it should help you get started at least.
I highly recommend getting a static IP at any rate.
@Tom-Elliott Right, got them mixed up, my bad. 
As to answer his question then, you need to add it in the advanced menu in 1.2 using iPXE formatting.
@hugothebas Are you on 1.2 or on trunk? Trunk doesn’t have pxelinux.cfg anymore since it switched to iPXE rather than PXE because of the added functionality.
I have not come across this issue since starting this thread (I did update FOG somewhere after the start of the thread which included updates for the binaries)
At worst it will ask me to enter the IP address which is a small price to pay for peace of mind.
So I guess this can be considered solved for now.
I work in a small repairshop, things come and go at a fast pace, as soon as I come across one that doesn’t work again I’ll update this.
@Sebastian-Roth I did as you say, the file will be lower in this comment. First though, something strange happened on the iPXE load screen that I have not seen before (perhaps related to upgrading FOG to latest earlier). It said it got info from both the dhcp server and the proxydhcp (and then selects proxyDHCP correctly).
Anyway, here’s the dump file:
Thanks
@Tom-Elliott Just checked and all those are pointing to the FOG server, which only makes sense since it works with ISC-DHCP and on some clients with dnsmasq ProxyDHCP.
And seeing as it looks on the wrong IP address for the default.ipxe, I’m not sure changing anything in that file would help. (even so everything looks normal in it)
@Sebastian-Roth I may have dun’goofed.
I just captured this on Windows, as you already know.
I suppose I should set up a debug task and capture it like that, then filter it later, right?
Should dnsmasq be enabled when doing this? Should ISC-DHCP?
EDIT: I also noticed dnsbootimage was set to 192.168.1.1 in .fogsettings . I don’t really know what that setting does, do you reckon that should be switched out?
I set up a DNS server in the mean time anyway, as it was a pain to not be able to access our internal network during network outages.
Thanks
Okay, so, I did some wireshark capturing and when ISC-DHCP-SERVER is running, all devices seem to receive their DHCP info from ISC-DHCP.
So I guess the main reason the issue of IP conflict comes up is when it’s unable to communicate with the rest of the network which typically happens when the router has issues as that is referred to as the DNS. So I guess for ISC-DHCP if I can resolve that I would be fine.
Also tried to capture traffic directly to the router and next-server option seems to be set as 0.0.0.0 according to wireshark. However option 63 is not passed along. (does this mean it defaults to the router’s ip or that it’s not set?)
Thanks for the help already, guys.
@Wayne-Workman The modem/router most certainly acts like a DHCP server, hence why we have issues with ISC-DHCP every once in a while. Most of the time it is able to coexist peacefully and everything (even multicast) works perfectly fine.
However, we can’t really change anything about the modem/router (believe me we were already trying to get into it to change things before we even implemented FOG)
All in all, it’s not super high priority or anything, but it would be pretty nice to see it resolved.
I know one of the devs is working on a ProxyDHCP implementation which would also allow for UEFI/BIOS combo (which I’d also like, even though even with ISC this has not really worked at all, it just boots from hard drive after pulling the ipxe.efi file)
Anyway, I do believe I have my answer to this question and I guess I’ll just have to be more patient 
@Wayne-Workman It does work and most of the time it works just fine without issues, but usually after some network issues with the ISP we end up having IP conflicts everywhere that often take hours to resolve which involves mostly praying for good luck and not much else.
@Sebastian-Roth It’s just a regular ISP (Belgacom, a Belgian ISP) modem/router combo thing. Can’t really change anything about it, unfortunately. It’s supposedly a business grade one as we have this server set up at work. It’s used exclusively internally in a small business, only one site and such.
I’m guessing it has to do with the script not always working, because it does work for some clients, but I’m willing to do some tests, if you like.
Is there a way to figure out if it’s sending out next-server information (I know for a fact it doesn’t have network booting options enabled since if I turn off the FOG server the clients just sit there waiting for information they’ll never get), but I suppose it is something worth exploring.
We can get by with isc-dhcp for now, no real rush, it would just prevent some occasional hiccups.
Is it possible to capture network information to the router itself?
I kind of really need to use ProxyDHCP as ISC-DHCP-SERVER tends to break our network every once in a while.
However, while the Proxy information is properly loaded and the file is properly configured (almost just a copy paste, minus changes to ip addresses) and the information on the client reflects this, it won’t boot properly on some clients.
It pulls undionly from the server, but then tries to pull ipxe.default from 192.168.1.1 (which is the router/unmodifiable DHCP) which obviously fails since the file is not located at that address.
Running Trunk latest SVN on ubuntu 15.10.
port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe,,192.168.1.156
dhcp-no-override
pxe-service=X86PC, "Boot from network", undionly
dhcp-range=192.168.1.156,proxy
Seeing as some clients do work, it seems to me the problem lies with how certain NICs function, but I don’t really know enough about it to say for sure.
Any help or ideas or just an explanation would be appreciated (found nothing in search function so far, sorry if this is a duplicate)
Thanks
You need to export the image list. Go to image management, export images, then import them in the VM.
What happens when you do sudo add-apt-repository?
If it says it’s not installed, then do the following:
sudo apt-get install software-properties-common python-software-properties
If it is installed, it’s most likely a proxy issue.
@george1421 said:
@Quazz said:
There is a new setting called bitrate for storage nodes in trunk version of FOG that may be missing a zero (I do not mean replication bandwidth)
First the simple answer. The bitrate is only for moving files/images between the master node and a storage node. Not between the fog server and the target computers.
Wait, then what exactly is the difference between the replication bandwidth setting (which controls at what speeds images are allowed to replicate to other storage nodes) and the bitrate setting?
There is a new setting called bitrate for storage nodes in trunk version of FOG that may be missing a zero (I do not mean replication bandwidth)