Replies: 1 comment 4 replies
-
Dnsmasq, and at least one other machine serves as a DHCP server, or DHCP proxy server. I would recommend using tcpdump or wireshark to inspect the traffic and understanding the DHCP packets. But essentially what you see here is that your new Ubuntu proxy DHCP responds several times, the first when PXEClient runs and that gives the first menu, then again when iPXE runs, and at this time you will want the server to respond with the settings used for "the old iPXE" server. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there! I hope you can help me with my special problem. I searched the web but can't find a working solution.
(Pls forgive my possibly poor english)
I have 2 seperate preinstalled servers with different software starting over PXE. These servers worked fine as single bootservers for a while, but the idea now is (not my idea, i just have the problem) to get them working at the same network now (without changing them much) so the clients can choose where to boot from. So i built a 3rd server with Ubuntu and made a pxe boot menu with dnsmasq. I had a little trouble to find out how to get that working (i'm neither a Linux or an network crack) but now it runs fine with the one server booting pxelinux. The other server boots iPXE and when i boot from the server directly it works fine. But when i boot from the menu iPXe starts but then searches for
http://10.77.80.2/iPXE.menu
instead ofhttp://10.77.80.1/iPXE.menu
running into an error "could not chain iPXE menu"dnsmasq.conf:
10.77.80.2 is the Ubuntu boot sever
10.77.80.3 client boots fine
10.77.80.1 client boots but the software runs into the error described above
Can i avoid the error by modifying anything at my Ubuntu Server?
Beta Was this translation helpful? Give feedback.
All reactions