18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 9: Configuring Proxies<br />

Using other proxies on the <strong>Sidewinder</strong> <strong>G2</strong><br />

Using other<br />

proxies on the<br />

<strong>Sidewinder</strong> <strong>G2</strong><br />

Transparent &<br />

non-transparent<br />

proxies<br />

254<br />

In special cases, you may want to set up a UDP proxy or a TCP proxy service<br />

that is not preconfigured when you install the <strong>Sidewinder</strong> <strong>G2</strong>. The <strong>Sidewinder</strong><br />

<strong>G2</strong> contains a special domain called Genx that can be used for TCP proxies<br />

other than the ones that are initially set up on the <strong>Sidewinder</strong> <strong>G2</strong>. A special<br />

domain called UDPx can be used for UDP proxies.<br />

If you set up more than one <strong>of</strong> your own proxies, they will not be isolated from<br />

each other using Type Enforcement since they are all contained in one domain<br />

(Genx for TCP and UDPx for UDP). However, proxies you add are still isolated<br />

from all other domains and cannot interfere with any other <strong>Sidewinder</strong> <strong>G2</strong><br />

activity.<br />

If you set up your own proxies or reconfigure established proxies, do not use<br />

ports 9000–9010. These ports are reserved by the <strong>Sidewinder</strong> <strong>G2</strong> for<br />

administration purposes.<br />

Tip: To set up additional proxies using the Admin Console, refer to “Setting up a<br />

new proxy” on page 270.<br />

The <strong>Sidewinder</strong> <strong>G2</strong> HTTP, HTTPS, and Telnet proxies can be configured to be<br />

transparent or non-transparent to users. Transparency for the HTTP and<br />

HTTPS proxies is configured on a per-rule basis via Application Defenses.<br />

Transparency for Telnet is determined by two distinct proxies that can be<br />

enabled and specified in your active rules (telnet and nt_telnet). When using<br />

transparent proxy settings, the user appears to connect directly to the desired<br />

network’s HTTP, HTTPS, or Telnet proxy without connecting to the <strong>Sidewinder</strong><br />

<strong>G2</strong> first.<br />

For example, to initiate an outbound Telnet session using a transparent Telnet<br />

proxy, a user would issue the following command from his or her workstation:<br />

telnet destination_IP_address<br />

With a non-transparent Telnet proxy, a user must first Telnet to the <strong>Sidewinder</strong><br />

<strong>G2</strong> and specify a destination address for the Telnet session. For example, the<br />

following shows how an internal user would initiate a Telnet session to a server<br />

in an external network using a non-transparent proxy that requires standard<br />

password authentication.<br />

>telnet internal_IP_address<br />

(connection message from the <strong>Sidewinder</strong> <strong>G2</strong> appears...)<br />

>Enter destination: destination_address<br />

>Username: username<br />

>Password: password<br />

(connection message from the destination Telnet server appears...)<br />

>login: username<br />

>Password: password

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!