1. Assign a password to the router
2. Change all 3 DNS servers to reference OpenDNS' DNS servers instead
of the ISP's DNS servers
3. Create an account on OpenDNS
4. Install the OpenDNS Client updater on a PC to retain filtering
preferences when the public IP changes(for dynamic IP addresses)
5. Set filtering preferences on OpenDNS
6. On Windows PCs, Install the free Bluecoat K9 Web Protection client
software and set filtering preferences
Now comes the loosely related open source question. One of the
weaknesses of the above approach is the dependence on number 4.
OpenDNS needs to know the IP address being used in order to enforce
specific filtering preferences. If the client IP address changes and
OpenDNS isn't notified the filtering preferences are lost.
My thought is there might be a way to use custom firmware such as DD-
WRT or Tomato and somehow include the Dynamic DNS update for a content
filtering service such as OpenDNS.
I'd like to address this weakness in my approach and receive
suggestions on how to implement it without paying for software. Any
ideas? What do you use?
Lars Rasmussen
Springville, Utah
--
You received this message because you are subscribed to the Google
Groups "LDSOSS" group.
To post to this group, send email to lds...@googlegroups.com
To unsubscribe from this group, send email to
ldsoss-un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/ldsoss?hl=en
Visit our wiki at http://ldsoss.org!
Yes, but how do you use that with OpenDNS?
Currently I'm using openwrt kamikaze (xwrt branch - http://x-wrt.org/
) at home and have written a small app to do the opendns update from
that platform and run it in my crontab. It would be absolutely trivial
if opendns didn't require the update session to be ssl. Haven't looked
at it since I wrote it - my guess it openwrt supports this out of the
box but where is the fun in that? If you want, I can send you the
source or the binary.
I installed a second wrt running Gargoyle (openwrt derivative):
http://en.wikipedia.org/wiki/Gargoyle_Router_Firmware. I noticed it
has opendns support out of the box. Again, I expect stock openwrt does
the same.
On the router I add a forwarding rule that blocks all port 53 traffic
- since the forwarding rule doesn't apply to packets destined to the
router or originated from the router, the router can do dns lookups
against opendns but the computers behind the router have accept the
dhcp offered dns servers (the router). This eliminates the possibility
that someone manually configures different dns servers on a computer
in the house.
Having linux on this device is great. My firewall rules change on
sunday and late at night to a more restrictive profile, I do string
matching in forwarded packets for stuff I don't want in the house, and
I keep a record of all image urls that pass through the device. For a
while I had it change all youtube thumbnails to pictures of barney.
Now I just block youtube. Cool toy for $50.
--
You received this message because you are subscribed to the Google
Groups "LDSOSS" group.
To post to this group, send email to lds...@googlegroups.com
To unsubscribe from this group, send email to
ldsoss-un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/ldsoss?hl=en
Visit our wiki at http://ldsoss.org!
he is trying to get the part of opendns working which allows opendns
to associate a policy with the source ip address of the dns request.
To do that something needs to be contacting opendns saying "hey, the
ip address of my cable modem is y.y.y.y."
Thank You!
--
Lars
additional details:
OpenDNS + K9 + DynDNS +Tomato firmware on the router intercepting all
DNS UDP port 53 requests.
Tomato also allows me to 'Block All Internet Access' or to disable
wireless during certain hours. Even with all this tech you still need
to physically secure the router and other equipment that grants open
ethernet access(like cable/DSL "modems") if you want to lock things
down.
I also install Firefox with the Adblock Plus extension as many ads are
offensive/distracting/take up space on the page and bandwidth.
With Tomato I don't need a DDNS client/service installed on one of the
computers when the Dyanmic IP address changes.
http://www.hugolarge.com/2009/01/using-multiple-ddns-providers-with-tomato-firmware/