
Features
Specs
FAQ
History
|
FilterWall Frequently Asked Questions
Current FilterWall Owners
-
-
-
-
-
-
-
-
Prospective FilterWall Owners
-
-
-
-
Current FilterWall Owners
-
| A: | Look at the back of the machine. If you only see 2 ethernet ports,
then you do not have a DMZ enabled FilterWall -- contact us
if you wish to upgrade.
|
-
| A: | Web pages are usually current, but if you want to be absolutely sure use
the "force reload" feature of your browser. Make sure your FilterWall clock is set correctly to provide maximum cache efficiency.
Further explanation:
- the web caching algorithm follows the content expiration date
provided by many web servers
- if no content expiration is provided, the web server is queried
for the modification date and compared to the date of the cached copy
- browser force-reload requests are always honored
NOTE: FilterWall Version 2.1 includes a workaround for a bug in
IE browsers < 5.2 that broke force-reload option
|
-
| A: | From the main web administration page, go to "Service Policies->Outgoing".
Add a new entry with port 443. To block https from only a specific server,
enter the server's address as the ip and "255.255.255.255" as the netmask.
To block all https traffic, enter "0.0.0.0" for both ip and netmask.
|
-
| A: | Just block all access to login.oscar.aol.com; right now login.oscar.aol.com
corresponds to the ip addresses 64.12.161.185 and 64.12.161.153.
Note these addresses might change in the future.
From the main web administration page, go to "Service Policies->Outgoing".
Add a new entry for each ip above, with netmask "255.255.255.255" and the
port "0".
|
-
| A: | It is difficult to provide complete coverage for these proxies, but
the following steps greatly limit this problem
- block port 8080
- block https (port 443) and http (use web filter) access to all known anonymizer proxy servers
|
-
| A: | The limiting factor in most installations will be the connection to the
Internet. A T1 line can handle approximatesly 30,000 web requests/hour.
|
-
| A: | This indicates that the web page is non-cacheable, and the server portion
of the url must be added to the list of uncached sites.
Example: if the url http://www.vctlabs.com/a_page.html gave this error,
then add "www.vctlabs.com" under "Service Policies->Caching"
|
-
| A: | There are two possible reasons for this error:
- the remote web server is having problems, and is dropping connections
- your internet connection is congested, and the resulting delays are causing
errors in connections
|
Prospective FilterWall Owners
-
| A: | None! If your network is already hooked up to the Internet, the FilterWall
package provides everything needed to install it.
|
-
| A: | If you have servers that must be accessed from the Internet (such as mail
or web servers), then a DMZ is recommended.
|
-
| A: | Cache efficiency is sensitive to network usage patterns, but typically
the efficiency ranges from 40-50% cache hits/web request.
|
-
|