Added support for FamilyShield from OpenDNS

With a very minor code change, individuals can now implement restrictions on dangers, disturbing, or otherwise adult oriented content without the need for managed restrictions.
This is a fairly non-invasive change and will benefit users who intend to use VPN for home or small business uses where access to such material may be undesirable.
This commit is contained in:
justinamcafee 2018-03-10 17:33:31 -06:00 committed by GitHub
parent 1e87850952
commit 2895b9bfb7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -771,6 +771,7 @@ setDNS() {
Comodo "" Comodo ""
DNSWatch "" DNSWatch ""
Quad9 "" Quad9 ""
FamilyShield ""
Custom "") Custom "")
# In a whiptail dialog, show the options # In a whiptail dialog, show the options
DNSchoices=$(whiptail --separate-output --menu "Select Upstream DNS Provider. To use your own, select Custom." ${r} ${c} 7 \ DNSchoices=$(whiptail --separate-output --menu "Select Upstream DNS Provider. To use your own, select Custom." ${r} ${c} 7 \
@ -817,6 +818,10 @@ setDNS() {
PIHOLE_DNS_1="9.9.9.9" PIHOLE_DNS_1="9.9.9.9"
PIHOLE_DNS_2="149.112.112.112" PIHOLE_DNS_2="149.112.112.112"
;; ;;
FamilyShield)
echo "FamilyShield servers"
PIHOLE_DNS_1="208.67.222.123"
PIHOLE_DNS_2="208.67.220.123"
Custom) Custom)
# Until the DNS settings are selected, # Until the DNS settings are selected,
until [[ "${DNSSettingsCorrect}" = True ]]; do until [[ "${DNSSettingsCorrect}" = True ]]; do