Content Gateway (web proxy) interfaces (P1 and P2)

Content Gateway interfaces P1 and P2 handle traffic directed to and from the Content Gateway proxy module.

Both the P1 and P2 proxy interfaces can be used to accept users’ Internet requests (inbound traffic) and communicate with web servers (outbound traffic). In other words, both interfaces can be configured to handle traffic into and out of the proxy module.
A typical configuration is to use P1 for both inbound and outbound traffic; P2 is not used.
Another option is to configure P1 to accept users’ Internet requests (inbound only). In this case, P2 is configured to communicate with web servers (outbound).
Important:
If you use the P2 interface, the P1 interface is bound to eth0, and the P2 interface is bound to eth1. Keep this in mind when you configure Content Gateway.

For example, suppose you are using a transparent proxy deployment, and the P1 interface is connected to a WCCP router. In this case, you must configure Content Gateway to use eth0 for WCCP communications (in Content Gateway Manager, see the General tab of the Configure > Networking > WCCP page).
To view the interface bindings in the CLI:
```
(view)# show interface info
```