Cisco Cisco Web Security Appliance S690 User Guide

Enable P2 (you must also enable P1 if not already enabled) (see 

Access the CLI.

Use the 

advancedproxyconfig 

-> 

miscellaneous 

commands to access the required area 

example.com> advancedproxyconfig

Choose a parameter group:

- AUTHENTICATION - Authentication related parameters

- CACHING - Proxy Caching related parameters

- DNS - DNS related parameters

- EUN - EUN related parameters

- NATIVEFTP - Native FTP related parameters

- FTPOVERHTTP - FTP Over HTTP related parameters

- HTTPS - HTTPS related parameters

- SCANNING - Scanning related parameters

- PROXYCONN - Proxy connection header related parameters

- CUSTOMHEADERS - Manage custom request headers for specific domains

- MISCELLANEOUS - Miscellaneous proxy related parameters

- SOCKS - SOCKS Proxy parameters

[]> miscellaneous

Press Enter past each question until the question:

Do you want proxy to listen on P2?

 

Enter ‘y’ for this question.

Press Enter past the remaining questions.

Commit your changes.

If you enable P2 to listen for client requests using the 

advancedproxyconfig > miscellaneous

 CLI 

command, you can choose whether to use P1 or P2 for outgoing traffic. To use P1 for outgoing traffic, 
change the Default Route for data traffic to specify the next IP address that the P1 interface is connected 
to. 

.

.

Routes are used for determining where to send (or route) network traffic. The Web Security appliance 
needs to route the following kinds of traffic: 

Data traffic. Traffic the Web Proxy processes from end users browsing the web.

Management traffic. Traffic created by managing the appliance through the web interface and 
traffic the appliance creates for management services, such as AsyncOS upgrades, component 
updates, DNS, authentication, and more.