[FS#3352] [dnsmasq] DHCP Option 6 doesn't proper auto-configured

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Sun Sep 20 11:02:42 EDT 2020


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Patrick Young (kmahyyg) 

Attached to Project - OpenWrt/LEDE Project
Summary - [dnsmasq] DHCP Option 6 doesn't proper auto-configured
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on

DHCP Options 6(DNS Server) doesn't correctly set after re-enable dns role on dnsmasq.

 - Software versions of OpenWrt/LEDE release, packages, etc.

LuCI Master (git-20.223.26773-d18ef13) / OpenWrt R20.8.27
DNSMasq Version 2.81
Unbound Version 1.10.1

 - Steps to reproduce

1. According to OpenWRT Wiki, https://openwrt.org/docs/guide-user/base-system/dhcp_configuration#disabling_dns_role , Disable DNS Role first.
2. Re-Enable DNS Role by reverting the changes above or configure unbound DNS with LuCI, make sure to set unbound linked to dnsmasq as DHCP Server.
3. Whatever choice you made on step 2, DHCP Option 6 won't be set. According to the capture by wireshark, the DHCP response packet does NOT contain any DNS Server related setting, which will finally lead Windows set 127.0.0.1 as DNS server and your internet connection won't be detected.

 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3352

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the openwrt-bugs mailing list