Then, check these settings by entering show ip urlfilter:
The filter is applied to the correct interface.
The filter is applied to traffic in the correct direction (usually inbound on
an Ethernet interface or outbound on a WAN interface).
The Websense server's IP address is correct.
The router has connected to a Websense server.
Figure 7-1 shows the output from the show ip urlfilter command.
ProCurve# show ip urlfilter
Configured for Websense URL filtering.
Filters
-------
Name: "MyFilter"
Ports: HTTP(80)
Interfaces that filter is applied to:
ppp 1 outbound
Servers
-------
IP address: 192.168.1.20
*ACTIVE*
Port: 15868
Timeout: 5 seconds
IP address: 192.168.1.19
Port: 15868
Timeout: 5 seconds
Excluded domains
----------------
Permit www.hp.com
Permit www.procurve.com
Other Settings
--------------
Allow mode: Off
Maximum outstanding requests: 500
Maximum number of response packets buffered: 100
Figure 7-1. Viewing Web Content Filtering Settings
Fix any misconfigurations. For example, if you see that the filter has not been
applied to any interfaces, move to the correct interface configuration mode
context and apply the filter.
While viewing these settings, check the Allow mode. It is perfectly acceptable
for Allow mode to be enabled. However, in this case, when the router cannot
reach the Websense server, it will allow all traffic—a good description of your
Troubleshooting Web Content Filtering
Has the router
connected to the server?
What is the
Allow mode?
Content Filtering
Is the filter correctly
applied to an interface?
Is the Websense server's
address correct?
7-15