RUT950 Web Filter (legacy WebUI): Difference between revisions
m (Dziugas moved page Draft:RUT950 Web Filter (legacy WebUI) to RUT950 Web Filter (legacy WebUI) without leaving a redirect) |
m (Dziugas moved page Draft:RUT950 Web Filter (legacy WebUI) to RUT950 Web Filter (legacy WebUI) without leaving a redirect) |
(No difference)
|
Latest revision as of 12:36, 19 July 2021
Main Page > EOL Products > RUT950 > RUT950 Manual > RUT950 Legacy WebUI > RUT950 Services section (legacy) > RUT950 Web Filter (legacy WebUI)The information in this page is updated in accordance with firmware version RUT9XX_R_00.06.09.5.
Note: this user manual page is for RUT950's old WebUI style available in earlier FW versions. Click here for information based on the latest FW version.
Summary
The Web Filter service provides you with the possibility to set up lists of wanted or unwanted websites (Blacklists or Whitelists).
This chapter of the user manual provides an overview of the Web Filter page for RUT950 devices.
Site Blocking
The Site Blocking service provides you with the possibility to create a Blacklist or Whitelist that filters out which websites a user on the local network can access.
The figure below is an example of the Site Blocking page and the table below provides information on the fields contained in that page:
Field | Value | Description |
---|---|---|
Enable | yes | no; Default: no | Turns Site Blocking on or off. |
Mode | Blacklist | Whitelist; Default: Whitelist | Mode of operation.
|
Hosts list | text file; Default: none | Provides a possibility to upload a text file containing a list of hosts instead of adding hosts individually via the WebUI. Different hosts must be separated by line breaks (one host per line) in the text file. |
Enable | yes | no; Default: yes | Turns an entry of the list to an active or inactive state. Inactive entries are not considered to be a part of the list until they are activated. |
Hostname | host; Default: none | Website name. The formats accepted are either www.website.com or website.com, i.e., the protocol and subdomains can be not specified. The rules will also be applicable for the subdomains of the specified site. |
Proxy Based Content Blocker
Proxy Based Content Blocker works in a similar manner to Site Blocking, except with Content Blocker you have the ability to filter out content with more versatility by using the asterisk (*) symbol instead of different extensions and phrases.
For example, instead of having to block multiple domains like website.com, website.net, website.org you can simply create an entry called website.*, which would block all websites whose names begin with website.
Note: a Proxy Based Content Blocker does not work with HTTPS pages, in order to block HTTPS pages please use Site Blocking instead.
The figure below is an example of the Proxy Based Content Blocker page and the table below provides information on the fields contained in that page:
Field | Value | Description |
---|---|---|
Enable | yes | no; Default: no | Turns Proxy Based Content Blocker on or off. |
Mode | Blacklist | Whitelist; Default: Blacklist | Mode of operation.
|
Hosts list | text file; Default: none | Provides a possibility to upload a text file containing a list of hosts instead of adding hosts individually via the WebUI. Different hosts must be separated by line breaks (one host per line) in the text file. |
Enable | yes | no; Default: yes | Turns an entry of the list to an active or inactive state. Inactive entries are not considered to be a part of the list until they are activated. |
URL content | host; Default: none | Website name or part of a website's name. The asterisk (*) symbol stands for anything so it can be used to block different variations of one website. For example:
|
Troubleshooting
Users often find that the Web Filter service doesn't seem to function as expected. In most cases the issue lies not with the functionality of Web Filter itself. Here are some steps to ensure you are using/testing Web Filter correctly (applies to both "Site Blocking" and "Proxy Base URL Content Blocker"):
- Reload your browser. After adding new hostnames to the list, make sure you re-launch your web browser. Web browsers cache previously accessed information so the reason why some sites added to the list don't filter out properly is because the content of those sites had been downloaded and cached prior.
Or you can test immediately after adding new entries to the list with your web browser's non-caching mode. For example, Google Chrome's "Incognito" mode (Ctrl + Shift + N) or Mozilla Firefox's "Private" mode (Ctrl + Shift + P).
- Multiple network interfaces. If your PC has multiple sources for Internet connectivity, make sure it uses the router as its default Internet gateway.
- Multiple domains. Popular sites like Google, Youtube, Facebook, etc. often use multiple domain names. Therefore, sometimes it may be necessary to block more than one domain in order to successfully block a single website.
- Mobile websites. If you're testing Web Filter via a mobile phone, keep in mind that by default mobile devices connect to mobile versions of websites (that usually have names beginning with m.) when they are available. Therefore, it is necessary to also add the mobile hostname as well as the regular one.
- Grammar mistakes. Make sure you have entered the desired hostnames correctly. Often sites aren't blocked because of simple grammar mistakes like typing .comm instead of.com, ww. instead of www. or other general misspellings. If a site is not being blocked properly, check that entry in the Web Filter list.