Public bug reported:
Hi,
I'm running an Ubuntu PXE server with dnsmasq.
Manpage says
-M, --dhcp-boot=[tag:<tag>,]<filename>,[<servername>[,<server
address>|<tftp_servername>]]
(IPv4 only) Set BOOTP options to be returned by the DHCP server.
Server name and address are optional: if not provided, the name is left empty,
and the address set to the address of the machine running dnsmasq.
However, I found PXE clients ot be stuck after loading pxelinux.0.
Analysis showed that the DHCP offers from dnsmasq do not conform to the
man page, if no server is given. The "Next Server IP Adress" field is
then set to 0.0.0.0 instead of the dnsmasq's own IP address.
Which is odd, since the PXE server itself gets his IP-address
dynamically, thus requires the config file to be changed after every
boot.
regards
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dnsmasq-base 2.75-1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 9 00:50:05 2016
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611140
Title:
--dhcp-boot option differs from man page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1611140/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
