That’s weird to me, unless it suggests only certain traffic triggers some classification/marking that causes a reboot. Is there ever any crashlog in the syslog during the next boot?
The other wildcard is the QoS signature versions between then and now. In the end, I think we’re going to discover that the new GPL and the closed-source components have screwed us over without any recourse.
It would be useful if someone would add a manual iptables rule to a vanilla Adaptive QoS setup and see if any crashes.
Code:
iptables -t mangle -A POSTROUTING -o br0 -p tcp -m multiport --sports 80,443 -m mark --mark 0x80080000/0xc03f0000 -j MARK --set-mark 0x8003ffff/0xc03fffff
iptables -t mangle -A POSTROUTING -o eth0 -p tcp -m multiport --dports 80,443 -m mark --mark 0x40080000/0xc03f0000 -j MARK --set-mark 0x4003ffff/0xc03fffff
Or add just one in case it’s a directional issue, and add the next one if no issues after a day.