jimr17 wrote:I've not been pointed to any authoritative source that it is against church policy since it does not circumvent any security the church puts in place, just supplements it to allow granular control of sites that the church hardware lets through the firewall.
There are two methods used in getting Internet access for units. The first is by sharing the Church provided Internet access for a family history center, a facilities management office, and so on. The policies for the family history center computers, networks, and Internet connections are the provided by the Area Family History Support Office and are contained in two documents. The first is the Policy and Guidelines For Computers in Family History Centers
, and the second is the Family History Center Internet Use Policies
(Available at the FHC and through the Family History Online Guide - requires username and password for access). The second Internet access method is through the Broadband Meetinghouse Internet Services in Meetinghouses program. Other than the Church provided security and Internet filtering
, the policies for this program are left up to the stake president.
It is important to note that shared use of a Church provided Internet connection should not interfere with the primary user's activities. For the purpose of simplicity I will be refering to units sharing an FHC Internet connection. The FHC Internet user policies state:
Altering Hardware or Software
- No one may modify, alter, or disable the Internet filter hardware or software supplied by Church headquarters.
With that in mind, how you employ a filtering solution such as OpenDNS depends on how a unit connects to the Internet. A unit connecting to the Internet through a FHC connection would have to employ a solution that does not alter or interfere with the FHC Internet connection without obtaining approval and support from the Area Family History Support Office. Setting up a unit sub-network off the FHC firewall employing another firewall device using OpenDNS would not interfere with the FHC network. That may be the simplest solution. It permits both wired connections and wireless connections with added filtering.
When using OpenDNS for added filtering there are two options that are available. The first is to use a router/firewall configuration. The second is to configure individual devices. For wireless operations this would be done at the wireless access point(s).
For any added filtering option employed you must consider the added complexity for support. While you may be comfortable understanding and maintaining the configuration, will your successor? Also contributing to potential difficulties will be the level of support you will be able to get from Church headquarters. Church headquarters may not be able to help you with non-standard networks behind the Church provided firewall.
It is for these reasons that I have not implemented a solution such as OpenDNS for networks and systems under my care.