Chen-Yu Tsai
2016-09-06 06:55:42 UTC
Hi,
I'm running dnsmasq 2.68 (sigh) on Ubuntu 14.04.5 as part of
a server & network equipment bootstrap & orchestration setup.
Our network equipment supports auto-configuration through DHCP,
using the next-server/tftp-server & bootfile options. The manpage
states """The special address 0.0.0.0 (or [::] for DHCPv6) is taken
to mean "the address of the machine running dnsmasq".""" However
that does not seem to be the case with the tftp-server option.
It seems that tftp-server is a special case, being a boot option
and also a "name" option field, rather than an IP address. Either
this should be fixed, or an exception should be added to the manpage
section on dhcp-option.
A workaround is to not use the tftp-server, and only use the
next-server field in the response, which dnsmasq always defaults
to the local server address. I think this bit also deserves some
mention in the manpage.
Regards
ChenYu
I'm running dnsmasq 2.68 (sigh) on Ubuntu 14.04.5 as part of
a server & network equipment bootstrap & orchestration setup.
Our network equipment supports auto-configuration through DHCP,
using the next-server/tftp-server & bootfile options. The manpage
states """The special address 0.0.0.0 (or [::] for DHCPv6) is taken
to mean "the address of the machine running dnsmasq".""" However
that does not seem to be the case with the tftp-server option.
It seems that tftp-server is a special case, being a boot option
and also a "name" option field, rather than an IP address. Either
this should be fixed, or an exception should be added to the manpage
section on dhcp-option.
A workaround is to not use the tftp-server, and only use the
next-server field in the response, which dnsmasq always defaults
to the local server address. I think this bit also deserves some
mention in the manpage.
Regards
ChenYu