DansGuardian Documentation Wiki

You are here: Main Index » network_billboard


|

Wiki Information

Differences

This shows you the differences between the selected revision and the current version of the page.

network_billboard 2008/12/14 16:29 network_billboard 2008/12/25 16:33 current
Line 1: Line 1:
====== Network Billboard ====== ====== Network Billboard ======
===== The Problem ===== ===== The Problem =====
-Imagine a non-technical kid that gets a new iPhone for Christmas, takes it to school, then starts up the web browser and accesses the web. With a [[Two Configuration Families#Family One: Transparent-Intercepting|"transparent-intercepting" configuration]], web access it's likely to work, and even if it doesn't at least a message can be displayed easily. But with a plain old [[Two Configuration Families#Family Two: Explicit-Proxy|"explicit-proxy" configuration]], the web browser may be totally unresponsive, and the kid will have no idea why or what to do about it. +Imagine a non-technical kid that gets a new iPhone for Christmas, takes it to school, then starts up the web browser and accesses the web. With a [[Two Configuration Families#Family One: Transparent-Intercepting|"transparent-intercepting" configuration]], web access is likely to work, and even if it doesn't at least a message can be displayed easily. But with a plain old [[Two Configuration Families#Family Two: Explicit-Proxy|"explicit-proxy" configuration]], the web browser may be totally unresponsive, and the kid will have no idea why or what to do about it.
It's very important to avoid reaching a "dead end" like this. It's very important to avoid reaching a "dead end" like this.
This one seeming advantage of "transparent-intercepting" configurations is so significant it sometimes outweighs all other considerations put together. This one seeming advantage of "transparent-intercepting" configurations is so significant it sometimes outweighs all other considerations put together.
 +
===== The Solution ===== ===== The Solution =====
If it was just possible to eliminate this one disadvantage of an "explicit-proxy" configuration... Well, __//it is possible//__ to make a display that a new/unexpected/naive device will always see no matter what. All that's needed is a "network billboard" that will display a message to even new/unexpected/naive devices (such as the example iPhone). This document describes how to set up such a thing. If it was just possible to eliminate this one disadvantage of an "explicit-proxy" configuration... Well, __//it is possible//__ to make a display that a new/unexpected/naive device will always see no matter what. All that's needed is a "network billboard" that will display a message to even new/unexpected/naive devices (such as the example iPhone). This document describes how to set up such a thing.