What you have is very similar to what diversion does, but with diversion you get push button customized configuration of this type of blocking which is very valuable to the less technically inclined. Diversion offers error checking and a nice, friendly interface to bring something like your script to those who have no idea what it means or how to implement it. It’s much less trouble for most.
Yup, then six years go by, your code has evolved and you find yourself posting a reply just as this one
I found it slightly amusing that even six years later your script is almost identical to the original version of this script. I guess that's proof it's still the best technique.
The main difference of course is that because your script is for stock Asus firmware it won't survive a reboot.
As you found out, Diversion auto-rewrites any <IP domain> pair to <blockingIP domain> in the blocking file and both blacklists.
As you found out, Diversion auto-rewrites any <IP domain> pair to <blockingIP domain> in the blocking file and both blacklists.
Your feature request would be an additional separate file that gets added to Dnsmasq. I'm not sure this is within the scope of Diversion.
You all would have to convince me this is a welcome and fitting addition
I might be misunderstanding. It seems you want to redirect outgoing URLs from your router clients to "safe" sources. I see Diversion as blocking incoming unwanted / objectionable / malicious contest. What you seek might be better for a new script or a "family / safe" DNS provider or the router DNS Filter? Apologies if I don't understand what you seek.
Ahem, Dnsmasq blocks outgoing requests in Diversion.
No, using a VPN on the client will completely bypass Diversion or any other router-based DNS server (assuming it's configured to do that).
That looks fine to me, open 192.168.1.3/servstats in a browser to see if pixelserv-tls is busy or not.
You're playing whack-a-mole with your kids here. At least you're teaching them about technology as they have to go to greater and greater lengths to get around your blocks.
you can start by blocking the standard openVPN server ports for connections from their clientsYou're playing whack-a-mole with your kids here. At least you're teaching them about technology as they have to go to greater and greater lengths to get around your blocks.
Next thing to do is figure out how to block their VPN connections. That's beyond my knowledge though.
That would be a configuration setting (if available) on the VPN client. It's nothing to do with the router.
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!
