Wookey wrote:
Package: dnsmasq
Version: 2.22-2
Severity: normal
I accidentally put a line like this in my dnsmasq.conf:
dhcp-option=pxe,next-server,194.70.44.161
instead of like this:
dhcp-option=pxe,66,194.70.44.161
If you so this dnsmasq segfaults.
That's fixable.
It should complain about 'unrecognised option at line foo' or something instead.
The code is there, but Not Quite Right.
Even better it would understand the dhcpd-syntax 'real names' rather than
just the rather arcane numbers.
Much more difficult: it's currently permisable to have more than one
network tag, like so
dhcp-option=pxe,wired-network,3,192.55.66.1
which means "send option three as 192.55.66.1 only when both pxe and
wired-network tags are set" disambiguating that when the option is
allowed to be textual gets messy. I guess it's something for dnsmasq 3.x
"now with properly designed config-language"
Note that your example is doomed anyway, dnsmasq will see 194.70.44.161
and think "IP address" and shove the obvious four bytes in, rather than
the ascii characters required by option 66, which is the next-server
_name_. dnsmasq 2.23 will do the correct things with quotes, allowing
dhcp-option=pxe,66,"194.70.44.161"
in the meantime, the best workaround is to send the next server value
using dhcp-boot=<filename>,<next_server>,<server_address>
Cheers,
Simon.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
