is it possible to run bootp/pxe server using dnsmasq without act as dhcp server – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, boot, pxe-boot, dhcp-server, dnsmasq.
on my network its already exist a router that do dhcp, boot in this network i need to boot a diskless system that use pxe to boot from network, while the pxe server is using dnsmasq to serve O/S, but currently this dnsmasq act as dhcp server too, so there are multiple dhcp server on the same network
how to run pxe server without act as dhcp server by using dnsmasq ?
this is my command line to dnsmasq, somehow if i dont specify dhcp ip range, the client wont receive IP and wont boot
dnsmasq --enable-tftp --tftp-root=/var/state/dnsmasq/root --dhcp-boot=pxelinux.0,"$IP",$IP --dhcp-range=192.168.1.10,192.168.1.252,proxy,25220.127.116.11,192.168.1.255 --log-dhcp --dhcp-option=3,192.168.1.1
You need a BOOTP and TFTP server. You could set “next-server” to your current DHCP server setting to your TFTP server too. You won’t be able to run remote boot without correct BOOTP server set to TFTP server (next-server).
First you need a BOOTP/DHCP server to setup the client network configuration and inform what server will be used for PXE/TFTP server. Then you need a PXE/TFTP server to host PXE files, it’s two different services which dnsmasq handles.
Lets consider the already in place DHCP server and your PXE server reside on different PCs.
In this case the DHCP component of the PXE server must be configured as a proxyDHCP and there will be no conflicts with the main DHCP.
You can configure dnsmasq as proxyDHCP.
# This range(s) is for the public interface, where dnsmasq functions # as a proxy DHCP server providing boot information but no IP leases. # Any ip in the subnet will do, so you may just put your server NIC ip here. dhcp-range=10.160.31.10,proxy