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 4: Understanding Policy Configuration<br />

IP Filter rule basics<br />

126<br />

Limitations <strong>of</strong> NAT for IP Filter protocols<br />

Note the following limitations when setting up rules involving address rewriting<br />

for TCP/UDP/ICMP protocols.<br />

• NAT and redirection are not allowed for bi-directional IP Filter rules with<br />

stateful packet inspection enabled.<br />

• For address rewrite rules with redirection to the source address, only unidirectional<br />

rules are allowed. Furthermore, the destination address in this<br />

type <strong>of</strong> rule must have a significant bits value <strong>of</strong> 32 (that is, it must be a<br />

single host or netmap). This is because the redirect address must be a<br />

single host.<br />

Setting the IP Filter NAT port rewrite range<br />

When a packet from a source reaches the <strong>Sidewinder</strong> <strong>G2</strong> and matches an IP<br />

Filter rule with NAT configured, the source port and source address will be<br />

rewritten and the packet will then be forwarded to its destination.<br />

To facilitate this process, the IP Filter reserves a block <strong>of</strong> 875 ports for its own<br />

use. The OS will never allow a process to bind to a port in this range. Creating<br />

a TCP generic services proxy in this port range will not work. The default range<br />

is set to 9210—9995.<br />

If you need a port in IP Filter's reserved range (perhaps for a generic proxy),<br />

the range can be moved by modifying the Start <strong>of</strong> Reserved Ports field in the<br />

IP Filter Properties window. See “Viewing and modifying general IP Filter<br />

properties” on page 241.<br />

It is possible that an existing TCP proxy connection may be using a port in the<br />

range you specify. In this case the cf ipfilter command will fail. You should<br />

look at the current port usage by entering the netstat -a command and<br />

adjust the IP Filter port range accordingly.<br />

Specifying the source port in an IP Filter rule<br />

The <strong>Sidewinder</strong> <strong>G2</strong> enables you to specify the source port value to use in an<br />

TCP or UDP IP Filter connection. This capability is typically only used when<br />

connecting to an application that requires the source port to be a specific<br />

value. (In some cases the application will require the source port to be the<br />

same value as the port on which the application is listening.)<br />

This capability is implemented by configuring NAT on the appropriate IP Filter<br />

rule. This “source port” implementation <strong>of</strong> NAT, however, is different from a<br />

normal implementation <strong>of</strong> NAT.

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

Saved successfully!

Ooh no, something went wrong!