I've got a couple of kids in the house, and the oldest one is getting old enough to get curious on the 'net. I've got a setup here I'm pretty happy with.
I'm running DD-WRT on my border firewall, and use OpenDNS to to parental filtering on the DNS side. OpenDNS now has a service called DNSoMatic, which updates multiple DDNS providers including OpenDNS. So, DD-WRT runs DDNS to DNSoMatic using a custom script as well as updating the DNS provider for realitycheckBBS.org.
DD-WRT gives the IP addresses for OpenDNS as DNS for my clients. I have all of my computers and systems configured with static DHCP reservations, so any system that's gotten a DHCP reservation in the open range is a kid's system.
OpenDNS has some nice logging capabilities of blocked sites, I'm considering showing the list of sites my son's tried to get to for shock value sometime.
:)
Under Access controls, I have the kids' systems configured for internet access between 9:00am and 6:00pm. Right now I'm using MAC addresses, but once I get all of the Apple TVs and set top stuff on static IPs, I'll apply that rule to the whole dynamic IP range.
There's one more rule across the range to disallow DNS redirection, so the kids couldn't change the DNS settings on their systems to point to another DNS server.
The bigger builds of DD-WRT include Privoxy, and I'm playing with that now.
The kids have a "safe" google account that's used on the set tops, with YouTube parental controls set. The kids log in with those credentials.
It's a start and gives me a little piece of mind, only using free software and services and an inexpensive router.
---
þ Synchronet þ realitycheckBBS --
http://realitycheckBBS.org