We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
问题现象 端口设为53,并勾选自动设置dnsmasq时,会自动在br-lan接口提供的dhcp通告选项加上"6,192.168.1.1/24",但是此时,Mac和iOS获取到dns会是24.192.168.1,导致无法上网。手动将dhcp通告选项改为“6,192.168.1.1” ,则正常。设置界面如下图:
运行环境
固件型号 Powered by LuCI openwrt-23.05 branch (git-24.057.29846-230cf97) / ImmortalWrt 23.05.1 (r27304-31bc47589e) 原版immortalwrt固件。非第三方修改版。
smartdns来源以及版本 仓库安装,版本45 dnsmasq版本: Dnsmasq version 2.89 Copyright (c) 2000-2022 Simon Kelley Compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
不清楚是固件原因,还是dnsmasq的DHCP通告选项不支持“6,192.168.1.1/24”这样的设置方式。个人网上搜索了下,都是“6,192.168.1.1”这样。
The text was updated successfully, but these errors were encountered:
补充下: 建议不要默认勾选“自动设置dnsmasq”了,或者写清楚会修改哪些地方,因为后台静默修改的话,万一和dnsmasq冲突出错了真的不好定位问题所在。
Sorry, something went wrong.
自动设置的就是6,192.168.1.1,故无法复现自动设置为6,192.168.1.1/24。。。。
No branches or pull requests
问题现象
端口设为53,并勾选自动设置dnsmasq时,会自动在br-lan接口提供的dhcp通告选项加上"6,192.168.1.1/24",但是此时,Mac和iOS获取到dns会是24.192.168.1,导致无法上网。手动将dhcp通告选项改为“6,192.168.1.1” ,则正常。设置界面如下图:
运行环境
固件型号
Powered by LuCI openwrt-23.05 branch (git-24.057.29846-230cf97) / ImmortalWrt 23.05.1 (r27304-31bc47589e)
原版immortalwrt固件。非第三方修改版。
smartdns来源以及版本
仓库安装,版本45
dnsmasq版本:
Dnsmasq version 2.89 Copyright (c) 2000-2022 Simon Kelley
Compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
不清楚是固件原因,还是dnsmasq的DHCP通告选项不支持“6,192.168.1.1/24”这样的设置方式。个人网上搜索了下,都是“6,192.168.1.1”这样。
The text was updated successfully, but these errors were encountered: