Hi,

The plan is that dnsmasq DHCP server hands bootfile information
in conjunction with an existing DHCP, a.k.a. proxy-DHCP

With dnsmasq fresh compiled from up-to-date git repository
works this configuration file:

port=0
interface=br0
bind-interfaces
dhcp-range=192.0.2.220,192.0.2.223
dhcp-boot=ipxe.pxe
enable-tftp
tftp-root=/home/stappers/src/ipxe/src/bin
log-dhcp


Changing 'dhcp-range=' for the wanted  proxy-DHCP

port=0
interface=br0
bind-interfaces
dhcp-range=192.0.2.0,proxy
dhcp-boot=ipxe.pxe
enable-tftp
tftp-root=/home/stappers/src/ipxe/src/bin
log-dhcp


Silences the dnsmasq DHCP server.  The change closer
dhcp-range=192.0.2.220,192.0.2.223
dhcp-range=192.0.2.0,proxy

With
dhcp-range=192.0.2.18,proxy
the same effect ...


Running dnsmasq  --no-daemon   shows
dnsmasq: started, version 2.81-12-g619000a DNS disabled
dnsmasq: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n
no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC
loop-detect inotify dumpfile
dnsmasq-dhcp: DHCP, proxy on subnet 192.0.2.0
dnsmasq-dhcp: DHCP, sockets bound exclusively to interface br0
dnsmasq-tftp: TFTP root is /home/stappers/src/ipxe/src/bin  
dnsmasq-dhcp: 4014338184 available DHCP subnet: 192.0.2.0/255.255.255.0
dnsmasq-dhcp: 4014338184 vendor class: PXEClient:Arch:00000:UNDI:002001
dnsmasq-dhcp: 4014338184 available DHCP subnet: 192.0.2.0/255.255.255.0
dnsmasq-dhcp: 4014338184 vendor class: PXEClient:Arch:00000:UNDI:002001


Network sniff with `tcpdump  -i br0 port bootpc or bootps` on the
server, on the destinated proxy-DHCP server,  shows the incoming
DHCP Discover request and DHCP Offer from existing DHCP server.
Not show a reply from the dnsmasq server.

The "boot client machine" complains "PXE-53: No boot filename received"


What is your  proxy-DHCP
dhcp-range=192.0.2.0,proxy
succes story?


Regards
Geert Stappers
-- 
Silence is hard to parse

_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Reply via email to