On 2016/11/15 15:29, ED Fochler wrote: > dhclient fails to update resolv.conf if DHCP is served by dnsmasq on linux. > > This bug is odd and very specific. affects at least OpenBSD 5.9 - 6.0 amd64. > Running OpenBSD on core2duo laptop and vm gives me the same behavior. > If dhclient.conf specifies domain-name, domain-name-servers then all is well. > Default behaviour with no dhclient.conf, such as bsd.rd for fresh install, > then > gateway and nameserver must be manually filled in despite being given by > DHCP. Other OSes (mac, linux, windows) on same DHCP service are fine. > > /var/db/dhclient.leases shows fully populated information as expected, but > does not populate /etc/resolv.conf by default. As the lease clearly has the > information, and default behavior should be to fill in DNS information, I am > blaming dhclient.
It would probably be useful to get a packet capture. Best way would be to record to a file: # tcpdump -w /tmp/dhcp.pcap -i <interface> -s 1500 port bootps or bootpc Upload that somewhere, and reply to bugs@ with the URL. Also include the output of this: # tcpdump -vvXnr /tmp/dhcp.pcap That way we have the decoded version on the list for ease of reading, and original capture in case it's needed. > I have found no other DHCP server which causes this, > and running dnsmasq on OpenBSD does not induce this problem. Is it the same version on dnsmasq on OpenBSD as other OS? > dhclient running in foreground throws no errors during this situation. > > I hope this is helpful, > > ED.
