You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LEDE 17.01 on Buffalo WZR-HP-AG300NH, tested with both dnsmasq-full 2.76 from 17.01 and 2.77test4-1 from trunk
The link-local address of the router is advertised as DNS resolver in the IPv6 router advertisement. Queries to that address are received on the router, logged in dnsmasq, but an answer is never sent (verified with tcpdump).
As you can see, it works for me - I have 5 different ipv6 /64 prefixes across 5 bridges, all with globally routable IPv6 and link-local IPv6 addresses. dnsmasq listens on all bridges and responds correctly to both global and link-local addresses.
bernhardschmidt:
LEDE 17.01 on Buffalo WZR-HP-AG300NH, tested with both dnsmasq-full 2.76 from 17.01 and 2.77test4-1 from trunk
The link-local address of the router is advertised as DNS resolver in the IPv6 router advertisement. Queries to that address are received on the router, logged in dnsmasq, but an answer is never sent (verified with tcpdump).
Tue Apr 4 00:10:20 2017 daemon.info dnsmasq[29569]: 15 fe80::6600:6aff:fe6a:9cf4%br-lan/34427 query[A] www.heise.de from fe80::6600:6aff:fe6a:9cf4
Tue Apr 4 00:10:20 2017 daemon.info dnsmasq[29569]: 15 fe80::6600:6aff:fe6a:9cf4%br-lan/34427 cached www.heise.de is 193.99.144.85
A query to the global address of the very same router works just fine.
The text was updated successfully, but these errors were encountered: