Adguard Plugin does show 0 blocked domains after restart, working fine before restart - reloading solves the issue. Just the regular options active - adaway, adguard, disconnect, yoyo
Apr 24 12:40:01 Lagom adblock-4.1.5[2166]: download of ‘yoyo’ failed, url: https://pgl.yoyo.org/adservers/serverlist.php?hostformat=nohtml&showintro=0&mimetype=plaintext, rule: /^([[:alnum:]-]{1,63}.)+[[:alpha:]]+([[:space:]]|$)/{print tolower($1)}, categories: -, rc: 6, log: curl: (6) Could not resolve host: pgl.yoyo.org
Apr 24 12:40:01 Lagom adblock-4.1.5[2166]: download of ‘disconnect’ failed, url: https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt, rule: /^([[:alnum:]-]{1,63}.)+[[:alpha:]]+([[:space:]]|$)/{print tolower($1)}, categories: -, rc: 6, log: curl: (6) Could not resolve host: s3.amazonaws.com
Apr 24 12:40:18 Lagom adblock-4.1.5[2166]: blocklist with overall 0 blocked domains loaded successfully (Turris Omnia, TurrisOS 7.0.0 3547565f245479dc1643ea66828fb55635d49051)
Apr 26 06:25:19 La*** adblock-4.1.5[933]: Please enable the ‘DNS Report’ option to use the reporting feature
Apr 26 06:25:27 L*** adblock-4.1.5[1036]: Please enable the ‘DNS Report’ option to use the reporting feature
Apr 26 06:25:29 L*** adblock-4.1.5[1131]: Please enable the ‘DNS Report’ option to use the reporting feature
I’m noticing very frequent reboots / crashes, but I haven’t been able to devote time to try to figure out what’s going on. What’s the recommended way to preserve logs across reboots?
Connect a drive and use it in Storage plugin. Then ssh to router and copy /etc/syslog-ng.conf to /etc/syslog-ng.d/logs.conf . Then edit the file and change destination to point inside /srv . Reboot and the logs should also start appearing on the drive.
However, if it’s kernel crashes or a similar problem, the logs won’t probably show what was wrong. For that, it’s best to connect a serial cable and watch the console.
I’ve got msata storage already setup - so I’ll just point syslog-ng over there. Maybe also time to swap out my old kickstarter omnia for a replacement (already have a spare one).
MCU upgrade is experimental and (so far) optional. Running old MCU firmware should not have any bad influence on your router (the new one mostly adds functionality, e.g. to power off a USB port).
My browser (firefox) was the culprit. When using M$ edge, it does work… So finally my dump AP MOX AB(AW7915-NP1)D(2,5GBE) also reached 7.0, even though it was not via update, but via reflashing the SD-card.
Question remaining for me: what are the plans for the further development? First 7.1 with nftables and then 8.0/23.04? (Not speaking of catching up with 9.0 to 24.04…)
I have the same issue, I enabled persistent logs and all, but there is “nothing” in the logs, the Turris Omnia just reboots.
I also checked my power supply, but the issue is the same with a different PSU.
Rolling back to 6.x (Schnapps) fixes the issue too, so it’s definitely software related.
I might have to do this, because so far there is “nothing” in the logs that helps, it just “randomly” reboots, sometimes 2 times in an hour sometimes 2 times in a day.