New issue
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
FS#3706 - odhcpd defaults to advertising it's own host as a resolver #8723
Comments
jow-: Use |
brianjmurrell: That doesn't seem to be working here: config dhcp 'lan' config dhcp 'lan1' Still getting: from rdisc6. |
dedeckeh: Which release are you using to test this ? |
brianjmurrell:
In the description: //- Software versions of OpenWrt/LEDE release, packages, etc.
No chance of a backport? Is it too invasive? So, is 21 the release after 20, which is not even a release yet? |
dedeckeh: Only bugfixes are backported to stable releases; not features The 21 release is the release currently being prepared |
brianjmurrell: Could I argue that odhcpd advertising itself as a DNS resolver, when it's not, and no ability to disable that is a bug, as it's causing lookup failures on the entire LAN it's servicing? :-) |
brianjmurrell:
Supply the following if possible:
x86_64
19.07.7
Package: odhcpd
Version: 2020-05-03-49e4949c-3
Configure LAN interface for IPv6. In the "config dhcp 'lan'" section of /etc/config/dhcp don't configure any dns items.
Observe that odhcpd (possibly incorrectly) just assumes the host that it is running on is a DNS resolver and puts the IP address of the node it's running in it's RAs as a "Recursive DNS server".
Of course, if there is a resolver running in the network with an IPv6 address, I can use "list dns '...'" to specify it.
But if there is no resolver with an IPv6 address, including the host odhcpd is running on, there is no way to prevent odhcpd from announcing an invalid "Recursive DNS server" as it incorrectly announces itself barring any "dns" option/list configuration.
The text was updated successfully, but these errors were encountered: