I have a RT-AC86U, on firmware 386.12.4. A few times per hour, all the wifi clients would disconnect for a few seconds, and reconnect.
The log showed that when the disconnect happens, Diversion restarted Dnsmasq and appeared to have triggered YazFi to restart
If I uninstall YazFi, the disconnect will not happen but "Diversion: restarted Dnsmasq to apply settings" still exists. Hence I believe the problem still exists.
I am running
Attached is the syslog. Entries from Skynet were removed
Thanks in advanced.
Also, it would be nice bonus if there is a solution to remove these logs. I have already forced remove and then re-install bind-dig, bind-libs and libuv based on this post
The log showed that when the disconnect happens, Diversion restarted Dnsmasq and appeared to have triggered YazFi to restart
Code:
Jan 26 18:08:12 Diversion: restarted Dnsmasq to apply settings
Jan 26 18:08:14 YazFi: YazFi v4.4.4 starting up
If I uninstall YazFi, the disconnect will not happen but "Diversion: restarted Dnsmasq to apply settings" still exists. Hence I believe the problem still exists.
I am running
- Diversion 5.0,
- Skynet 7.5.6 and
- YazFi 4.4.4.
Attached is the syslog. Entries from Skynet were removed
Thanks in advanced.
Also, it would be nice bonus if there is a solution to remove these logs. I have already forced remove and then re-install bind-dig, bind-libs and libuv based on this post
Code:
Jan 26 18:04:33 kernel: pgd = ffffffc016215000
Jan 26 18:04:33 kernel: [00000000] *pgd=000000001709c003, *pud=000000001709c003, *pmd=0000000010f0c003, *pte=0000000000000000
Jan 26 18:04:33 kernel: CPU: 1 PID: 14090 Comm: dcd Tainted: P O 4.1.27 #2
Jan 26 18:04:33 kernel: Hardware name: Broadcom-v8A (DT)
Jan 26 18:04:33 kernel: task: ffffffc010f8b5c0 ti: ffffffc011e70000 task.ti: ffffffc011e70000
Jan 26 18:04:33 kernel: PC is at 0xf6d7cf44
Jan 26 18:04:33 kernel: LR is at 0x1dce0
Jan 26 18:04:33 kernel: pc : [<00000000f6d7cf44>] lr : [<000000000001dce0>] pstate: 600b0010
Jan 26 18:04:33 kernel: sp : 00000000ffc95a48
Jan 26 18:04:33 kernel: x12: 00000000000a2050
Jan 26 18:04:33 kernel: x11: 00000000f60ff024 x10: 00000000000a23c4
Jan 26 18:04:33 kernel: x9 : 00000000f60ff684 x8 : 00000000000a287c
Jan 26 18:04:33 kernel: x7 : 00000000f60ff6bc x6 : 00000000000a2876
Jan 26 18:04:33 kernel: x5 : 0000000000000000 x4 : 00000000f60ff668
Jan 26 18:04:33 kernel: x3 : 0000000000000000 x2 : 00000000ffc95a24
Jan 26 18:04:33 kernel: x1 : 000000000007d72e x0 : 0000000000000000
Jan 26 18:04:33 kernel: CPU: 1 PID: 14090 Comm: dcd Tainted: P O 4.1.27 #2
Jan 26 18:04:33 kernel: Hardware name: Broadcom-v8A (DT)
Jan 26 18:04:33 kernel: task: ffffffc010f8b5c0 ti: ffffffc011e70000 task.ti: ffffffc011e70000
Jan 26 18:04:33 kernel: PC is at 0xf6d7cf44
Jan 26 18:04:33 kernel: LR is at 0x1dce0
Jan 26 18:04:33 kernel: pc : [<00000000f6d7cf44>] lr : [<000000000001dce0>] pstate: 600b0010
Jan 26 18:04:33 kernel: sp : 00000000ffc95a48
Jan 26 18:04:33 kernel: x12: 00000000000a2050
Jan 26 18:04:33 kernel: x11: 00000000f60ff024 x10: 00000000000a23c4
Jan 26 18:04:33 kernel: x9 : 00000000f60ff684 x8 : 00000000000a287c
Jan 26 18:04:33 kernel: x7 : 00000000f60ff6bc x6 : 00000000000a2876
Jan 26 18:04:33 kernel: x5 : 0000000000000000 x4 : 00000000f60ff668
Jan 26 18:04:33 kernel: x3 : 0000000000000000 x2 : 00000000ffc95a24
Jan 26 18:04:33 kernel: x1 : 000000000007d72e x0 : 0000000000000000
Last edited: