New fonctionnality in Parental control

[Bob2016]

Hi,

I'm proposing to add a great new fonctionnality under AIProtection Parental Controls, Time Scheduling.

The grouping fonctionnality. With so much connected devices the grouping will help a lot. The restriction should be applied for every device under the groups.
ex. all the kids devices cellphones, tablet, computer shutoff at 8:00pm. The grouping facilitate the management vs one by one.

A manuel on and off restriction for the group must be a great addition too (with maybe a timer option).
ex. your kids have no school tomorow so you remove the restriction after 8:00pm for 120 minutes.

Your input is welcome to develop the idea. I'm sure everybody with kids will love this kind of features.

By the way very great work with Asus Merlin. I really enjoy my new router with it.

Thanks to consider this
Bob

 

[sfx2000]

This in many ways is a battle that one can not win thru tech alone...

We can do interesting things with DNS, ARP, etc on the router - but this is easily bypassed by a 13 year old boy that wants to surf some pron by disabling WiFi and going to 3G/4G/LTE on his phone... and if he wants his pron, he's gonna find a way...

Even within the constraints - it's easy enough to bypass - DNS blocks on the router - can be bypassed on the client...

It's fun to put some roadblocks - and it's interesting to see how kids work around them - and they will...

Which brings my argument back full circle - be a good parent...

When my kid was of a certain age - we let him onto the internet - but also I showed him up front, that everything was logged, and we would hold him accountable... he pushed things a bit, and I let him know by showing him the logs..

It's more about timing and trust to be honest...

 

[sfx2000]

One can try to fight against something like this - this is a scripted DNSmasq... mostly focused on Ads, but the same thing would apply to any blacklist...

But this can be easily bypassed by setting client DNS to something other that what DHCP offers - and then what?

Dec  3 18:03:57 dnsmasq[5782]: read /etc/pihole/gravity.list - 103819 addresses
Dec  3 18:04:15 dnsmasq[5782]: /etc/pihole/gravity.list edge.quantserve.com is 192.168.1.5
Dec  3 18:04:15 dnsmasq[5782]: /etc/pihole/gravity.list b.scorecardresearch.com is 192.168.1.5
Dec  3 18:04:15 dnsmasq[5782]: /etc/pihole/gravity.list www.googletagservices.com is 192.168.1.5
Dec  3 18:04:38 dnsmasq[5782]: /etc/pihole/gravity.list js-agent.newrelic.com is 192.168.1.5
Dec  3 18:04:38 dnsmasq[5782]: /etc/pihole/gravity.list segment-data.zqtk.net is 192.168.1.5
Dec  3 18:04:38 dnsmasq[5782]: /etc/pihole/gravity.list cdn.yldbt.com is 192.168.1.5
Dec  3 18:04:38 dnsmasq[5782]: /etc/pihole/gravity.list c.amazon-adsystem.com is 192.168.1.5
Dec  3 18:04:58 dnsmasq[5782]: /etc/pihole/gravity.list www.googletagmanager.com is 192.168.1.5
Dec  3 18:04:59 dnsmasq[5782]: /etc/pihole/gravity.list ads.servebom.com is 192.168.1.5
Dec  3 18:05:22 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 18:05:35 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:10:37 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 18:10:38 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:10:38 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 18:16:23 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:16:23 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 18:16:23 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 18:22:04 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 18:22:05 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:22:06 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 18:30:34 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 18:30:35 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:30:35 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 18:33:43 dnsmasq[5782]: /etc/pihole/gravity.list csi.gstatic.com is 192.168.1.5
Dec  3 18:35:42 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 18:35:43 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:35:43 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 18:44:03 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 18:44:03 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 18:44:35 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:57:16 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 18:57:17 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 18:57:17 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 19:04:36 dnsmasq[5782]: /etc/pihole/gravity.list g.symcd.com is 192.168.1.5
Dec  3 19:04:43 dnsmasq[5782]: /etc/pihole/gravity.list id.google.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list partner.googleadservices.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list www.googletagservices.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list tpc.googlesyndication.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list pubads.g.doubleclick.net is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list stats.g.doubleclick.net is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list googleads.g.doubleclick.net is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list pixel.quantserve.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list edge.quantserve.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list www.addthis.com is 192.168.1.5
Dec  3 19:04:58 dnsmasq[5782]: /etc/pihole/gravity.list sp.udimg.com is 192.168.1.5
Dec  3 19:05:57 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 19:19:07 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 19:19:08 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 19:19:08 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 19:28:37 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 19:28:38 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 19:28:38 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5
Dec  3 19:48:29 dnsmasq[5782]: /etc/pihole/gravity.list www-google-analytics.l.google.com is 192.168.1.5
Dec  3 19:48:30 dnsmasq[5782]: /etc/pihole/gravity.list z-na.amazon-adsystem.com is 192.168.1.5
Dec  3 19:48:30 dnsmasq[5782]: /etc/pihole/gravity.list pagead2.googlesyndication.com is 192.168.1.5

 

[RMerlin]

But this can be easily bypassed by setting client DNS to something other that what DHCP offers - and then what?

Using DNSFilter on my firmware will prevent that. It creates an iptables rule that redirect all port 53 connections to a specific IP address. It will allow you to lock someone into a DNS of your choice (such as OpenDNS). Bypassing it would require either a VPN tunnel, or a hotspot other than your router.

 

[sfx2000]

Using DNSFilter on my firmware will prevent that. It creates an iptables rule that redirect all port 53 connections to a specific IP address. It will allow you to lock someone into a DNS of your choice (such as OpenDNS). Bypassing it would require either a VPN tunnel, or a hotspot other than your router.

Don't be so sure about that - there's always a way...

 

[RMerlin]

Don't be so sure about that - there's always a way...

If you're connecting to port 53, you're getting redirected by iptables if that feature is enabled. I don't see any way around that.

 

[BiffMalibu]

This in many ways is a battle that one can not win thru tech alone...

We can do interesting things with DNS, ARP, etc on the router - but this is easily bypassed by a 13 year old boy that wants to surf some pron by disabling WiFi and going to 3G/4G/LTE on his phone... and if he wants his pron, he's gonna find a way...

Even within the constraints - it's easy enough to bypass - DNS blocks on the router - can be bypassed on the client...

It's fun to put some roadblocks - and it's interesting to see how kids work around them - and they will...

Which brings my argument back full circle - be a good parent...

When my kid was of a certain age - we let him onto the internet - but also I showed him up front, that everything was logged, and we would hold him accountable... he pushed things a bit, and I let him know by showing him the logs..

It's more about timing and trust to be honest...

I agree, but my guess is that Bob did not have the horny 13 yr old in mind, but rather the 6+ yr olds that sneak their way onto their various devices as soon as mum/dad isn't watching? It's a time consuming struggle, and the "I'm logging you" thing... well, my 6 yr old is not that impressed.

So, this would be a very welcome addition and a possibility to put Disney's Circle out of the market.