I’m glad things are running stable, but it’s an unsatisfying ending in terms of understanding the root cause. Your log shows amas_lib restarting the firewall, which is related to AiMesh.@dave14305 just as an update a rooter reboot fixed the issue . I've been playing the streamer for hours today and no issues so far. The only thing that started to happen after the reboot I get frequent firewall restarts and the below is what I get in the syslog. Any idea what may be casing this?
Code:Jan 2 15:33:58 RT-AC86U-4AB0 kernel: br0: received packet on wl0.1 with own address as source address Jan 2 15:34:56 RT-AC86U-4AB0 dnsmasq-dhcp[27149]: DHCPREQUEST(br0) 192.168.1.79 80:2b:f9:1b:86:ef Jan 2 15:34:56 RT-AC86U-4AB0 dnsmasq-dhcp[27149]: DHCPACK(br0) 192.168.1.79 80:2b:f9:1b:86:ef DESKTOP-V8J7HQR Jan 2 15:35:26 RT-AC86U-4AB0 rc_service: amas_lib 1424:notify_rc restart_firewall Jan 2 15:35:26 RT-AC86U-4AB0 kernel: 80:2B:F9:1B:86:EF already exist in UDB, can't add it Jan 2 15:35:26 RT-AC86U-4AB0 custom_script: Running /jffs/scripts/service-event (args: restart firewall) Jan 2 15:35:26 RT-AC86U-4AB0 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0) Jan 2 15:35:26 RT-AC86U-4AB0 custom_script: Running /jffs/scripts/firewall-start (args: ppp0) Jan 2 15:35:26 RT-AC86U-4AB0 custom_script: Running /jffs/scripts/service-event-end (args: restart firewall) Jan 2 15:35:26 RT-AC86U-4AB0 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=11554) called in unattended mode with 1 args: -start Jan 2 15:35:26 RT-AC86U-4AB0 FlexQoS: Applying iptables static rules Jan 2 15:35:26 RT-AC86U-4AB0 FlexQoS: Applying iptables custom rules Jan 2 15:35:27 RT-AC86U-4AB0 FlexQoS: Flushing conntrack table Jan 2 15:35:27 RT-AC86U-4AB0 FlexQoS: No TC modifications necessary Jan 2 15:35:34 RT-AC86U-4AB0 kernel: htb: htb qdisc 16: is non-work-conserving?