2 Error in iPXE (time out and sand device)

[george1421]

@FrancoDin said in 2 Error in iPXE (time out and sand device):

kernel tftp://${fog-ip}/mint/18.1/vmlinu

If you use the fog parameter ${fog-ip} that will be replaced by the actual IP address of the fog server. That makes the fog menu entry portable between different fog servers.

Also be aware that you typed in your post
kernel tftp://${fog-ip}/mint/18.1/vmlinu

I hope its just a type-o but you missed the z on the end
kernel tftp://${fog-ip}/mint/18.1/vmlinuz

Back to your question you can also enter it as this:
kernel tftp://10.0.0.7/mint/18.1/vmlinuz

In programming terms the ${ } denote a variable used in the iPXE menu. Where the variable name is between the curly braces.

[FrancoDin]

@FrancoDin
Also… why the route is
kernel tftp://${fog-ip}/mint/18.1/vmlinuz
when actually the vmlinuz is in /tftpboot/mint/18.1

[george1421]

@FrancoDin said in 2 Error in iPXE (time out and sand device):

But when I boot from there Its says “Connection time out”, its has anything to deal whit dnsmasq?

If you are seeing the FOG iPXE menu then the issue is beyond dnsmasq. If you didn’t see the FOG iPXE menu then we would focus on the dnsmasq settings.

I’m suspecting that there is something wrong with the custom iPXE menu you created or the needed files are missing.

[george1421]

@FrancoDin said in 2 Error in iPXE (time out and sand device):

@FrancoDin
Also… why the route is
kernel tftp://${fog-ip}/mint/18.1/vmlinuz
when actually the vmlinuz is in /tftpboot/mint/18.1

well this will become clear when you know that the tftp server’s base directory is /tftpboot. Just like the http server’s base directory is /var/www/html/. And the nfs servers base export directory is /images on the fog server. So knowing what tranfer protocol you want use, you would place the files in the correct base file directory.

Your menu entry is using the tftp protocol so your base directory is /tftpboot. I can tell you that tftp is the slowest protocol of the three. Depending on how you want to use this configuration you might want to change some things. If its just a test or something you use once a month its fine. But for now get it working then improve on what you have once its works.

[FrancoDin]

@george1421
ahh ok.
I get to here:

When I enter Linux MInt 17.3 It first load 100%, then ok.
and I get to this

[george1421]

@FrancoDin I don’t have this configuration setup any more, but from the error message tells me the fog bits are working correctly (even if FOG was not designed to do what you are doing). You are at the point of netbooting linux mint.

Did you remember to add the kernel argument line after the initrd line?
imgargs vmlinuz root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/mint/18.1/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=us quiet splash

(also make sure your paths are correct)

What I’m doing in this configuration its loading the linux mint kernel and inital virtual drive using the tftp protocol then by using the kernel arguments (imgargs) I’m telling the kernel to get the rest of the files via the nfs protocol (hint: nfs base directory is /images) in the path provided. From your error message I would say that linux mint has started but can’t get the rest of the files over nfs.

[FrancoDin]

@george1421
Ok, you are my new god.
It was an extra character in that line, a type-o.
Now all is working perfectly.
Just one final doubt, what does dnsmasq do to the dhcp?, I am worry that maybe an error in the net and the DHCP failed for the server whit dnsmasq, when I put the server whit DHCP at the start, I lost connection in some devices because the two DHCP overwrite eachother. I am sure this not happen whit dnsmasq but, just wanna be sure.
And sorry for the bad english.

[george1421]

@FrancoDin said in 2 Error in iPXE (time out and sand device):

Just one final doubt, what does dnsmasq do to the dhcp?

We have dnsmasq only configured for proxy dhcp mode. In this configuration dnsmasq will only provide pxe boot information to override dhcp options 67 and 68. You MUST have a functional dhcp server on your network too. This configuration is used when people can change the settings in their dhcp server, we just override them with dnsmasq. If you turn off dnsmasq then the only thing that falls down is pxe booting. No other services are impacted.

If you are getting unexpected results from your dhcp server, then its your dhcp server not dnsmasq doing this to you.

If you want me to provide that dnsmasq is not messing up your dhcp process we can do that too. We’ll just capture a typical pxe booting process using tcpdump (or wireshark) to see exactly what is going down your network wire. I can show you how.