[Dnsmasq-discuss] test DHCP clients

Geert Stappers stappers at stappers.nl
Sun Dec 30 15:26:10 GMT 2018


On Sun, Dec 30, 2018 at 03:36:29PM +0100, Geert Stappers wrote:
> On Sat, Dec 29, 2018 at 10:00:50PM +0100, Geert Stappers wrote:
> > On Sat, Dec 29, 2018 at 07:49:34PM +0100, Geert Stappers wrote:
> > > Hi,
> > > 
> > > What is your favorite / good enough  DHCP test client?
> > > 
> > 
> > I use `dhtest`  ( https://sargandh.wordpress.com/2012/02/23/linux-dhcp-client-simulation-tool/ )
> > 
> > Test is `dhtest -m 00:00:11:22:33:44 -i eth0`
> > 
> > At server side is dnsmasq.
> > With `dhcp-range=192.168.45.100,192.168.45.200` I do get replies.
> > With `dhcp-range=192.168.45.19,proxy` I don't.
> > 
> > I would like to know if my "DHCP client" is wrong
> > or that I did misconfigure dnsmasq.
> > 
> 
> Both.
> 
> Working dnsmasq.conf
> -------
> $ cat /etc/dnsmasq.conf
> # interface=eth0
> 
> pxe-service=123456789, "Install Linux", pxelinux,0
> 
> dhcp-range=172.24.0.63,proxy
> ## dhcp-range=172.24.0.30,172.24.0.40
> 
> dhcp-option=vendor:PXEClient,6,2b
> 
> dhcp-boot=bootfilename.bin,nero.lan,172.24.0.54
> log-dhcp
> 
> enable-tftp
> tftp-root=/srv/tftpd
> 
> port=0
> -------
> 
> Main difference against previous version is the 'pxe-service=' line.
> 
> The 172.24.0.63 is the broadcast address ( my network is 172.24.0.0/26 )
> 
> 
> To have that seen working, I did have to reboot a physical computer.
 
Without reboot:

   sudo dhtest -m 00:00:11:22:33:44 -i eth0 \
     -c 97,hex,0000 -c 93,hex,0000 -c 94,hex,010201 \
     -o PXEClient:Arch:00000:UNDI:002001


> So, yes,  your advice for DHCP test client is still welcome.

   :-)


Groeten
Geert Stappers
-- 
Leven en laten leven



More information about the Dnsmasq-discuss mailing list