Simon Kelley <[email protected]> writes: > Ferenc Wagner wrote: > >> The default config file of dnsmasq 2.55 reads: >> >> # If you want dnsmasq to provide only DNS service on an interface, >> # configure it as shown above, and then use the following line to >> # disable DHCP on it. >> #no-dhcp-interface= >> >> Which is a contradiction, because dnsmasq can also serve TFTP. Is >> that always offered on all interfaces being listened to, or disabled >> along with DHCP on the specified interfaces? Of course the best would >> be adding some general configuration mechanism, like specifying the >> services on the interface= lines (with sensible defaults), but >> documenting the actual behaviour would be good enough for now. :) > > TFTP service is offered on the same interfaces as DHCP, so that should read: > > # If you want dnsmasq to provide only DNS service on an interface, > # configure it as shown above, and then use the following line to > # disable DHCP and TFTP on it. > > > I'll make the change.
Thanks. Now I firewalled the DHCP traffic coming from the segment I want to provide only TFTP on to suppress the "no address range available for DHCP request" messages. Is there a better way to achieve this? -- Cheers, Feri.
