@AndrewG78 said in Multiple FOG servers in one network:

dnsmasq will respond with dhcp offer as it does right now, but only to the machines included on MAC address list.
Simple query to FOG’s mysql will get registered hosts from DB and update the list automatically.
If this is not possible with dnsmasq I thought iptables could be used instead?
Obviously, we will lost the ability to register new machines from the FOG boot menu.

Although it’s kind of a hack I kind of like the idea. Personally I would go the iptables route but just because I love it.

You could even get registration working I suppose. Let me think about the whole idea a bit more. Will get back to you soon.

Why using dnsmasq anyway? What DHCP server do you have right now that cannot be modified to do PXE boot?

@jgiovann said in Clients PXE booting from another subnet:

Continuous pings to the target client show that the interface is correctly assigned an IP address after it boots into the FOG menu. However as soon as the registration process is launched, the client loses connectivity and is no longer able to communicate with the FOG server.

I have seen the client receiving a different IP address on different stages of the PXE boot process. In that whole process the client requests an address from the DHCP server three times. First the PXE ROM of your network card, second is iPXE and last the Linux Kernel. There should be no difference in the DHCP information the client gets for each of those three stages but you never know. Maybe there is another wild DHCP server in your network or a replicating DHCP server setup that is playing tricks.

To actually know what DHCP information is sent is key here I suppose. Setup a mirror port to capture the client port traffic using Wireshark.

If that is asking too much of you we could maybe do a Teamviewer session. The other thing you could check is when exactly does the ping stop? It should stop and pick up again several times if the IP does not change. Check your DHCP logs or leases to see which IP it recieves. As well pay attention on boot up, the Linux part should show the IP it gets as well.

Then see if you find that HTTP request done by the Linux FOS client after DHCP. It should be a so called HTTP HEAD request.

@hancocza Please check to see if you have also set the FQDN in FOG configuration -> FOG settings -> Web Server -> WEB HOST! Writing my last messages in the train where I don’t have good access to the code I forgot about this.

From the information you posted I would expect you’d need to use the GoDaddy Secure Server Certificate (Intermediate Certificate) - G2 as TRUST. This (or more precisely its private key) should be exactly the one that was used to sign your certificate.

@hancocza Oh man/woman, I have overlooked the most obvious problem with this. iPXE is connecting to the IP address instead of hostname and therefore cannot match the names in the certificate. I just had a quick look at the manual pages and seems like iPXE can handle alternative subjects, so I was wrong in my last post.

Edit /tftpboot/default.ipxe on your FOG server and make it use the DNS name instead of the IP.

@hancocza said in Not able to TFTP boot. Invalid Argument Error:

Subject: OU = Domain Control Validated, CN = csims.clas.gvsu.edu

So this is the main subject it was created for. All the other DNS names we find in the alternative subject extension further down. I am not exactly sure about this from the top of my head but possibly iPXE does not support using the alternative subjects from a cert. I will check this out and get back to you.

@Quazz said:

It seems that on GPT builds of Windows 10 (at least on the latest official ISO release of Microsoft), the only folder (and there’s no files) on the first partition (which should be non-resizable) is ‘System Volume Information’ which is available on every NTFS partition…

What exactly is the first partition for I am wondering?!

Got a working flag based approach available for now which should work fine for cases such as @maxcarpone has experienced.

Great stuff. I would say let’s give it a try! Mind sending a pull request towards out fos git repo?

@hancocza said in Not able to TFTP boot. Invalid Argument Error:

Is there a way to use my ssl certs for just the web server?

Sorry, but no. iPXE requests information through HTTP(S) and you can’t separate that from the web interface (certs). I suppose you could setup another webserver (like nginx) on another port and run the FOG web UI on that. But that’s not a great way - don’t go there!

I am fairly sure we can get this to work for you. Let’s start by talking about the certificate. Where did you get it from. What CN is it dedicated to and does it have any extensions enabled? Please run openssl x509 -in /path/to/custom/certificate.crt -text -noout and post output here. A certificate is the public part of a public/private key crypto system and hence there should be no issue posting this content here. If you’d prefer you could also just send me a private message with the information.

@TheDiskDrive What exactly do you see when booting off the ISO? Nothing or does it give you the netboot.xyz bootmenu?

Why do you use netboot.xyz? Not saying that this cannot be used but it’s not specific to FOG and therefore you don’t see the FOG menu no matter what. Look into using our iPXE binaries (download here). Also here you find a tutorial on creating bootable USB media here: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/3?page=2

@DarkSwordsman About DHCP PXE boot you want to read this: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

Sure some hardware just does not want to play with the exit types. But give it another try. Make sure you play with the UEFI exit types for UEFI systems.

Do you have one batch of identical client hardware or is it all different systems? Please tell us what exactly you have and there might be other users around using the same hardware and might know which setting works.

@Dee I guess you have a a fair amount of clients and maybe also storage nodes. All talking to the FOG server and causing too much load so other requests time out.

We have adjusted some values and fixed other related things in version 1.5.5 so might want to update and see if that helps.