Hallo Turris community,
I have a problem with DNS resolver on my Turris.
Every now and then the PC connected to the LAN interface of Turris stops resolving DNS queries and when I login to Turris and try to resolve a query from there, it fails too:
root@turris:~# dig www.debian.org
; <<>> DiG 9.11.5 <<>> www.debian.org
;; global options: +cmd
;; connection timed out; no servers could be reached
In the Turris syslog I see these messages:
root@turris:~# grep -i crash /var/log/messages
2018-12-10 21:47:51 info procd: Instance kresd::instance1 s in a crash loop 6 crashes, 232 seconds since last crash
2018-12-11 01:35:41 info procd: Instance kresd::instance1 s in a crash loop 6 crashes, 46 seconds since last crash
2018-12-11 16:23:57 info procd: Instance kresd::instance1 s in a crash loop 6 crashes, 286 seconds since last crash
I wasn’t able to find more crash information in system logs (please let me know where to look eventually).
Turris was reset by the three LED reset mode (2 red and one green) into the factory reset state and the initial configuration wizard has been skipped from step 3.
The Atheros 5G wifi card is in Client mode, connected to access point. The 5G wifi card interface is added into the WAN firewall zone.
The AP provides DHCP/DNS information to Turris and Turris runs DHCP/DNS in default configuration for the LAN clients.
My PC is connected via wire to one of the LAN switch ports.
The wired WAN port is not used.
Normally if I toggle the 5G wifi interface off and on using LuCI, the kresd is started and everything works for some time. After a while, DNS resolving starts to fail and I have to manually stop and start the wireless interface or restart resolver or reboot Turris.
It is very annoying and I have no clue how to workaround this.
Please help with any advice.