I had to turn off rebind protection. It broke dozens of commercial websites for me.
19:17:43 blocked by blockinglist www.googletagservices.com
19:17:44 blocked by blockinglist ssl.google-analytics.com
19:17:44 blocked by blockinglist sb.scorecardresearch.com
19:17:44 blocked by blockinglist cdn-gl.imrworldwide.com
19:17:44 blocked by blockinglist s.amazon-adsystem.comMaybe you can try and see which one of those is not blocked when you are on 'small blacklist' and then whitelist the domain when you switch to standard . Could be a 'middle' domain which causes this issue
Yep, they both need to be on the blocklist. www.domain.com is different than domain.com. Diversion does support wildcard-blacklist, too.Hello
What exactly do I have to do so that domains are always blocked with and without www.? Both domain options must be on the lock list or not?
Thanks.
Why use Adguard DNS upstream? You can just import their blocklist if you really want (it's on GitHub) and use a more reliable upstream provider (Quad9, Cloudflare).
Of course I know that. But this is a very different question...Now I need to figure out why this errors occurs
/opt/bin/diversion: /opt/share/diversion/file/functions.div line 1776 syntax error unexpected ";;" (expecting "then")Aug 15 19:30:26 kernel: pixelserv-tls[7848]: unhandled level 0 translation fault (11) at 0x47bf3e0dd00, esr 0x92000004
Aug 15 19:30:26 kernel: pgd = ffffffc011a5d000
Aug 15 19:30:26 kernel: [47bf3e0dd00] *pgd=0000000000000000, *pud=0000000000000000
Aug 15 19:30:26 kernel: CPU: 0 PID: 7848 Comm: pixelserv-tls Tainted: P O 4.1.27 #2
Aug 15 19:30:26 kernel: Hardware name: Broadcom-v8A (DT)
Aug 15 19:30:26 kernel: task: ffffffc01393eb40 ti: ffffffc00a78c000 task.ti: ffffffc00a78c000
Aug 15 19:30:27 kernel: PC is at 0x7f8cdeae80
Aug 15 19:30:27 kernel: LR is at 0x7f8cdeb574
Aug 15 19:30:27 kernel: pc : [<0000007f8cdeae80>] lr : [<0000007f8cdeb574>] pstate: 80000000
Aug 15 19:30:27 kernel: sp : 0000007fc6ccba60
Aug 15 19:30:27 kernel: x29: 0000007fc6ccba60 x28: 0000007f8ce09000
Aug 15 19:30:27 kernel: x27: 0000007f8ce08000 x26: 0000007fc6ccc370
Aug 15 19:30:27 kernel: x25: 0000007f8cdf4000 x24: 0000000000000001
Aug 15 19:30:27 kernel: x23: 0000007fc6ccbc00 x22: 0000000000000000
Aug 15 19:30:27 kernel: x21: 0000007f8ce02ca0 x20: 0000000000000010
Aug 15 19:30:27 kernel: x19: 0000007f8ce033a0 x18: 0000000000000001
Aug 15 19:30:27 kernel: x17: 0000007fc6ccc4b8 x16: 0000000000554e47
Aug 15 19:30:27 kernel: x15: 0000007f8ce0a700 x14: 0000000000000000
Aug 15 19:30:27 kernel: x13: 0000007f8ce09008 x12: 0000000000000040
Aug 15 19:30:27 kernel: x11: 0000000000000001 x10: 0000000000000010
Aug 15 19:30:27 kernel: x9 : 0000000000000000 x8 : 0000007f8ce028b8
Aug 15 19:30:27 kernel: x7 : 0000000000000000 x6 : 0000000000000000
Aug 15 19:30:27 kernel: x5 : 0000000000000004 x4 : 0000007f8ce033b0
Aug 15 19:30:27 kernel: x3 : 0000007f8ce03340 x2 : fffffffffffffff0
Aug 15 19:30:27 kernel: x1 : 0000007f8cdfb3a0 x0 : 0000007f8ce033a0
Do you have all the requirements met?
Login to your router admin page, and go to System Log > General Log. Under "System Time", is the time set correctly?
Figured as much. Reboot it from the admin console. Had the same issue.
Yes, in the web UI at the top. Then check the time and date again.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!
