Hosts are looking for tftp server.
-
@marted I can’t speak for this setting since I’ve never used it.
dhcp-range=eth10,192.168.148.254,proxy dhcp-range=eth11,192.168.149.254,proxy dhcp-range=eth12,192.168.150.254,proxy dhcp-range=eth13,192.168.151.254,proxyI can say for 99% of the dnsmasq installs this line is all that is needed.
dhcp-range=<fog_server_IP>,proxyJust for clarity this is a new vm and not the fog server where dnsmasq is installed?
So if you are on a subnet where these 5-7 workstations ask for the tftp server. If you have wireshark loaded on a third computer with the capture filter of
port 67 or port 68do you only see one or 2 offers? There has to be still something else going on here. Dnsmasq should be fast enough to respond to 100s of requests per second. -
@george1421 @Sebastian-Roth
Please somebody to help me with the options 66 67
on windows DHCP (Infoblox). Finally the University accepted to add the info for tftp on the main dhcp and like this I can stop the dnsmasq.
On 66 I put the IP of the server 192.168.149.43
but on 67 I don’t know how to provide the syntax of the boot file. Do I have to write /tftpboot/default.ipxe or I write directly default.ipxe
Thanks -
@marted said:
Finally the University accepted to add the info for tftp on the main dhcp and like this I can stop the dnsmasq.
Ohhh wow. Keeping my fingers crossed this will fix your issue!but on 67 I don’t know how to provide the syntax of the boot file.
They need to add several ones for different vendor classes. Hope infoblox is able to do this.
undionly.kpxefor legacy BIOS machines (vendor classPXEClient:Arch:00000)ipxe.efifor most UEFI machines (vendor classPXEClient:Arch:00006andPXEClient:Arch:00009)i386-efi/ipxe.efifor some weird 32 bit UEFI devices (vendor classPXEClient:Arch:00007- but seldomly used at all).
The first two are important!
-
@Sebastian-Roth just from curiosity— why when a client boot I see default.ipxe like a file boot
-
@marted Because it’s the first file we tell iPXE to load. Take a look at the ipxescript we embed into the iPXE binaries: https://github.com/FOGProject/fogproject/blob/master/src/ipxe/src/ipxescript
-
@Sebastian-Roth thanks for the answer.
Now I need just to put the files without /tftboot in front right? -
@marted said in Hosts are looking for tftp server.:
Now I need just to put the files without /tftboot in front right?
Yes
-
@marted I remember infoblox from another thread. I guess we need to be mindful of this thread if we see issues here
https://forums.fogproject.org/topic/11749/uefi-pxe-not-downloading-ipxe-efi-file?_=1583888282658
-
@george1421 you’re right. It was a challenge to figured out the way to boot BIOS and UEFI clients with Infoblox… but We did it
and I’m so happy. The info I saw in fogwiki for Windows 2012 server it wasn’t work well on Infoblox. Creating a general roule for Bios clients with .kpxe file and add a filter for UEFI clients didn’t work at all. But what we figured out was that we can simply delete all general config IPV4 and BOOTP and create three IPV4 filters for BIOS 00000 , UEFI 00007 and UEFI 00009. And it works. 5 hours tests but it works . And I was wondering if you want guys to add this info in your wiki or I can add it.
@george1421 @Sebastian-Roth I can prepare a page with all screenshots for all config we did on Infoblox server and I think will be quite handy for people who want to use the principal DHCP for delivering information for boot file and tftp server.
Thanks again for your help and I’m so happy
it works now without any proxy DHCP ! -
@marted Any hints you could provide the next guy would be appreciated. If one person has the problem there will be 10 other later. So if you have a step by step or at least a general guide that can be added to the wiki it would be well accepted.
I’m glad you have it working now so you can get back to imaging and not messing under the hood with networking infrastructure.
-
@marted Just want to keep this topic up as it might be very helpful for others. Not sure if you have time and access to systems right now though.
