DNS Director would enforce all devices on the LAN to use the router as the DNS resolver, even if they are configured with other DNS settings. This assumes the Director global mode is set to “Router” and LAN DHCP DNS is blank.
Ahh, thanks. Yeah, my clients use the router as the DNS server, so this explains why I didn't see much difference with DNS Director enabled or disabled.
I always set "Global Redirection" on my main router to "Router". As you found you'll notice no difference and so do I.
Thanks for the feedback. I may do that as well.
Looks like something worked itself out... the large list is working perfectly now (no complaints from the fam).
Its the power of diversion. You know @thelonelycoder has tried the hardest to wife-proof and fam-proof diversion. All else fails, create a secondary blocklist that uses "less" blocking. Force the wife and kids devices to the secondary blocklists dns using DNS Director. One feature @thelonelycoder should consider is creating a IPV6 address for the secondary blocklist similarly to how an ipv4 address is generated for it since DNS Director now supports adding a custom ipv6 on most the newer models.... (as a work temporary around, users can already use a mapped Ipv4 to ipv6 addresses for DNS Director IPV6...) <<<--- this is assuming diversion still supports secondary blocklist feature...Looks like something worked itself out... the large list is working perfectly now (no complaints from the fam).
The list owner is so confident in his list that he offers a form to report false positive!Looks like something worked itself out... the large list is working perfectly now (no complaints from the fam).
"
Pixelserv is no longer included with Diversion. (See the latest release notes).
This Mr. oisd (Stephan) runs or at least tested Diversion. On the setup page https://oisd.nl/setup/diversion if you select Diversion in the drop-down a clear instruction is given to change from the Standard to the Large blocking list. Standard uses the small, while large uses the big oisd list.
You answered your own question. Never touch a running system.
glad it was so easy! thanks for the answer
2GB. Give the RAM some room to breathe.
I second this, that ram definitely needs some breathing room when users are pushing the routers to their memory confined limits.
I just switched from standard to large for the sake of science. No swap. Plenty of memory.
# free
total used free shared buffers cached
Mem: 1018788 577800 440988 4484 3904 37912
-/+ buffers/cache: 535984 482804
Swap: 0 0 0what other scripts/router features are you running? I could easily agree with these numbers if all you were running was diversion + large list.
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!