This is a continuation of this topic.(Creating this new topic because the problem is now related to AdBlock)
I tried both adblock and adblock-fast. After any of these Adblock runs for about 10 hours, the built-in USB modem gets disconnected with no logs related to the USB itself or from Adblock (please refer to the other topic for a complete idea of the logs).
Device Model: TOZED ZLT S12 PRO
Snapshot Version: 23.05.2 (r23630-842932a63d)
Kernal Version: 5.15.137
Total Device Memory: 256MB
Used about 70MB without Adblock enabled, and 100-150MB with Adblock enabled.
I'm no expert on this topic, but what could be the trigger for the usb0 going down?
This could be power related issue. With adblock turned on, modem device is not receiving enough power to maintain connection. Only after adblock is off, that extra power released by that is enough to keep the connection alive.
I would try again with powered usb hub and see if anything changes.
Does not actually run for 10 hours, it preps the block-list for dnsmasq/smartdns/unbound and exits.
Does not log anything outside of the short start/stop sequences.
I'd test the adblock-fast with the smallest block-list (which is pretty much like not using adblocking at all) to test the hypothesis of any correlation of using adblocking and losing the USB modem.
It looks like the issue lies with the DNS resolver. After testing dnsmasq and smartdns, the problem persisted. However, after installing unbound, I haven't noticed any issues with usb0 going down in the last 24 hours. So, installing unbound seems to have resolved the problem. I'm curious about the specific differences that unbound introduces compared to other resolvers.