Solution to Windows cannot get IP from dnsmasq as DHCP server

Email this to someoneTweet about this on TwitterShare on FacebookShare on Google+Print this page

This is a fix on server side while solution for client side provided by M$ does not always work out.

Windows DHCP Client always sets the BROADCAST flag in DHCP discovery packets and there are two related options from dnsmasq: dhcp-broadcast and dhcp-authoritative.

  • dhcp-broadcast explicitly allows dnsmasq to always use broadcast to communicate with host
  • dhcp-authoritative makes dnsmasq the only DHCP server who will not hold strict RFC compliance

During test, it seems either option respectively solved the problem. However, dhcp-authoritative is preferred if network is setup out of one’s own thought.

 

Apr 17, 2014 @ 00:00
Email this to someoneTweet about this on TwitterShare on FacebookShare on Google+Print this page

Leave a Reply

Your email address will not be published. Required fields are marked *

Please calculate * Time limit is exhausted. Please reload CAPTCHA.