Closed mpvader closed 5 years ago
summary from the slack discussion:
something, presumably the router, is advertising both working and broken dns servers. at times, connman puts three copies of the bad one in resolv.conf. and no good ones. then things break. Those backported patches remove the duplicates so there's always room for the good one.
Mans was able to reproduce that on his local network; and the patches fixed it there.
Its unclear why this has become a problem in v2.30, perhaps related to the linklocal address additions.
On full cycle of boot until the network-watchdog-initiated-reboot below. As can be seen from the ntp updates, it did have a working dns resolving for a while.
The problem is shown in the dnsmasq lines.
This was system 28480, running v2.30. The problem started occurring after the update from v2.23 to v2.30.